HTTP Headers API

Returns the response headers, final status, redirect chain and a security-header grade for a URL, without downloading the body.

Updated

Agents read this page asGET /v1/http-headers/schemafree: schema, examples, errors, price

Endpoint
POST /v1/http-headers
Price
$0.002 per call
Timeout
8 s
max_timeout_seconds
29 (the whole call as the 402 envelope sells it: the timeout, plus payment verification and settlement around it)
Response cap
64 KB (65,536 bytes)

When to use it

It needs a hardened HTTP client -- an agent that fetches the URL itself can walk a redirect into a private address -- and the security grade is a deterministic, documented rubric it would otherwise have to build and maintain.

When not to use it

  • The destination needs more than 8 s to answer: the call ends with upstream_timeout (424).
  • The destination is on a private or local network: the network guard refuses it with blocked_target (403).

Parameters

One JSON body. The schema is free at GET /v1/http-headers/schema.

FieldTypeRequiredDescription
urlstringyesAbsolute http(s) URL to request, up to 2048 characters; up to five redirects are followed and every hop goes through the SSRF guard.
methodstringnoHTTP method for the request, HEAD by default; GET is for servers that mishandle HEAD, and its body is still never read. One of: "HEAD", "GET". Default: "HEAD".

Limits

LimitValue
Size cap64 KB (65,536 bytes)
Timeout8 s
Show the JSON Schema the handler validates against
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2048,
      "format": "uri",
      "description": "Absolute http(s) URL to request, up to 2048 characters; up to five redirects are followed and every hop goes through the SSRF guard."
    },
    "method": {
      "default": "HEAD",
      "description": "HTTP method for the request, HEAD by default; GET is for servers that mishandle HEAD, and its body is still never read.",
      "type": "string",
      "enum": [
        "HEAD",
        "GET"
      ]
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}

Example

The published example, verbatim: the request and the response it returns.

Request
POST /v1/http-headers
content-type: application/json
payment-signature: <base64 x402 payload>

{
  "url": "https://example.com/",
  "method": "HEAD"
}

Without the payment-signature header the call answers 402 with the payment requirements, including this endpoint's price and its max_timeout_seconds, so the deadline is known before anything is paid. The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case we cannot state for you is a settlement call that fails without answering: the error message says so when that is what happened.

Response200 OK
200 OK
payment-response: <base64 settlement receipt>

{
  "url": "https://example.com/",
  "source_url": "https://example.com/",
  "final_url": "https://example.com/",
  "redirect_count": 0,
  "http_status": 200,
  "headers": {
    "content-security-policy": "default-src 'self'",
    "content-type": "text/html; charset=utf-8",
    "cross-origin-opener-policy": "same-origin",
    "cross-origin-resource-policy": "same-origin",
    "permissions-policy": "geolocation=()",
    "referrer-policy": "strict-origin-when-cross-origin",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
    "x-content-type-options": "nosniff",
    "x-frame-options": "DENY"
  },
  "security": {
    "hsts": {
      "present": true,
      "max_age": 63072000,
      "include_subdomains": true,
      "preload": true
    },
    "csp_present": true,
    "x_content_type_options": "nosniff",
    "x_frame_options": "DENY",
    "referrer_policy": "strict-origin-when-cross-origin",
    "permissions_policy": "geolocation=()",
    "cross_origin_opener_policy": "same-origin",
    "cross_origin_resource_policy": "same-origin"
  },
  "security_grade": "A",
  "missing_security_headers": [],
  "fetched_at": "2026-08-26T18:00:00.000Z"
}

This example is illustrative: it shows the exact shape the handler returns, but it was not produced by a reproducible call, because the real answer depends on live network data that changes over time.

Response fields

FieldTypeIn the example
urlstring"https://example.com/"
source_urlstring"https://example.com/"
final_urlstring"https://example.com/"
redirect_countnumber0
http_statusnumber200
headersobjectan object with content-security-policy, content-type, cross-origin-opener-policy, cross-origin-resource-policy, permissions-policy, referrer-policy, strict-transport-security, x-content-type-options and x-frame-options
securityobjectan object with hsts, csp_present, x_content_type_options, x_frame_options, referrer_policy, permissions_policy, cross_origin_opener_policy and cross_origin_resource_policy
security_gradestring"A"
missing_security_headersarray0 items
fetched_atstring"2026-08-26T18:00:00.000Z"

Deterministic: the same input returns the same output. Clock-derived fields, when present, are declared in the response.

Call it from code

The client reads the 402, signs the payment and retries on its own.

