Skip to main content
Planned. This service is not live yet. This page explains what it will do and what to use in the meantime.
Learn what to expect from RPC rate limits on BOT Chain today and how to keep your app within them. Uzo RPC’s rate limits will be published at launch.

​
Uzo RPC limits

Will be published at launch. There are no numbers to share yet.

​
Public endpoint limits

BOT Chain doesn’t publish rate limits for https://rpc.bohr.life or https://rpc.botchain.ai. BOTScan’s API doesn’t publish limits either. Treat both as shared resources with unknown limits.

​
Stay within unknown limits

  • Batch reads. Combine many eth_call reads into one with Multicall.
  • Poll at a sensible interval. Blocks arrive about every 0.75 seconds, so polling faster than once a second gains nothing.
  • Bound event queries. Read logs in chunks of a few thousand blocks, not from block 0. See Known limitations.
  • Cache on a server. Don’t call the RPC or explorer API from every visitor’s browser for data that changes rarely.
  • Retry with backoff. If a request fails with HTTP 429 or a gateway error, wait and retry with increasing delays.

​
At a hackathon

Many teams on one network can hit the same endpoints at once. See Faucet plan for funding, and ask teams to follow the tips above.

​
Learn more

Endpoints

Public endpoints you can use today.

Uzo RPC

What the planned service will add.
Last modified on October 2, 2026