Metamap Rate Limits
MetaMap does not publish explicit numeric rate limits in its public developer documentation. The API uses an OAuth 2.0 client-credentials flow that issues a one-hour JWT bearer token; concurrency is governed by the per-account verification volume tier negotiated with sales. SDK Cooldown is a product-level throttle that prevents duplicate verifications from the same origin within a configurable window. This document records the throttling surface so consumers know which headers and response codes to expect.
Metamap Rate Limits is the rate-limit profile for MetaMap on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for unauthorized, forbidden, notFound, throttled, and serverError.
Tagged areas include Identity Verification, KYC, and Rate Limiting.
limitremainingresetretryAfter
generated, dated 2026-05-25.
Limits
Sources
- https://docs.metamap.com/reference/authentication
- https://docs.metamap.com/docs/sdk-cooldown
- https://docs.metamap.com/docs/errors
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.