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.

API

Spend, balances, runway and per-request costs over REST, plus the writes.

Send

Push per-call telemetry from your app — with the SDK or one signed POST.

Ask

Let agents watch your meters through the MCP server.

Make your first request

Everything lives under https://api.argus.town. Create an API key (type api) in Settings → API keys, then ask for the summary — the same numbers the dashboard's front page shows:

curl https://api.argus.town/v1/summary \
  -H "Authorization: Bearer argus_api_..."

You'll get back every meter Argus is watching for your project:

{
  "object": "summary",
  "totals": { "mtd_spend_usd": 438.12, "projected_month_end_usd": 754.53 },
  "connections": [
    {
      "object": "connection",
      "id": "conn_…",
      "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"
      }
      // … one entry per connection
    }
  ],
  "advisories": []
}

That's the shape of the whole API: bearer key in, snake_case JSON out, the resource itself as the body. Lists page with next_cursor and failures carry a stable error.code. Daily history is GET /v1/spend. Next: how credentials work.

Authentication →