What usage information is available?
GET /usage returns the current month, total_requests, monthly_limit, remaining_requests, and an api_keys array. Each key record can include its identifier, plan, requests_this_month, remaining_requests, monthly_limit, and last_used_at. The endpoint gives an account-level capacity view and enough per-key context to attribute consumption to named applications without exposing the raw API key secret.
How can usage data support operations?
Display remaining capacity on an internal dashboard, alert when thresholds are crossed, investigate sudden traffic changes, and identify dormant or unexpectedly active credentials. Per-key totals are particularly useful when production, staging, and worker services have separate keys. The account summary remains essential because all those workloads consume one shared monthly allowance, even when a Pro key has its own lower cap.
How frequently should usage be requested?
Poll at a modest interval appropriate for the account volume and alerting requirement rather than before every lookup. Usage retrieval does not consume the lookup allowance, but unnecessary high-frequency polling still creates noise and operational dependency. Cache the summary briefly for dashboards, track the time of the reading, and avoid presenting an old remaining value as an exact real-time guarantee during fast traffic growth.
How should last-used data be interpreted?
A null last_used_at can mean the key has not made a recorded request, while an older value can help identify a candidate for retirement. It does not prove that a service is permanently unused; scheduled or seasonal workloads may be quiet. Confirm ownership and deployment state before revocation. Combine the timestamp with key name, expected schedule, and recent request count during access reviews.
How do I retrieve the usage summary?
Authenticate GET /usage with the same key header used for lookups. Check the status before decoding the summary and keep the response private because it contains account and key-level operational information. The request below is suitable for a server-side monitoring job or authenticated dashboard backend.
curl --fail-with-body --max-time 10 \
-H "Authorization: Bearer $IPROUT_API_KEY" \
https://api.iprout.com/usageWhat alerts are most useful?
Create separate thresholds for shared remaining capacity and high-value keys, and alert on unusual growth rather than only absolute exhaustion. Track HTTP 429 responses beside usage readings so cap failures can be diagnosed quickly. Redact credentials, restrict access to operational dashboards, and preserve enough historical aggregate data to distinguish normal seasonal traffic from a leak, loop, or abuse event.
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.
- Account and per-key totals
- Remaining request visibility
- Last-used context
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.