How to get your WhoisXML API API usage, balance and spend programmatically
What the WhoisXML API API exposes
| Signal | WhoisXML API |
|---|---|
| Balance | Yes. GET user.whoisxmlapi.com/user-service/account-balance (per-product credits) |
| Spend history | No |
| Cost breakdown | No |
| Plan and quota | No |
| Cost on each response | No |
| Rate-limit headers | X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset |
| Credential | API key |
Call it yourself
Credential. A normal WhoisXML API key, passed as the apiKey query parameter.
Balance per product
curl "https://user.whoisxmlapi.com/user-service/account-balance?apiKey=$WHOISXML_API_KEY&outputFormat=JSON"
{
"data": [
{ "product_id": 1, "product": { "id": 1, "name": "WHOIS API" }, "credits": 486 }
]
}Trimmed to the fields Argus reads. Values are examples.
Gotchas
- Each product has its own pool, and pools don't combine. Argus shows the WHOIS API pool and keeps the rest.
- WhoisXML doesn't publish a response example for this endpoint, so parse it defensively.
- One-time credits expire after 12 months.
How WhoisXML API charges
Per-product prepaid credit pools (WHOIS, DRS, and standalone APIs) drawn down at per-API credit costs; one-time credits expire in 12mo. Monthly volume subscriptions exist (USD unverified).
| Plan | Monthly price |
|---|---|
| Free | $0 |
| Enterprise | Contact sales |
Free allowance. 500 on signup. First 500 WHOIS API calls.
At zero. Requests fail once a product's credit pool hits 0; one-time/prepaid credits expire after 12 months.
- 200 requests per second, per key. Excess rejected until next second.
Or let Argus track it
Paste the key once. Argus keeps the ledger, and your coding agent reads it through the MCP server.
- Reads the WhoisXML API balance every hour and keeps the series, so you get burn per day (top-ups never count as negative spend) and days until it hits zero.
- With the SDK, itemizes each call by endpoint and prices it at WhoisXML API's per-operation rates.
- Emails you on low balance, days to zero, a spend spike, or projected overage.
- Hands all of it to your coding agent over MCP, so it can ask what a run cost or how much runway is left without leaving the editor.
> what has whoisxml cost today, and how long until it runs out?
get_overview → whoisxml: mtd spend, burn per day, days to zero
get_request_costs { "provider": "whoisxml", "limit": 25 }
get_advisories → credits_low, spend_spike, rate_limit_low …Questions
- Does WhoisXML API have an API for its balance?
- Yes. GET https://user.whoisxmlapi.com/user-service/account-balance?apiKey=KEY&outputFormat=JSON returns a credit balance for each product. The call is free.
- Can I get WhoisXML API spend per day from the API?
- Not as a series. Derive it from how much the balance drops each day, ignoring top-ups.
- What happens when WhoisXML API credits run out?
- Requests fail once a product's credit pool hits 0; one-time/prepaid credits expire after 12 months.
- What key does Argus need for WhoisXML API?
- A normal WhoisXML API key, passed as the apiKey query parameter.
Related
Pricing and limits verified 2026-07-21 against whois.whoisxmlapi.com/documentation/making-requests, whois.whoisxmlapi.com/documentation/balance-information, whois.whoisxmlapi.com/documentation/limits. Endpoints are the ones the Argus WhoisXML API connector calls.
Connect a provider key, point Claude Code or Cursor at the Argus MCP server, and ask what the last run cost.