Accounts & provisioning
Issue keys, adjust plans, inspect usage and revoke access.
Accounts
| Account | Plan | API key | Today | Status | Actions |
|---|
Issue a new key
The key is shown once. Copy it and send it to the customer.
Issued key
Requests by plan, today
Revenue by plan
Top accounts by volume
| Account | Plan | Requests | Tokens | Errors |
|---|
REST API Toolkit — usage
Client keys (auc_rest_…) on the toolkit worker — live usage vs daily quota. Manage keys in the API keys tab.
Add a custom inference provider
Any OpenAI-compatible endpoint. Models are discovered from /models automatically. Optional filter restricts which model IDs are accepted (regex, e.g. -free$).
Registered providers
| Name | Base URL | Kinds |
|---|
Upstream API keys — REST toolkit
Register with the provider, paste the key, done. You can paste multiple keys per provider — calls use the first healthy one and automatically rotate to the next when a key is exhausted or rejected. Keys are verified live before they are stored, only shown masked afterwards, and every provider still works keyless via free fallbacks.
| Provider | Used for | Register | Keys | Paste new key |
|---|
Client API keys — /api access
Every call to /api/<feature>?key=… requires one of these keys. Free keys allow 5 calls/day (quota adjustable per key). Without a valid key every path answers the identical generic 404, so path-finder tools cannot discover which endpoints exist.
| Name | Key | Plan | Quota/day | Used today | Created |
|---|
Audit log
| When | Action | Target | Detail |
|---|