Context for agents.
One cent at a time.

Token risk, liquidity, contracts, wallets, protocols, and web context — paid HTTP endpoints an agent can discover, pay, and call in a single exchange. $0.01 per request. No accounts, no API keys, no subscriptions.

curl -X POST https://api.1cent.sivaram.dev/services/token-risk -H 'content-type: application/json' -d '{"chain":"base","tokenAddress":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'

browse 14 services

x402 v2 · usdc · base sepolia (testnet)

no wallet yet? running it returns the 402 quote — that’s the protocol working.

api · checking

1¢ requests · payment record · specimen

POST /services/token-risk

response: 402 payment required
quote: $0.01 USDC
network: eip155:84532 · base sepolia

retry + PAYMENT-SIGNATURE

response: 200 ok
settled: tx 0x3f9c…a1d2
total: $0.01

req_01hx…7km4 · no account · no api key

aggregated from 14 upstream providers

The whole payment is two requests.

POST /services/token-risk
Call any service. No auth header, no key, nothing provisioned.
402 PAYMENT-REQUIRED
The server quotes exact terms: $0.01 USDC, network named in full.
retry + PAYMENT-SIGNATURE
The agent's wallet signs the quote and retries. No checkout page exists.
200 + PAYMENT-RESPONSE
Settled on-chain; context delivered with provider attribution.

the trace, unabridged

$ curl -X POST https://api.1cent.sivaram.dev/services/token-risk \
    -H 'content-type: application/json' \
    -d '{"chain":"base","tokenAddress":"0x8335…2913"}'

< HTTP/1.1 402 Payment Required
< PAYMENT-REQUIRED: eyJ4NDAyVmVyc2lvbiI6Miw…   # $0.01 USDC

$ # sign & retry (agents use @x402/fetch)
< HTTP/1.1 200 OK
{ "service": "token-risk", "data": { "riskLevel": "low", … } }

The service ledger

every line item, itemized

All 14 services with endpoint and price
item	endpoint	price
crypto context · 7 items
Token Risk Scanner	/services/token-risk	$0.01
Pool & Liquidity Snapshot	/services/pool-snapshot	$0.01
Contract Explain	/services/contract-explain	$0.01
Protocol Context	/services/protocol-context	$0.01
Phishing URL Check	/services/phishing-check	$0.01
Wallet Brief	/services/wallet-brief	$0.01
Approval Risk Checker	/services/approval-risk	$0.01
web context · 7 items
Exa Web Search	/services/exa/search	$0.01
Exa Page Contents	/services/exa/contents	$0.01
Firecrawl Map	/services/firecrawl/map	$0.01
Firecrawl Search	/services/firecrawl/search	$0.01
Firecrawl Scrape	/services/firecrawl/scrape	$0.01
Context7 Resolve Library	/services/context7/resolve-library	$0.01
Context7 Query Docs	/services/context7/query-docs	$0.01
total — 14 services × $0.01		$0.14

Open the full catalog →

Machine commerce needs machine payments.

Subscriptions, checkout pages, and API-key dashboards assume a human is present. An agent mid-task has a wallet and an HTTP client — so that is the entire integration surface.

No signup friction: Crypto agents already hold wallets. The resource quotes its price inside the 402 response and the agent pays at request time — no key provisioning for every upstream vendor.
Exact per-request pricing: Every route carries an exact price; the flagship tier is one cent. Cost guardrails reject any upstream option that would break that envelope, so a request never costs more than its quote.
Read-only and attributable: Services never custody funds or sign transactions. Every response names its upstream providers with per-call status, so agents can weigh the evidence.

Discovery is part of the API.

Everything an agent needs is machine-readable: the catalog, per- service input schemas, a full OpenAPI document, and llms.txt on this site. Payment challenges follow the x402 v2 spec, so clients like @x402/fetch run the 402 → sign → retry loop automatically.

GET /servicesthe catalog
GET /services/:sluginput schemas
/openapi.jsonfull spec
/llms.txtfor agents
/llms-full.txtexpanded

agent discovery

$ curl https://api.1cent.sivaram.dev/services | jq '.services[0]'
{
  "slug": "token-risk",
  "path": "/services/token-risk",
  "price": "$0.01",
  "payment": { "protocol": "x402", "network": "eip155:84532" }
}

Questions, answered precisely.

Do I need an account or an API key?

No. The 402 response quotes exact payment terms, your agent's wallet signs them, and the retried request succeeds. There is nothing to register, provision, or rotate — ever.

How does an x402 payment actually work?

Two requests. The first returns HTTP 402 with a PAYMENT-REQUIRED header quoting $0.01 USDC and the exact network. The client signs that quote and retries with a PAYMENT-SIGNATURE header; the second response settles the payment on-chain and delivers the data. Clients like @x402/fetch run the whole loop automatically.

What currency and network does it use?

USDC over the x402 v2 protocol. Today it settles on Base Sepolia (eip155:84532) — testnet, stated plainly; mainnet is a configuration change, not a redesign. Every 402 quote names its exact network and asset, so clients never guess.

What does the cent actually pay for?

Aggregation, normalization, caching, and the payment overhead itself. Several services combine three or four upstream sources into one normalized response, and every response names those providers with per-call status.

Is any of this custodial?

No. Every service is read-only context: nothing custodies funds, requests approvals, or signs transactions. The only on-chain action is the one-cent payment your own wallet signs.

Can my agent use this without me?

Yes — discovery is part of the API. The catalog at GET /services, per-service input schemas, openapi.json, and llms.txt are all machine-readable. An agent can find a service, read its schema, pay, and call it without a human in the loop.

Spend a cent. Judge for yourself.

The first request costs $0.01 and takes less time than reading this sentence twice. Without a wallet it returns the 402 quote instead — that one is free.

curl -X POST https://api.1cent.sivaram.dev/services/token-risk -H 'content-type: application/json' -d '{"chain":"base","tokenAddress":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'

read the docs

Context for agents.One cent at a time.