Thyme Gate
Gate is Thyme's blockchain RPC product. Its console provides authenticated HTTPS endpoints, project API keys, request analytics, and compute-unit usage. Some existing navigation, API fields, and billing records still call this product RPC or use the service identifier rpc.
Use Gate with an execution client such as viem to read chain state, call contracts, estimate transactions, and interact with the RPC methods available on your selected network.
Start using Gate
- Select a workspace and project with an active RPC service subscription.
- Create an RPC API key as a workspace owner or admin.
- Open Endpoints, select your key and network, and copy the complete HTTPS URL.
- Verify its chain ID before using it in your application.
Follow the quickstart for a first request and a viem client.
Gate, Flow, and Lift
| Need | Product |
|---|---|
| Read chain state or connect an ordinary execution client | Gate |
| Run TypeScript tasks on a trigger and execute their results | Flow |
| Sponsor and bundle a supported ERC-4337 UserOperation | Lift |
Gate does not turn an execution RPC request into a sponsored transaction. Lift uses a separate endpoint and a separate secret-key format. For a direct Lift integration, use Gate as the execution client and Lift as the bundler/paymaster transport.
Flow provides its task runtime with chain access through the SDK context. A task normally uses that context instead of embedding a Gate key in its source.
Availability and limits
The Endpoints page discovers the networks available to your key. That current response is the source of truth for network availability; a chain name, icon, or explorer link in the interface does not imply an enabled endpoint.
RPC methods, archive availability, log ranges, request sizes, rate limits, and transport capabilities can vary by endpoint and plan. Use the displayed HTTPS endpoint and verify additional capabilities before depending on them. See endpoints and requests, keys, usage, and troubleshooting.