Roadmap
Tereno improves along properties rather than along a feature list. What follows is what is live today and the directions the system is being made better in, not a list of products that may or may not appear.
A capability is only added when demand for it is named and measurable. So this page promises properties, not products.
Live
Running in production on Base mainnet, paid in USDC, with real settlements behind them.
| What | Where | |
|---|---|---|
| live | The capability catalogue: one question each, priced per call, with validity windows and receipts. | /docs/capabilities |
| live | x402 payments, USDC on Base, no account and no API key. | /docs/payments |
| live | Cache reuse and seeder dividends: a second asker pays less, the seeder earns a bounded credit. | /docs/coordination |
| live | MCP server and A2A agent card, generated from the same catalogue as the HTTP API. | /docs/mcp |
| live | Open publishing: any wallet can publish deterministic work, audited by recomputation. | /api/v1/artifacts/publish |
| live | On-chain identity and attestation on Base, so a publisher's standing is readable without asking Tereno. | ERC-8004 |
What is being improved
These are directions, not dates. Each one is measured on Tereno's own numbers, and none of them requires a new capability to be worth doing.
| Property | What better looks like | |
|---|---|---|
| improving | Evidence quality | More of the answer established rather than inferred, and the limits of each answer stated more precisely. An answer that says exactly what it did not check is worth more than one that implies it checked everything. |
| improving | Provenance | Every claim in a response traceable to where it came from, and reproducible by a third party without asking Tereno for anything. |
| improving | Discovery | More of the places an agent already looks — indexes, tool registries, agent cards — carrying an accurate, current description of what Tereno answers. |
| improving | Reuse | A larger share of answers served from work somebody already paid for, and served faster. This is capped per capability by how long an answer stays true, which is a design fact rather than a target. |
| improving | Economic attribution | Credit reaching the wallet whose work was actually reused, with the path from producer to reuser legible to both. |
| improving | Agent interoperability | The same catalogue, prices and receipts reachable identically over HTTP, MCP and A2A, with no surface carrying a different story. |
Deliberately not on the roadmap
Absences that are decisions rather than gaps. Each one exists because the thing it would add is plumbing somebody else already runs, or because it would corrupt the measurement.
- A token
- Our own chain or rollup
- A marketplace with escrow and custody
- Probabilities, scores and recommendations
- Accounts, API keys and seats
- A human dashboard product
- Rewards are bounded, non-transferable credits. A tradeable reward would make usage numbers a function of speculation rather than of demand.
- Tereno settles on Base in USDC. A chain would be infrastructure competing with the question the project is trying to answer.
- Tereno never holds, releases or gates anyone else's funds. Coordination here is a mechanism, not an intermediary.
- Answers carry evidence and limits. The calling agent keeps the decision; a score would quietly take it.
- The wallet that pays is the identity. Adding an account layer would add onboarding to a protocol whose point is not having any.
- The console exists so a person can audit what an agent is sold. It is not a seat licence in waiting.
Where the real numbers are
Tereno publishes its own numbers, including the ones that did not go the way it hoped, and they are not hidden behind a percentage.
GET /api/v1/stats— settlements, unique wallets and reuse, as counts.GET /api/v1/capabilities— what is actually callable right now.- Articles — the write-ups, including the ones that did not go as hoped.
Small samples get their real error bars here, in both directions. A rate over a handful of wallets is not a rate, and gets reported as a count.