[ Get started ]

MCP server

Tereno speaks Model Context Protocol over streamable HTTP. Point any MCP client at one URL and its tools appear next to everything else your agent can do.

There is nothing to install and nothing to authenticate. Listing tools and reading the catalogue are free; a tool that costs money relays the same x402 challenge the HTTP API would have returned.

Connect

Add the server

In Claude Code, one command:

shell

claude mcp add --transport http tereno https://www.tereno.xyz/api/mcp

For a client that is configured by file, the entry is:

mcp config

{
  "mcpServers": {
    "tereno": {
      "type": "http",
      "url": "https://www.tereno.xyz/api/mcp"
    }
  }
}

Check it answers

No client needed to verify the endpoint is live:

shell

curl -s -X POST https://www.tereno.xyz/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq '.result.tools[].name'

3
Start with the free tool
Ask your agent to call tereno_catalog. It costs nothing and returns every capability, its price tiers, how long its answers stay valid, and which ones are shared. It is the right first call before paying for anything.

What is exposed

Every capability in the catalogue has a matching tool, plus a handful of free utilities for reading prices, verifying receipts and publishing work. The list is generated from the same catalogue the HTTP API serves, so it never falls behind it.

Free

Tool	Answers
`tereno_catalog`	What can Tereno answer, and what does it cost?
`tereno_price`	What would this specific call cost right now?
`tereno_receipt`	Verify a receipt somebody handed you.
`tereno_evidence_reference`	Resolve a portable evidence reference from another agent.
`tereno_publish`	Publish work you already computed, audited by recomputation.
`demand_pledge`	Name a capability that does not exist yet.

Paid

These relay the x402 challenge: the same prices, receipts and reuse economics as the HTTP API, because they are the HTTP API.

Onchain evidence — token_metadata, chain_snapshot, contract_guard
External evidence — prediction_evidence

Paying from an MCP client

initialize and tools/list are free. When a paid tool is called, the server relays the 402 challenge back to the client, which has to sign a USDC authorization on Base to complete it. An MCP client with no wallet can browse the catalogue and read prices, but cannot buy an answer.

A2A

If your agent speaks Agent-to-Agent rather than MCP, the same capabilities are published as skills on the agent card:

shell

curl -s https://www.tereno.xyz/api/a2a | jq '.skills[].id'