# true402 HTTP Headers Check

> true402 HTTP Headers Check is a paid API for AI agents from true402.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-21).

Checks and returns the HTTP response headers for a given URL

## Facts

- Endpoint: POST https://true402.dev/api/v1/headers-check?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/true402-http-headers-check-33046f14
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MDEoQUq8DHcVAwe0ShTu6

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 true402-http-headers-check-33046f14 -d '<json body>'
```

Example prompt: Can you check what HTTP headers are returned by https://example.com — I want to see things like CORS, cache-control, and any security headers it sets?

## When to prefer this

Use this endpoint when you need to programmatically inspect the HTTP headers returned by any public URL, especially for security auditing, CORS checking, or infrastructure analysis. It is pay-per-call via x402 with no API key needed — ideal for machine-native or agent-driven workflows where wallet-based micropayments are available.

## Known failure modes

- URL is unreachable or times out — may return error or empty headers
- Invalid or malformed URL input — likely returns validation error
- Non-HTTP/HTTPS URL schemes rejected — URL must begin with http:// or https://
- Payment failure via x402 — returns 402 if USDC wallet balance is insufficient

## How this service works

The machine-native marketplace. Wallet = identity. Pay per call with HTTP 402.

## Output

Returns an object containing the HTTP response headers returned by the target URL, including keys like content-type, cache-control, x-frame-options, strict-transport-security, and other server-sent headers.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "The URL (http/https)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ok": {
   "type": "boolean"
  },
  "url": {
   "type": "string"
  },
  "score": {
   "type": "number",
   "description": "0–100 (fraction of security headers present)"
  },
  "server": {
   "type": "string"
  },
  "status": {
   "type": "number"
  },
  "isHttps": {
   "type": "boolean"
  },
  "missing": {
   "type": "array",
   "description": "missing security headers"
  },
  "securityHeaders": {
   "type": "object",
   "description": "present security headers → value"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/true402-http-headers-check-33046f14/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from true402.dev](https://www.zero.xyz/host/true402.dev/llms.txt)