Argus API
Your product runs on other people's APIs, and every one of them is a meter — tokens, credits, requests, rate limits. Argus reads them all into one place. This API is how you read Argus.
Spend, balances, runway, and per-request costs over REST.
Push per-call telemetry from your app — with the SDK or one signed POST.
Let agents watch your meters through the MCP server.
Make your first request
Everything lives under https://api.argus.town. Grab an API key from Settings → API keys in your dashboard, then ask for the overview — the same numbers the dashboard's front page shows:
curl https://api.argus.town/overview \ -H "Authorization: Bearer argus_mcp_..."
You'll get back every meter Argus is watching for your workspace:
{
"success": true,
"data": {
"total_mtd_usd": 438.12,
"total_projected_usd": 754.53,
"providers": [
{
"connection": { "id": "…", "provider": "openrouter", "status": "active" },
"metrics": {
"balance_usd": 96.72,
"burn_per_day": 7.09,
"days_to_zero": 13.6,
"mtd_spend_usd": 179.71,
"rate_limit_headroom_pct": 82,
"accuracy": "exact"
},
"advisories": []
}
// … one entry per provider
],
"daily_spend": [ { "day": "2026-07-19", "by_provider": { "openrouter": 12.4 } } ]
}
}That's the shape of the whole API: bearer key in, snake_case JSON out, always wrapped in { success, data }. Next: how credentials work.