Incode Rate Limits
The Incode Omni API applies tiered, token-bucket rate limits by endpoint weight. Document endpoints (SUPER_HEAVY, e.g. add/front-id, add/back-id, process/id) and facial recognition endpoints (HEAVY, e.g. add/face, process/face) are limited to roughly 1 request/second with a 5-token burst, while other endpoints (OTHER) allow about 100 requests/second with a 50-token burst. Requests are capped at a 10 MB request/response size and a 30-second timeout. Exact account-level limits are set per deployment and not fully reconciled here.
Incode Rate Limits is the machine-readable rate-limit profile for Incode on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring requests, bytes, and seconds.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Identity Verification, Biometrics, KYC, Liveness, and Onboarding.
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/incode-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.