Usage and credits

Base URL https://api.tilion.dev. Every request needs Authorization: Bearer $TILION_API_KEY.

Usage

GET /v1/usage

{
  "tier": "pro",
  "month": "2026-07",
  "usage":     { "actions": 1420, "egress_bytes": 830472192, "browser_seconds": 41230, "sessions": 203, "captcha_solves": 11 },
  "limits":    { "actions": 10000, "egress_bytes": 10737418240, "browser_seconds": 1800000, "captcha_solves": 500 },
  "remaining": { "actions": 8580,  "egress_bytes": 9906946048,  "browser_seconds": 1758770, "captcha_solves": 489 },
  "concurrency_limit": 50,
  "premium_egress": true,
  "overage_allowed": true,
  "enforced": true
}

null in limits or remaining means unlimited on your plan. Read remaining here rather than waiting for a 402.

Credits

Metered usage past the monthly allowance draws on a credit balance:

GET /v1/credits

{
  "owner": "...",
  "balance": 24998.99,
  "enforced": true,
  "cost": { "action": 1.0, "captcha": 20.0, "egress_mb": 1.0, "session": 0.0 }
}

cost is the per-unit price of each metered thing. An empty wallet returns 402 with the machine-readable code insufficient_credits.

Redeeming a credit code

POST /v1/credits/redeem

The body is {"code": "..."} and a successful redeem returns the granted amount and the new balance:

{ "ok": true, "granted": 5000, "balance": 29998.99 }

A 409 means the code was already redeemed.

Get started

MCP

Sessions

Fetch & jobs

Content

Agent & tasks

Live view & recordings

Account

Reference

Usage and credits

Usage

Credits

Redeeming a credit code

​Usage

​Credits

​Redeeming a credit code

Usage

Credits

Redeeming a credit code