Trulioo Rate Limits
The REST API publishes no numeric rate limit: the API reference overview says only that "rate limits are designed to be very accommodating and flexible" and that support will adjust them on request, and no rate-limit response header or 429 behaviour is documented. The hosted MCP server publishes early-access usage limits signalled by a retry_after_seconds field in the tool result, plus hard caps on sandbox scenarios and on the analytics query. The rows below quote those caps verbatim from the MCP developer index.
Trulioo Rate Limits is the rate-limit profile for Trulioo on the APIs.io network — every limit transcribed verbatim from the provider’s own documentation on 2026-10-08.
It captures 5 rate-limit definitions, including MCP early-access usage limit — Usage limits apply during early access; Sandbox scenario body size — bodies cap at 16 KiB; Sandbox scenarios per caller — 50 per caller.
Limit state is signalled in the rest and mcp response headers.
Tagged areas include Identity Verification, KYC, KYB, AML, and Watchlist Screening.
restmcp
Limits
Sources
- https://developer.trulioo.com/reference/api-reference-overview.md
- https://mcp.trulioo.com/developer/index.md
- https://mcp.trulioo.com/developer/llms.txt
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.