# URL HTTP Headers Inspector

> URL HTTP Headers Inspector is a paid API for AI agents from url-intel.bowling-anthony.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Fetches and analyzes the HTTP response headers of a given URL, reporting on server identity, content type, caching directives, and the presence or absence of security headers.

## Facts

- Endpoint: GET https://url-intel.bowling-anthony.workers.dev/headers
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/url-http-headers-inspector-0e4f823a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__rmPnS3KdDCRZCwOAG6b2

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 url-http-headers-inspector-0e4f823a
```

Example prompt: Can you check what HTTP response headers https://example.com returns — specifically which security headers like HSTS, CSP, or X-Frame-Options are set and which are missing?

## When to prefer this

Use this endpoint when you need a quick, per-URL HTTP header inspection — especially for security audits, server fingerprinting, or cache configuration checks — without needing to follow redirect chains (use the sibling redirect endpoint for that) or parse page content. Ideal for automated compliance checks, pre-deployment header audits, or security monitoring workflows.

## Known failure modes

- Target URL is unreachable or returns a network error — endpoint may return an error or timeout
- URL is malformed or missing — likely returns a 400 Bad Request or validation error
- Target server blocks automated requests — may return 403 or empty header set
- DNS resolution failure for the target host — results in a connection error
- Redirects not followed — headers returned may be from an intermediate redirect response rather than the final destination

## How this service works

What a host says about itself: status, server, content type, caching, and which security headers are set or missing.

## Output

Returns the HTTP response headers from the target URL, including the status code, Server header, Content-Type, caching-related headers (Cache-Control, Expires, ETag), and a summary of which security headers (such as HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy) are present or absent.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/url-http-headers-inspector-0e4f823a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from url-intel.bowling-anthony.workers.dev](https://www.zero.xyz/host/url-intel.bowling-anthony.workers.dev/llms.txt)
