Circle Community Rate Limits
Circle publishes a documented rate limit for the Admin API of 2000 requests per 5 minutes per IP address (roughly 400 requests per minute), which Circle notes can change at any time. Requests over the limit should be retried with a backoff strategy rather than immediate retry. Admins can monitor their usage in the Developers tab of the community admin area, where counts update roughly 5 minutes after calls due to backend caching. Circle does not publish a distinct numeric limit for the Headless Member API or the beta WebSocket surface as of the review date. Pagination defaults are page 1 and 10 items per page.
Circle Community Rate Limits is the machine-readable rate-limit profile for Circle on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests, connections, and items.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Community, Rate Limiting, Quotas, and Admin API.
Limits
Policies
Sources
- https://api.circle.so/apis/admin-api
- https://api.circle.so/apis/admin-api/usage-and-limits
- https://api.circle.so/get-started/websockets-beta
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/circle-community-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.