// http-headers: $0.002 per call, paid in USD Coin on eip155:8453 via x402
// Install: npm install @x402/fetch@2 @x402/evm@2 viem@2
// Save as client.mjs (ES module, Node 18+), export EVM_PRIVATE_KEY with the paying wallet's key in your shell, then run: node client.mjs
// The wrapper reads the 402 (payment-required), signs and retries with payment-signature.
import { wrapFetchWithPayment, x402Client, decodePaymentResponseHeader } from '@x402/fetch'
import { ExactEvmScheme } from '@x402/evm/exact/client'
import { privateKeyToAccount } from 'viem/accounts'

const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY)
const client = new x402Client().register('eip155:8453', new ExactEvmScheme(account))
const fetchWithPayment = wrapFetchWithPayment(fetch, client)

const body = {
  "url": "https://example.com/",
  "method": "HEAD"
}

const res = await fetchWithPayment('https://grist.tools/v1/http-headers', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify(body),
})
console.log(res.status, await res.json())
const settle = res.headers.get('payment-response')
if (settle) console.log(decodePaymentResponseHeader(settle).transaction)

Errors

Every error is typed JSON. Only a successful call is settled.

CodeHTTPWhen
invalid_input400The body does not match the schema on this page. Nothing is charged. The body does not match the schema; its fields are url and method.
blocked_target403The destination is refused by the network guard: a disallowed address, or, for HTTP requests, a scheme other than http/https, a port other than 80/443, or credentials in the URL.
unreachable_target424The destination you named did not resolve or refused the connection.
upstream_timeout424The destination you named did not answer before the declared timeout for this endpoint expired.
internal500Our fault, and in almost every case nothing is charged. The exceptions come after the call has run and the settlement call was made: the message "The work was done but settlement could not be completed", and the messages starting with "Payment settlement returned". There, whether the payment moved is unknown to us as well. The payment moves at most once: its nonce is single-use and settlement is idempotent, so a retry with it is never charged twice. A retry is normally refused with a 402: replay_consumed, an expiry reason, or a reason saying the nonce was already used once the transfer is on-chain. Only if our server restarted before the transfer was final can a retry run the call again. Even then, the payment moves at most once. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain; to call again, sign a new payment.
rate_limited429Too many calls from the same payer, or too many calls towards the same destination domain. Nothing is charged.
concurrency_limit,
registry_at_capacity,
upstream_unavailable
503We could not serve the call right now. Retryable: wait the number of seconds in the retry-after header, then repeat the call. concurrency_limit and registry_at_capacity mean we were at capacity: the call did not run. You can send the same payment again if its validBefore is still far enough away to cover another call. If it is not, the retry gets a 402 authorization_validity_too_short: sign a new payment. upstream_unavailable means our internal service failed or did not answer in time: the call may already have run and the payment may have been settled. A retry with the same payment can get a 402 whose error field says why. authorization_validity_too_short: too little time is left before validBefore to cover another call. This check comes before the replay check, so it does not tell whether the first payment was settled. replay_consumed (the payment was used and may have been settled) or replay_exhausted (too many attempts): sign a new payment. replay_in_flight: the first call is still running, so wait and do not pay again. invalid_exact_evm_nonce_already_used: the transfer is already on-chain, so this payment cannot move again. Sign a new payment. An authorization can be settled only once, since its nonce is single-use. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain.
misconfigured503The service is not configured to serve calls. The call did not run and nothing is charged. It needs a fix on our side, so there is no retry delay to wait for.

Input that is rejected before the tool runs (malformed JSON, schema mismatch, body over the size limit) is never charged.

Questions

How much does a call to the HTTP Headers API cost?

$0.002 per call, paid in USD Coin on Base via x402. There is no account and no API key: the price is in the 402 answer, before anything is paid.

What is the timeout of http-headers?

The endpoint itself runs for at most 8 s. max_timeout_seconds in the 402 answer is 29: that covers the whole call, including payment verification and settlement around it.

How large can a response from http-headers be?

The response-size cap is 64 KB (65,536 bytes).

Is the http-headers input schema free to read?

Yes. GET https://grist.tools/v1/http-headers/schema returns the input schema for free, paid endpoints included.

What happens if a call to http-headers fails?

The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case that cannot be stated in advance is a settlement call that fails without answering: the error message says so when that is what happened.

What does http-headers return?

A JSON object with 10 top-level fields: url, source_url, final_url, redirect_count, http_status, headers, security, security_grade, missing_security_headers and fetched_at. The example on this page is illustrative, not a recorded call.