Skip to main content

Capability Status

This page is generated from user-docs/static/capabilities.json. It is the public status surface for capabilities that remain limited, preview, planned, or otherwise outside the narrow Phase 1 workload boundary.

Current capability status

CapabilityRequest familyTransportDeployment modeAvailabilityLast verification dateEvidence tierLimitations
CAP-ACCESS-LIVEchat_completions, responses, messagesjson, sseself_hosted, hosted, saasplannedNot yet verifiedmock_verifiedUnified Access live enforcement is not reconciled for the Phase 1 public scope. Public copy must not imply live wallet reservation or settlement.
CAP-BUDGET-LIVEchat_completions, responses, messagesjson, sseself_hosted, hosted, saasplannedNot yet verifiedmock_verifiedLive hard-budget enforcement is not Phase 1 GA and must stay off primary surfaces. Capability status may describe the current budget-policy state only with limitations.
CAP-GW-AUDIT-DURABILITYchat_completions, responsesjson, sseself_hosted, air_gappedlimitedNot yet verifiedmock_verifiedDecision evidence is available for governed gateway traffic, but immutable every-decision durability remains a tracked gap. Phase 1 capability status must disclose current WAL, ingestion, and continuity limits. No primary surface may imply complete Trail durability until later phases close the gap.
CAP-GW-CHAT-POLICYchat_completionsjson, sseself_hosted, air_gappedlimitedNot yet verifiedmock_verifiedPhase 1 covers the documented Chat Completions gateway path only. Anthropic Messages, WebSocket, and MCP parity remain outside the initial wedge. GA remains blocked until live-provider and post-deploy evidence is current.
CAP-GW-RESPONSES-POLICYresponsesjson, sseself_hosted, air_gappedlimitedNot yet verifiedmock_verifiedPhase 1 covers the documented Responses gateway path only. Streaming parity is limited to the documented JSON and SSE flow. GA remains blocked until live-provider and post-deploy evidence is current.
CAP-KMS-HOSTEDkms_hostedinternalhosted, saasplannedNot yet verifiedmock_verifiedHosted external KMS integration remains blocked until region, rotation, and readiness evidence exists. Primary surfaces must not imply hosted KMS support.
CAP-MCP-ACTION-POLICYmcpstreamable_httpself_hosted, hostedpreviewNot yet verifiedmock_verifiedLive MCP tool-action governance remains preview-only and must not be marketed as GA.
CAP-MESSAGES-POLICYmessagesjson, sseself_hosted, air_gappedpreviewNot yet verifiedmock_verifiedAnthropic Messages policy parity remains outside the initial GA wedge.
CAP-OAUTH-BEARERoauth_bearerhttp, browserhosted, saaspreviewNot yet verifiedmock_verifiedOAuth bearer access remains preview-only and must not be marketed as a supported public bearer flow.
CAP-ROUTER-AUTOchat_completions, responses, messagesjson, sseself_hosted, hosted, saasplannedNot yet verifiedmock_verifiedAutomatic model routing remains non-GA and must stay off primary surfaces until deterministic selection evidence exists.
CAP-SCIMscimhttphosted, saasplannedNot yet verifiedmock_verifiedSCIM provisioning remains non-GA and unadvertised on primary surfaces until provisioning, deprovisioning, and rotation lanes pass.
CAP-SIEM-STREAMsiem_deliveryhttpself_hosted, hosted, saaspreviewNot yet verifiedmock_verifiedDurable SIEM outbox delivery and replay guarantees are not Phase 1 GA. Primary surfaces must not imply production-ready SIEM streaming.
CAP-SSO-OIDCbrowser_sign_inbrowser, redirecthosted, saasplannedNot yet verifiedmock_verifiedOIDC SSO remains non-GA and unadvertised on primary surfaces until browser, API, and recovery lanes pass.
CAP-SSO-SAMLbrowser_sign_inbrowser, redirecthosted, saasplannedNot yet verifiedmock_verifiedSAML SSO remains non-GA and unadvertised on primary surfaces until browser, API, and recovery lanes pass.
CAP-WS-FRAME-POLICYchat_completions_ws, responses_wswebsocketself_hosted, air_gappedplannedNot yet verifiedmock_verifiedPer-frame governance and binary-frame rejection remain planned. Primary surfaces must not imply WebSocket policy parity.

How to read this page

  • ga means the manifest-declared positive, negative, and freshness gates are all satisfied.
  • beta means a fresh sandbox or runtime verification exists, but the capability is still outside the GA contract.
  • limited, preview, and planned stay here until the owning phase closes their gaps.

Next steps