# HTTP Content-Disposition Filename Precedence Detector

> HTTP Content-Disposition Filename Precedence Detector is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-11-04).

Counts anomalous download filename fallbacks and unresolvable parameter bindings in source headers before a delivery switch

## Facts

- Endpoint: POST https://detect.halowerk.com/u/http-content-disposition-filename-precedence?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/http-content-disposition-filename-precedence-detector-0e34f3d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_41O0voiYS4Hy4tnFV4l7f

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability http-content-disposition-filename-precedence-detector-0e34f3d9 -d '<json body>'
```

Example prompt: Can you check https://files.example.com/report.pdf for any anomalous Content-Disposition filename fallbacks or unresolvable parameter bindings in its headers before we switch our delivery infrastructure?

## When to prefer this

Use this endpoint when you need to audit a specific URL's HTTP Content-Disposition header for filename parameter precedence anomalies — particularly the filename vs filename* fallback resolution — before switching CDN providers, delivery infrastructure, or file hosting. It is purpose-built for this narrow HTTP header compliance check rather than general header inspection tools.

## Known failure modes

- URL is unreachable or returns a non-HTTP error — no header data to analyze
- Target URL does not return a Content-Disposition header — empty or null result
- Malformed URL input fails schema validation — 400 error
- URL redirects to a non-file resource with no relevant headers — zero counts returned
- Network timeout when fetching remote URL headers

## How this service works

Zählt abweichende Download-Dateinamen-Fallbacks und nicht auflösbare Parameterbindungen in Quell-Headern vor einem Auslieferungswechsel.

## Output

Returns counts of anomalous filename fallback occurrences and unresolvable parameter bindings found in the Content-Disposition headers of the given URL's HTTP response, helping identify issues before a delivery infrastructure change.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "pattern": "^https?://"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/http-content-disposition-filename-precedence-detector-0e34f3d9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from detect.halowerk.com](https://www.zero.xyz/host/detect.halowerk.com/llms.txt)