Admin areas
Admin responsibilities
- Keep model access aligned with organization policy.
- Review usage trends before raising quotas.
- Rotate secrets when an application owner changes.
- Remove access that is no longer needed.
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Manage users, models, API keys, quotas, and usage in Pinter.
| Area | Route | Use for |
|---|---|---|
| Users | /admin/users | Manage users and access mappings. |
| Models | /admin/models | Configure available model providers and model entries. |
| Virtual models | /admin/virtual-models | Configure fallback chains and round-robin model groups. |
| API keys | /admin/api-keys | Manage platform API keys. |
| Applications | /admin/applications | Manage app credentials and application access. |
| Quotas | /admin/quotas | Set usage limits. |
| Budget requests | /admin/budget-requests | Review quota or budget increase requests. |
| Usage | /admin/usage | Monitor usage across the platform. |
| Marketplace approvals | /admin/marketplace-approvals | Review submitted marketplace items. |