GenderAPI technical FAQ

How should clients handle rate limits and retries?

API operationsMarkdown version

Direct answer

Answer

V2 applies rate and concurrency limits; respect HTTP 429 and Retry-After. Every repeated prediction is a new operation with normal billing. Do not automatically retry a timeout, lost response or unconfirmed billing outcome. Inspect code, action and meta.usage.billing_status first; contact support with request_id for billing_reconciliation_required. Use bounded backoff only when billing is confirmed and the documented action permits a new attempt.

Further reading

Related guidance

Continue with the primary GenderAPI resources used for this answer.

Errors, limits and retriesOpen guide →Credits and usageOpen guide →