Quickstart & authentication
Install the public CLI, understand the closed access gate, and see the proposed inference request.
Read the guideAPI reference
Endpoint inventory, availability and planned authorization scopes. All /v1 routes currently return 401 for every supplied key.
Read the guidePolicies & routing configuration
Versioned rules control destinations, processing, transformations and release decisions before preferences are considered.
Read the guideGrammar definition & enforcement
A grammar is a versioned output contract. It defines allowed structure independently of whether a response sounds plausible.
Read the guideContext actions & parallel execution
Policy-approved triggers can enrich, filter or transform a flow and run additional checks before or after inference.
Read the guideManaged, server & device profiles
The same policy model applies across three execution placements. Their trust boundaries and supported hooks differ.
Read the guideTracing, provenance & insight
Connect the request, controls, inference and action graph without treating private content as telemetry.
Read the guideErrors, limits & failure behavior
A failed required control stops the protected flow. A useful error explains the next check without exposing private data.
Read the guideInteractive workspaces
Four role-specific demos expose the planned routing, action, governance and marketplace workflows.
Read the guideCLI reference
Install the public access CLI today; review the proposed workspace commands separately.
Read the guideMCP integration preview
A scoped agent interface to routing, policy explanations, synthetic action simulation and trace metadata. Production MCP access is closed.
Read the guideStart with the public surface
The CLI can be installed today. Login and signup are closed, API keys are not issued, and every /v1 endpoint returns 401. The contracts below define the proposed beta interface. They do not run an inference gateway or an action engine.
Choose the part you are building
Read Quickstart for authentication and a minimal request. Use API reference for the endpoint and scope matrix. Policies defines decision precedence and configuration. Grammars and Context actions define the two control layers. Deployment profiles and Tracing cover execution boundaries and evidence. Interactive workspaces maps all four demo roles to their contracts. CLI and MCP have dedicated reference guides.
Download the contracts
OpenAPI 3.1 and JSON Schema files are available below. Examples use placeholder model IDs and references. Production compatibility, grammar support and deployment profiles will be certified individually before access opens.
Contracts & examples
Download the preview, validate its shape locally and review the capability limits before planning an integration.
OpenAPI preview