Bitgo Rate Limits
The BitGo Platform API applies per-access-token request rate limits. When a client exceeds the allowance the API returns HTTP 429 (Too Many Requests). BitGo does not publish a single fixed public number for all accounts; limits are enforced per token and can be raised for enterprise customers under a commercial agreement. Specific per-endpoint values are not reconciled in this artifact.
Bitgo Rate Limits is the machine-readable rate-limit profile for BitGo on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Digital Assets, Custody, Wallets, Rate Limiting, and Quotas.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/bitgo-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.