PerformanceBlog
Tempo MCP serverGive agents search and read tools for Tempo docs
Skip to content
LogoLogo

Tempo API

Use the Tempo API for indexed chain data, readable account activity, token metadata, balances, transfers, transaction receipts, and RPC methods.

Start with the Tempo API

Every endpoint is served over HTTPS from https://api.tempo.xyz under the /v1 prefix. Most read endpoints are public, so you can make your first request without any credentials:

curl 'https://api.tempo.xyz/v1/blocks'

The same base URL and credentials give you access to three surfaces:

  • REST API: typed endpoints for indexed chain data such as blocks, transactions, tokens, balances, transfers, and receipts.

    curl 'https://api.tempo.xyz/v1/addresses/0x.../balances'
  • JSON-RPC API: a node-level RPC entrypoint for raw chain access.

    curl 'https://api.tempo.xyz/rpc' \
      --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'
  • Indexer API: a SQL-over-HTTP entrypoint for read-only queries against indexed chain data.

    curl --get 'https://api.tempo.xyz/v1/indexer/query' \
      --data-urlencode 'chainId=mainnet' \
      --data-urlencode 'sql=SELECT num, hash FROM blocks ORDER BY num DESC LIMIT 10'

There are three ways to authenticate, depending on the throughput you need:

MethodHowLimit
PublicNo credentials20 requests / minute per IP
MPPAuthorization: Payment <credential>Pay per request, no key required
API keyAuthorization: Bearer tempo:sk:...Higher, dedicated quota per key

Public access lets you try the API and serve low-volume reads, and MPP lets you pay per request without a key. For higher, dedicated quotas, use an API key.

Try a Tempo API request

Check out an endpoint below and click "Try" to run it directly against the API. For example, fetch the token balances for an address:

Tempo REST API endpoints

Next API integration steps

Was this helpful?