Enrichment

How to get your Hunter.io API usage, balance and spend programmatically

Yes. GET https://api.hunter.io/v2/account returns your plan, reset date and the searches, verifications and credits used and available. The call is free.

What the Hunter.io API exposes

SignalHunter.io
BalanceYes. GET /v2/account (searches/verifications used & available)
Spend historyNo
Cost breakdownNo
Plan and quotaYes
Cost on each responseNo
Rate-limit headersNone
CredentialAPI key

Call it yourself

Credential. A normal Hunter API key, passed as the api_key query parameter.

Account

curl "https://api.hunter.io/v2/account?api_key=$HUNTER_API_KEY"
{
  "data": {
    "plan_name": "Starter",
    "plan_level": 1,
    "reset_date": "2026-11-01",
    "requests": {
      "searches": { "used": 120, "available": 500 },
      "verifications": { "used": 40, "available": 1000 },
      "credits": { "used": 220, "available": 2000 }
    }
  }
}

Trimmed to the fields Argus reads. Values are examples.

Gotchas

  • available is the period's allowance, not what's left. Remaining is available minus used.
  • Some accounts report searches without a credits block. Argus falls back to searches.
  • Hard stop at exhaustion: 429 "usage limit reached". Credit packs are valid for three months.

How Hunter.io charges

Monthly subscription credits (1 credit = 1 email found) plus prepaid credit packs. Hard stop at exhaustion — buy a pack or upgrade.

PlanMonthly price
Free$0
Starter$49
Growth$149
Scale$299

Free allowance. 50 a month.

At zero. Hard stop — 429 "usage limit reached"; buy credit packs (3-mo validity).

  • 15 requests per second, per key. 500/min. Verifier 10/s.

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 Hunter.io 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.
  • Tracks the plan: the allowance, what's used this period, the reset date, and when you cross into overage.
  • With the SDK, itemizes each call by endpoint and prices it at Hunter.io'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 hunter cost today, and how long until it runs out?

get_overview       → hunter: mtd spend, burn per day, days to zero
get_request_costs  { "provider": "hunter", "limit": 25 }
get_advisories     → credits_low, spend_spike, rate_limit_low …

Questions

Does Hunter.io have an API for its balance?
Yes. GET https://api.hunter.io/v2/account returns your plan, reset date and the searches, verifications and credits used and available. The call is free.
Can I get Hunter.io 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 Hunter.io credits run out?
Hard stop — 429 "usage limit reached"; buy credit packs (3-mo validity).
What key does Argus need for Hunter.io?
A normal Hunter API key, passed as the api_key query parameter.

Related

Pricing and limits verified 2026-07-20 against hunter.io/pricing, hunter.io/api-documentation/v2. Endpoints are the ones the Argus Hunter.io connector calls.

Let your coding agent watch the meter.

Connect a provider key, point Claude Code or Cursor at the Argus MCP server, and ask what the last run cost.