Keys & budgets

Each key can have its own guardrails. The dashboard exposes budgets and model allowlists when you create a key:

• Budget — a hard spend cap for the key. Requests fail once it's reached.
• Allowed models — restrict a key to specific models (e.g. only cheap ones for a side project).
• Promotional-account limits — accounts using only promotional credit are automatically capped at 10 RPM and 50,000 TPM per key until the first paid top-up. Funded PAYG keys have no RouterPlex product-level RPM or TPM default.

Per-request logs (time, model, tokens, cost) are available per key in the dashboard under API Keys → Logs.

Recommended setup for agents #

Coding agents and autonomous tools can burn tokens quickly. For each agent:

1. Create a dedicated key named after the tool (cursor, claude-code, openclaw…).
2. Set a budget you're comfortable losing to a runaway loop.
3. Optionally allowlist only the models that tool should use.

That way one misbehaving tool can never spend more than its own cap, and your usage logs stay attributable per tool.