Users & API access
Manage access while keeping wallet balances intact.
Deactivating a user revokes their key. Reactivation requires a new key. Requests already accepted may finish.
| User | Access | Wallets | API key | Actions |
|---|
Create test user
Generate / rotate API key
Copy the returned key now. It will not be displayed again.
Set upstream pool
Allocate / return credits
Admin accounts
Owner manages admins, pools and credits. Operator manages users and API keys. Viewer reads records and exports. Keep at least one active Owner.
| ID | Role | Active | Action |
|---|
Admin password & sessions
Change your password using your current password. Owners can reset another admin by ID. Password changes revoke other sessions.
Users, wallets & history
Inspect stored records without changing balances. All dates and times are UTC.
API usage contains persisted billing records. API request activity is separate best-effort tracking from v0.9, including rejected requests; unknown users were rejected before authentication. No prompts, keys or response bodies are stored.
Admin activity
Successful data changes recorded from v0.5 onward. Times are UTC.
Actor IDs identify individual admins; older records retain shared-admin. Login attempts and rejected requests are not included.
| Time (UTC) | Action | User | Details | Actor | Source IP |
|---|
Activity maintenance
Remove up to 1,000 API activity rows older than 30 days and 1,000 rate-limit counters older than 24 hours per run. Wallets, usage records, ledger and admin audit are preserved. Cleanup is manual.
Current records
Loading...