Reference

Data API

Everything the dashboard shows is yours to pull programmatically — usage, request logs, team leaderboard, billing history and savings. Same API keys, same base URL. Every dashboard page also has an Export button for one-off JSON/CSV downloads.

Endpoint	Query params	Returns
GET/v1/data/usage	from, to, model, key_id, group_by=model\|key\|day	Daily usage aggregates: spend, requests, tokens — per model and key.
GET/v1/data/logs	from, to, model, key_id, status, limit, cursor	Per-request log rows: timestamps, model, tokens, latency, cost, status.
GET/v1/data/leaderboard	period=week\|all	Your team leaderboard: XP, weekly XP, streaks and 30-day spend per member.
GET/v1/data/transactions	from, to, type, limit, cursor	Billing history: top-ups, bonuses, promo credits and usage debits.
GET/v1/data/savings	from, to	What you saved vs list price and vs always-flagship routing.
GET/v1/models	—	Live model catalog with per-token pricing, context windows and status.

Example

team leaderboard, this week

curl "https://api.rooter.dev/v1/data/leaderboard?period=week" \
  -H "Authorization: Bearer sk-rooter-..."

{
  "period": "week",
  "members": [
    { "name": "Ada N.", "role": "member", "xp": 1210, "streak_days": 6, "spend_usd": 48.20 },
    { "name": "You",    "role": "owner",  "xp": 985,  "streak_days": 9, "spend_usd": 36.45 }
  ]
}

Notes: responses are JSON; add Accept: text/csv to any /v1/data/*endpoint for CSV. Reads are free and don't count against your credit. Keys need no extra scope — any active key can read its own account's data.