Capabilities and boundaries
Designed for decisions you can explain.
Each capability below describes its operating scope so technical and commercial teams can evaluate the same proposition.
011. Authenticate and scope
A request arrives through a documented endpoint. The API key establishes its organisation, project and allowed model, supplier and region scope.
- Credential validation
- Organisation and project context
- Endpoint-specific input validation
022. Apply policy and select
Direct model requests retain the caller's choice. Opt-in chat autorouting considers eligible models using configured constraints and available fit, cost and health signals.
- Policy eligibility before routing
- Regional and supplier restrictions retained
- No routing outside configured lanes
033. Execute and observe
The request is sent to an eligible hosted, direct-provider or integrated infrastructure lane, then metered for operational and billing records.
- Current: supported managed and direct-provider lanes
- Assisted: customer-owned GPU onboarding and integration
- Response, usage and route evidence returned to the platform