# x402 QR API - Request Headers Endpoint

> x402 QR API - Request Headers Endpoint is a paid API for AI agents from x402-qr-api.vercel.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-11).

Returns the HTTP request headers received by the server, accessible via x402 micropayment

## Facts

- Endpoint: GET https://x402-qr-api.vercel.app/api/headers?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-qr-api-request-headers-endpoint-3ec1f6dd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__vI5kwZfARHQp5YZJw3vJ

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 x402-qr-api-request-headers-endpoint-3ec1f6dd
```

Example prompt: Can you check what HTTP headers the x402 QR API server is seeing from my request right now?

## When to prefer this

Choose this endpoint when you need to inspect or debug the raw HTTP headers arriving at the x402-qr-api server, particularly when troubleshooting x402 payment header propagation, verifying proxy forwarding behavior, or confirming what metadata a Next.js Vercel function receives. Not suitable for general header inspection of arbitrary servers.

## Known failure modes

- 402 Payment Required if valid x402 payment is not included
- 400 Bad Request if the request is malformed
- 500 Internal Server Error if the Next.js function fails
- Empty or partial headers if proxy strips certain fields before reaching the server

## How this service works

Generated by create next app

## Output

Returns a JSON object or plain response containing all HTTP request headers as key-value pairs, including standard headers like Host, User-Agent, Accept, Authorization, and any custom headers such as x402 payment tokens that were sent with the request.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-qr-api-request-headers-endpoint-3ec1f6dd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-qr-api.vercel.app](https://www.zero.xyz/host/x402-qr-api.vercel.app/llms.txt)