Fetch a URL and grade its HTTP security headers

What it does

Fetch a URL and grade its HTTP security headers. Pass url (scheme optional — defaults to https). Returns an overall letter grade + score, the list of present/missing headers, and a per-header analysis with the live value and specific issues for: Strict-Transport-Security (HSTS max-age/includeSubDomains), Content-Security-Policy (flags 'unsafe-inline'/'unsafe-eval'/missing default-src), X-Frame-Options or CSP frame-ancestors (clickjacking), X-Content-Type-Options (nosniff), Referrer-Policy, Permissions-Policy, and Cross-Origin-Opener/Resource-Policy. Also flags Server/X-Powered-By info disclosure. Analyzed from the target's LIVE response headers through an SSRF-guarded fetch (private/loopback targets refused) — an LLM cannot see a site's current headers. For web-app security review, vendor assessment, and CI gates.

Tags: public-records · identifiers · ai-agents · us-gov-data · x402 · bazaar

Call contract

Method

GET

Input

query parameters

Output

json

Last paid call

2026-10-08

{
  "url": "https://example.com"
}

Use with an agent

1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
2. Inspect. Fetch /resources/42791.json for the price and payment options.
3. Pay. Call GET https://2s.io/api/security/http-headers. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, Solana, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price

$0.0045 / request

Protocol

x402 v2

Auth

No account or API key. Pay per request.

Networks

Base, Solana

Demand

4 calls · 3 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x2b6D4988Db4723E6908Db86Ab2b8dFBc51FC32C5",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "4500",
    "amountUsd": 0.0045,
    "maxTimeoutSeconds": 60
  },
  {
    "scheme": "exact",
    "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
    "payTo": "TW6ntaGzvj63ZgPjszd4FCGmVTGfzv1MAYZbjYcyWhn",
    "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "4500",
    "amountUsd": 0.0045,
    "maxTimeoutSeconds": 60
  }
]

Examples

curl "https://2s.io/api/security/http-headers"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid

const res = await fetch("https://2s.io/api/security/http-headers");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

import httpx
res = httpx.get("https://2s.io/api/security/http-headers")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider

2s.io

Endpoint

https://2s.io/api/security/http-headers

Machine-readable

/resources/42791.json