Audience map
API clients
Create API keys, fund inference credits, select routing policies and audit routed requests.
Providers
Publish endpoints, declare deployments, price inference, run checks and follow statements.
Admins
Review accounts, legal documents, billing operations, suspensions and marketplace incidents.
Operators
Deploy, observe, diagnose and roll back the platform with internal runbooks.
Boundaries
- Public docs explain product behavior, API usage and marketplace controls.
- Internal runbooks remain repository documentation and are not exposed under public routes.
- Community deployments are visible and selectable, but automatic routing requires explicit key-level opt-in.
- Docs must not promise confidentiality, exact model identity, provider location or no-log behavior without the matching proof.