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

Connect to a Zone

Use this page when you need the RPC endpoint and chain metadata for Zone A or Zone B.

Account-scoped zone RPC methods require an X-Authorization-Token header signed by the Tempo account you are using. The interactive guides handle that for you automatically. If you are building your own integration, see the Zone RPC specification for the token format and the list of scoped methods.

Create a Viem client

Use zoneModerato(...) from viem/tempo/zones so the client has the correct chain metadata for the zone you want to reach.

import { createClient } from 'viem/tempo'
import { http, zoneModerato } from 'viem/tempo/zones'
 
const rpcUrl = 'https://rpc-zone-a.testnet.tempo.xyz'
 
const zoneClient = createClient({
  chain: zoneModerato(6),
  transport: http(rpcUrl),
})
 
const blockNumber = await zoneClient.getBlockNumber()
console.log(blockNumber)

Direct Connection Details

Zone A

PropertyValue
Network NameZone A
Zone ID6
Chain ID4217000006
HTTP URLhttps://rpc-zone-a.testnet.tempo.xyz
Portal Address0x7069DeC4E64Fd07334A0933eDe836C17259c9B23
Outbox Address0x1c00000000000000000000000000000000000002

Zone B

PropertyValue
Network NameZone B
Zone ID7
Chain ID4217000007
HTTP URLhttps://rpc-zone-b.testnet.tempo.xyz
Portal Address0x3F5296303400B56271b476F5A0B9cBF74350D6Ac
Outbox Address0x1c00000000000000000000000000000000000002

Zones do not expose a public block explorer for private activity. Use authenticated RPC reads instead.