How to get your MillionVerifier API usage, balance and spend programmatically
What the MillionVerifier API exposes
| Signal | MillionVerifier |
|---|---|
| Balance | Yes. GET /api/v3/credits?api=KEY ({ credits }) |
| Spend history | No |
| Cost breakdown | No |
| Plan and quota | No |
| Cost on each response | No |
| Rate-limit headers | None |
| Credential | API key |
Call it yourself
Credential. A MillionVerifier API key, passed as the api query parameter.
Credits
curl "https://api.millionverifier.com/api/v3/credits?api=$MILLIONVERIFIER_API_KEY"
{ "credits": 48210, "bulk_credits": 48210, "renewing_credits": 0, "plan": 0 }Trimmed to the fields Argus reads. Values are examples.
Gotchas
- The single-verification API takes the key as api; the bulk API takes it as key.
- bulk_credits mirrors credits. Don't add them together.
- Credits never expire.
- The bad-key response on /credits isn't documented, so check for an error field as well as the status.
How MillionVerifier charges
Prepaid credit packs — 1 credit = 1 email verification, credits never expire. Cheaper per credit at higher volume; 100 free on signup.
Free allowance. 100 on signup. On signup, no card.
At zero. 402. At 0 credits verification blocks until you buy another (non-expiring) pack.
- 160 requests per second, per org.
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 MillionVerifier 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 MillionVerifier'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 millionverifier cost today, and how long until it runs out?
get_overview → millionverifier: mtd spend, burn per day, days to zero
get_request_costs { "provider": "millionverifier", "limit": 25 }
get_advisories → credits_low, spend_spike, rate_limit_low …Questions
- Does MillionVerifier have an API for its balance?
- Yes. GET https://api.millionverifier.com/api/v3/credits?api=KEY returns your credit balance.
- Can I get MillionVerifier 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 MillionVerifier credits run out?
- Requests fail with HTTP 402. At 0 credits verification blocks until you buy another (non-expiring) pack.
- What key does Argus need for MillionVerifier?
- A MillionVerifier API key, passed as the api query parameter.
Related
Pricing and limits verified 2026-10-16 against millionverifier.com/#pricing, help.millionverifier.com/email-verification-api/real-time-api, developer.millionverifier.com. Endpoints are the ones the Argus MillionVerifier connector calls.
Connect a provider key, point Claude Code or Cursor at the Argus MCP server, and ask what the last run cost.