HyperVerge · Rate Limits

Hyperverge Rate Limits

HyperVerge does not publish fixed numeric per-second or per-minute rate limits in its public REST-API documentation. Throughput and monthly verification volume are governed by the commercial plan (Start / Grow / Enterprise) and the appId/appKey credentials issued to the account, rather than by a documented public request cap. Invalid or missing credentials return HTTP 401. Contact HyperVerge for the concurrency and volume limits provisioned for a given account and region host.

Hyperverge Rate Limits is the machine-readable rate-limit profile for HyperVerge on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests and verifications.

The profile also includes 2 backoff/retry policies defined and response codes documented for unauthorized.

Tagged areas include Identity Verification, KYC, India, Rate Limiting, and Quotas.

2 Limits
Identity VerificationKYCIndiaRate LimitingQuotas

Limits

Verification Requests account
requests
not published
No fixed numeric request-rate limit is documented for the REST APIs; governed by the account's commercial plan.
Monthly Verification Volume account
verifications
per plan
Volume allowance is set by the Start / Grow / Enterprise agreement and issued credentials.

Policies

Credential Enforcement
Every request must include a valid appId/appKey pair; invalid or missing credentials return HTTP 401.
Backoff Strategy
Clients should implement retry with exponential backoff on transient 5xx responses and respect any account-level concurrency provisioned by HyperVerge.

Sources