Create a key
Keys belong to your project. Name them for each app or environment, and revoke them in the console when you rotate access.
project / api keysThyme / Gate
Read state, fetch logs, and send transactions through a project endpoint. Keep your app on the JSON-RPC interface you already know.
Request · POST $THYME_RPC_URL
{
"jsonrpc": "2.0",
"method": "eth_chainId",
"params": [],
"id": 1
}Response · 200 OK
{
"jsonrpc": "2.0",
"result": "0x1",
"id": 1
}01 / Connect
Create a key, choose a network, and paste its endpoint into the client you use today. No custom transport or SDK required.
Keys belong to your project. Name them for each app or environment, and revoke them in the console when you rotate access.
project / api keysPick a mainnet or testnet endpoint. The console shows the exact HTTPS URL for every network available to your project.
network / endpointUse the URL with any JSON-RPC client. Reads, logs, and transaction submissions go through the same familiar interface.
POST / json-rpcimport { createPublicClient, http } from 'viem'
import { base } from 'viem/chains'
const client = createPublicClient({
chain: base,
transport: http(process.env.THYME_RPC_URL),
})
const block = await client.getBlockNumber()02 / Networks
Switch networks by changing the endpoint and chain configuration. Available HTTPS URLs appear in your project console alongside chain IDs and network status.
Mainnet · Sepolia
Mainnet · Sepolia
Mainnet · Amoy
Mainnet · Sepolia
Mainnet · Sepolia
Mainnet · Fuji
Representative networks. Check the console for the current endpoint list and availability.
03 / Visibility
The console tracks requests, errors, and compute units. Inspect usage by method, see traffic for each API key, and follow your free allowance through the billing cycle.
04 / Pricing
One pay-as-you-go plan. Your first 30 million compute units each month are free; usage above that is metered.
Need more throughput or a signed SLA? Talk to us about enterprise.
Start here