IPRout

Shared Quotas Across API Keys

Multiple API keys improve isolation and attribution, but they do not multiply plan capacity. Every successful lookup made by an account's keys contributes to the same monthly request total. Per-key usage and caps help control individual workloads inside that shared allowance.

Last updated August 10, 2026

How is account usage calculated?

The account total is the combined usage of its active keys during the current month.

Why use separate keys then?

Separate keys let you revoke one workload, apply different origins, attribute consumption, and on Pro contain a workload with its own cap.

How do I monitor shared capacity?

Use GET /usage and alert on both remaining_requests at the account level and remaining_requests for individual keys.