Meet Thyme Gate

Every onchain app needs an RPC endpoint. Usually that's yet another vendor with its own dashboard, its own keys and its own bill, separate from the rest of your backend.

Thyme Gate is the RPC product in thyme/labs. It gives you a JSON-RPC endpoint per chain, with keys scoped to your project and usage you can actually read. It sits in the same workspace as our onchain automation (Flow) and hosted subgraphs (Atlas).

Keep your client, change the URL

There's no custom SDK or transport. If your code speaks JSON-RPC, it works with Gate.

1. Create a key

Keys belong to a project. Name one for each app or environment, such as orders-production or orders-staging, so you can see each one's traffic and revoke them separately.

2. Choose a network

Pick a mainnet or testnet. The console shows the exact HTTPS URL for every network available to your key.

3. Send a request

curl "$GATE_RPC_URL" \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Or with viem:

import { createPublicClient, http } from 'viem'
import { mainnet } from 'viem/chains'

const client = createPublicClient({
  chain: mainnet,
  transport: http(process.env.GATE_RPC_URL),
})

const block = await client.getBlockNumber()

Reads, logs and transaction submissions all go through the same interface. To switch chains, change the endpoint and the chain config.

Supported networks

Chain	Chain ID	Networks
Ethereum	1	Mainnet, Sepolia
Polygon	137	Mainnet, Amoy
Optimism	10	Mainnet
BNB Smart Chain	56	Mainnet
Unichain	1301	Sepolia

Need another chain? Email [e-mail] and tell us which one.

See the traffic behind the bill

RPC bills are often a black box. Gate's console shows:

• Requests and errors by network
• Compute units by RPC method, so you can see what's driving cost
• Traffic and last use per API key
• Your free allowance through the billing cycle

If one method is eating your budget, you'll see it in the method breakdown instead of finding out on the invoice.

Keys you control

• Keys are scoped to a project, and only workspace owners and admins can create or revoke them.
• To rotate a key without downtime, create a new one, deploy the new URL, check that traffic moved, then revoke the old key.
• Revoking a key stops future requests that use it.

One tip: the endpoint URL contains your key. Keep it in server-side config, not in a browser bundle, and redact it from logs and screenshots.

Need more throughput or a signed SLA? Talk to us about enterprise.

Try it

• Get an endpoint: https://gate.thymelabs.io
• Quickstart: https://flow.thymelabs.io/docs/gate/quickstart

Your client is ready. Give it an endpoint. What are you building? Tell us in the comments. 👇