1-cent-requests

What this is

1-cent-requests is an API marketplace that sells 14 context services to AI agents at a flat $0.01 per request. Payment happens in-band over HTTP using the x402 protocol: the server answers 402 Payment Required with machine-readable terms, the client signs a USDC payment and retries, a facilitator verifies and settles, and the response comes back — all in one request/retry cycle.

Every endpoint is a plain POST with a JSON body. Agents discover the catalog at GET /services, fetch per-service input schemas at GET /services/:slug, and get an OpenAPI 3.1 document at GET /openapi.json.

Token & contract safety

Honeypot and tax risk (token-risk), approval hygiene (approval-risk), contract verification (contract-explain), and phishing URL checks (phishing-check) across 6 EVM chains.

Market & protocol data

DEX pair snapshots (pool-snapshot), DeFi protocol fundamentals via DefiLlama (protocol-context), and read-only wallet briefs (wallet-brief).

Web context

Capped Exa search and page contents, Firecrawl map/search/scrape — strictly bounded so every call fits the one-cent envelope.

Live library docs

Context7 resolve-library and query-docs return current documentation snippets for any framework, with a bounded token budget.

x402 payments

Exact-price USDC payments settled on-chain through a facilitator that never custodies funds. The quote in every 402 names the amount, asset, and network — nothing else is ever drawn.

Built for agents

Machine-readable discovery, JSON Schemas per service, a consistent response envelope, and typed error codes. No signup flow anywhere.

The response envelope

Every successful service call returns the same shape:

{
  "service": "token-risk",
  "requestId": "…",
  "cache": { "hit": false },
  "providers": [{ "name": "goplus", "status": "ok" }],
  "warnings": [],
  "data": { "…": "service-specific payload" }
}

Errors are equally uniform — see Error Codes.