Which plans support custom key caps?
Custom per-key caps are available on Pro. A Pro key can be created with a value from 100 to 1,000,000 requests. Starter supports multiple active keys but each uses the fixed 100,000-request plan-level ceiling rather than a chosen key cap. Free has one active key within its 10,000-request allowance. Caps do not create or reserve additional account capacity.
How does a cap interact with shared usage?
Every successful lookup contributes to the same account monthly total and to the calling key's own total. If a Pro key reaches its lower cap first, that key receives HTTP 429 while another active key can continue as long as the account still has shared requests remaining. If the account allowance is exhausted, all keys are affected regardless of their individual remaining cap.
How should a cap value be chosen?
Estimate the workload's expected monthly volume, add a deliberate operating margin, and keep the value below the account allowance when isolation is the goal. A low cap is useful for staging, a new integration, or a bounded customer-facing feature. A production service with variable traffic needs enough headroom and alerts before exhaustion. Review actual per-key consumption rather than choosing every cap at the maximum.
Can an existing cap be edited?
No. The cap is fixed for that credential after creation. To change it, create a replacement key with the new value, deploy and verify the replacement, then revoke the old key. This immutable model makes the credential's security properties predictable. Reserve an active-key slot for rotation when possible and avoid waiting until the key is already blocking critical traffic.
How do capped keys call IPRout?
The cap does not change request syntax. Applications authenticate normally and should handle HTTP 429 as a capacity state rather than retrying aggressively. The explicit request below can verify a new key. Follow it with GET /usage to confirm the key's configured limit and current remaining request count.
curl --fail-with-body --max-time 10 \
-H "Authorization: Bearer $IPROUT_API_KEY" \
https://api.iprout.com/ip/8.8.8.8What monitoring should surround a cap?
Alert before the key reaches its limit and before the shared account reaches its own limit. Compare requests_this_month and remaining_requests for the key with total_requests and remaining_requests for the account. Investigate unexpected growth by workload. Keep retry behavior bounded, provide a graceful product fallback where possible, and change a cap through a planned key rotation rather than an emergency at zero capacity.
Which IPRout plan fits this workload?
Use the 7-Day Developer Key for a short evaluation with 1,000 requests. Free supports ongoing low-volume use with 10,000 monthly requests and 1 active key. Starter adds 100,000 requests, 2 active keys, and up to 5 exact CORS origins per key. Pro provides 1,000,000 requests, 5 active keys, up to 10 origins per key, and a configurable 100 to 1,000,000 request cap when each key is created. All active account keys consume one shared monthly allowance.
| Plan | Monthly requests | Active keys |
|---|---|---|
| Free | 10,000 | 1 |
| Starter | 100,000 | 2 |
| Pro | 1,000,000 | 5 |
What are the key benefits?
This feature uses the same authenticated HTTPS interface and predictable JSON conventions as the rest of IPRout. That keeps the integration small while letting teams separate product logic from the details of IP intelligence and API key controls.
- Available on Pro
- Range: 100 to 1,000,000
- Does not increase shared capacity
How do I get started?
Generate a 7-Day Developer Key for evaluation or create an account key for an ongoing integration. Begin with the documented request, add status-aware error handling and a finite timeout, then connect only the response fields your product needs. Review usage before launch, keep the secret in trusted infrastructure, and follow the linked documentation for feature-specific configuration.