Verifiable evidence for autonomous agents
Tereno is a cooperation layer where agents pay for verified information before they act — and reuse trusted work instead of repeating it. Paid per call in USDC over x402. No account, no API key, no signup: the wallet that pays is the identity.
Ask. Verify. Pay. Reuse.
An agent asks something it needs to know before it acts: what token is this, what is the current state of the chain, is this contract safe to touch, what evidence supports this proposition. It pays a few cents and gets a typed answer with its provenance, a validity window and a receipt.
When verified work already exists, another agent can reuse it instead of paying to reproduce the same work — it is served the stored answer for less, and the agent that produced it receives credit for that reuse. That is what makes this a cooperation layer rather than an API: cooperation is not a second product, it is what happens when verified work can be economically reused.
Start here
The live catalogue: what each capability answers, what it costs and how long the answer stays true.
Connect Claude Code, Claude Desktop or any MCP client in one command.
Drive the same endpoints by hand: curl, the browser console, and the TypeScript client.
Your first call
Every paid endpoint speaks x402. An unpaid request answers 402 with the price and the payment terms in a header; the same request retried with a signed USDC authorization returns the answer. You can see the whole contract without paying anything:
# What can Tereno answer, and what does it cost? Free.
curl -s https://www.tereno.xyz/api/v1/capabilities | jq '.capabilities[] | {id, summary, pricing}'
# Ask for something paid without paying, and read the challenge.
curl -i -X POST https://www.tereno.xyz/api/v1/capabilities/prediction.evidence/invoke \
-H "Content-Type: application/json" \
-d '{"question":"Will Ethereum Pectra activate on mainnet before Q4 2026?"}'
# -> HTTP/1.1 402 Payment Required, terms in the payment-required headerHow it fits together
Shared work, cache hits and reuse dividends: why a generic answer is the point rather than the weakness.
The 402 handshake, USDC on Base, quotes, receipts and what a settlement actually proves.
What Tereno is, and is not
The shape matters more than the feature list, because most of what follows only makes sense once it is clear what the product is trying to be.
- A pay-per-call source of verifiable answers about on-chain and public state
- A place where a generic answer gets cheaper because others also asked it
- An answer with provenance, a validity window and a reproducible receipt
- Machine-first: typed JSON, a published OpenAPI spec, an MCP server
- A small, deliberate catalogue: four answers, each with its evidence attached
- A subscription API with accounts, keys and rate plans
- A source of proprietary data nobody else could produce
- A recommendation, a score or a prediction
- A dashboard product with a human seat licence
- A broad platform with a feature for every question
a buyer could get this from their own nodeis aimed at a product Tereno never tried to be. The sharper question is who the buyer is: an agent already running its own node has nothing to gain from pooling, and an agent that is not is exactly who benefits.
Machine-readable surfaces
Discovery is machine-first. Everything below is free to read and needs no account.