How to get your Crustdata API usage, balance and spend programmatically
What the Crustdata API exposes
| Signal | Crustdata |
|---|---|
| Balance | Yes. GET /account/credits (account.credits, recurring_credits, refresh_date) |
| Spend history | No |
| Cost breakdown | No |
| Plan and quota | Yes |
| 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 Crustdata API key.
Credits
curl https://api.crustdata.com/account/credits \ -H "Authorization: Bearer $CRUSTDATA_API_KEY" \ -H "x-api-version: 2025-11-01"
{
"account": {
"credits": 1834.27,
"recurring_credits": 2500,
"recurring_credits_frequency": "monthly",
"recurring_credits_refresh_date": "2026-11-01"
}
}Trimmed to the fields Argus reads. Values are examples.
Gotchas
- Leave out x-api-version and you get a 400.
- Credits are fractional: a search result costs about 0.03, a real-time profile enrichment up to 7.
- Credits are valid for six months. At zero you get 402 insufficient_credits.
How Crustdata charges
Fractional credit pool (search ~0.03/result, real-time enrich up to 7/profile); credits valid 6 months with optional monthly recurring grant. Contact-priced tiers.
| Plan | Monthly price |
|---|---|
| Real-time API | Contact sales |
| Enterprise / Flat-file | Contact sales |
At zero. 402 insufficient_credits (error.type); credits valid 6 months from purchase.
- 15 requests per minute, per key. Per-endpoint RPM varies by account; headers x-ratelimit-*.
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 Crustdata 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 Crustdata'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 crustdata cost today, and how long until it runs out?
get_overview → crustdata: mtd spend, burn per day, days to zero
get_request_costs { "provider": "crustdata", "limit": 25 }
get_advisories → credits_low, spend_spike, rate_limit_low …Questions
- Does Crustdata have an API for its balance?
- Yes. GET https://api.crustdata.com/account/credits returns your credit balance and the recurring grant with its refresh date. It's free, and it needs the x-api-version header.
- Can I get Crustdata 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 Crustdata credits run out?
- 402 insufficient_credits (error.type); credits valid 6 months from purchase.
- What key does Argus need for Crustdata?
- A normal Crustdata API key.
Related
Pricing and limits verified 2026-07-21 against docs.crustdata.com/general/credits, docs.crustdata.com/general/pricing, docs.crustdata.com/openapi-specs/2025-11-01/introduction, crustdata.com/pricing. Endpoints are the ones the Argus Crustdata connector calls.
Connect a provider key, point Claude Code or Cursor at the Argus MCP server, and ask what the last run cost.