Inspect local HTML, JSON and OpenAPI files and save a diagnostic report.
Free local useSoftware licence
Market / detect.halowerk.com · /u/fetch-response-mime-destination-admission
External service · publisher supplied metadata
detect.halowerk.com · /u/fetch-response-mime-destination-admission
Source and listing identity
Source: x402 Bazaar
Listing ID: x402:ff6b2feb9b1f186ff7f928c79e83997c30702d0f1bd9ca8e564cce6188474cad
Topic categories are inferred from listing text. Prices are source declarations; provider terms take precedence.
A registry entry or matching company name does not establish product authorship. Compare record IDs before treating similar titles as one product.
When transferring a measured response into a browser-compatible resource pipeline, determine the exact conditional refusal relation of the two Fetch MIME rules for script-like, style and other request destinations. Preserve distinction between unconditional MIME refusal and Nosniff-dependent refusal, including duplicate field precedence. Return aggregate rule facts, never actual browser blocking, Fetch success or security assessment.
Listing completeness · 80/100
Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.
- Name and traceable source
- 10/10 · Present
- Meaningful description
- 10/10 · Present
- Connection or installation reference
- 20/20 · Present
- Dedicated documentation or source repository
- 0/15 · Missing or insufficient
- Explicit free access or numeric tariff
- 20/20 · Present
- Declared integration protocol
- 10/10 · Present
- Source updated within 90 days
- 10/10 · Present
- Declared capability names
- 0/5 · Missing or insufficient
Evaluated 2026-11-01 · Method listing-completeness-1. Scoring rules
Connect & use
Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.
x402 resource
https://detect.halowerk.com/u/fetch-response-mime-destination-admissionRead the current payment requirements with a compatible client before authorizing a call.
Categories and declared capabilities
Topic categories are derived from publisher text for discovery, not independently verified capabilities.
The registry does not provide a verified tools list. See the observations, when available, for any tools/list check; a published tools list does not establish that execution succeeds.
Evidence, with its limits.
This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.
The listing completeness score measures published information only. No safety or performance score has been assigned. A signature, source listing or successful HTTP response does not certify factual accuracy or safety.
How verification states work →Related tools
Similar tasks and categories; compatibility has not been tested.