Feature and Support Matrix
This matrix maps customer jobs to the documented, supported surface. A feature name in source code, a catalog entry, or a UI placeholder is not a customer support commitment.
Customer surfaces
| Surface | Status | Use it for | Important boundary |
|---|---|---|---|
| Management console | Supported | Use the console for interactive organization, agent, gateway, identity, evidence, and billing workflows. | Use the console sign-in flow. Do not copy browser credentials into API clients. |
verdictan CLI | Supported | Use the CLI for local gateway operation and scripted control-plane workflows. | Examine the authentication, region, and mutation flags for the command. |
| Public API v1 | Supported | /v1/openapi.json shows programmatic control and audit workflows. | Endpoint-specific schemas and permissions are authoritative. |
| OpenAI-compatible SDK use | Supported for documented gateway families | Point standard SDKs at the gateway base URL. | Governance coverage is different for each request family. |
Product feature coverage
| Job | Console | CLI | Public API guidance |
|---|---|---|---|
| Agents | Read Agents. | Read Agents CLI. | OpenAPI contains agent operations. |
| Gateway runtime | Read Gateway Fleet. | Read Gateway Administration. | OpenAPI contains gateway registry and telemetry operations. |
| Runtime configuration | Read Configurations. | Read Policy Lifecycle. | OpenAPI contains configuration operations. |
| IAM, users, teams, roles | Read Identity and Access. | Read IAM CLI. | OpenAPI contains identity and access operations. |
| SSO and SCIM | Read SSO and SCIM for connection, test, activation, enforcement, and provisioning tasks. | The control manifest supports organization browser-auth and SSO-discovery policy. It does not manage connections or SCIM. | OpenAPI contains the identity and access operations. |
| OAuth clients | Read OAuth Clients for registration, PKCE, consent, and bearer-token use. | — | OpenAPI contains client registry, consent, and token endpoints. |
| MFA and passkeys | Read MFA and Passkeys. | — | OpenAPI contains authentication operations. |
| Events and escalations | Use Overview and agent or gateway monitoring for Events. Use Inbox for escalations. | Read Events and Escalations. | OpenAPI contains governance operations. |
| Trail evidence | Read Trail and Audit Evidence. | Read Trail CLI. | OpenAPI contains Trail operations. |
| History | Use Console History. | Read History CLI. | OpenAPI contains History operations. |
| Usage costs and budgets | Read Usage Costs and Budgets. | Read Spend CLI. | OpenAPI contains spend and budget operations. |
| Resource tags | Read Resource Tags. | Control manifests support agent tags. A generic verdictan tag command is not available. | OpenAPI contains resource-tag operations. |
| Context Fabric | Use agent and gateway detail views. | Use gateway and config workflows. | Read Context Fabric Lifecycle and Context Fabric Work Reuse. |
| Secrets | Use Console Secrets. | Read Secret and Credential Management. | OpenAPI contains secret operations. |
| Region discovery | Use console locality fields. | Read Regions CLI. | OpenAPI contains region operations. |
An empty CLI cell means that this site does not document an equivalent customer workflow. It does not authorize use of an undocumented route.
Gateway request families
| Family | Public route | Active boundary |
|---|---|---|
| Chat Completions | POST /v1/chat/completions | Supports OpenAI-compatible JSON or SSE. Executes the documented input and output policy path. |
| Responses | POST /v1/responses | Supports Responses-style JSON or SSE. Executes the documented input and output policy path. |
| Anthropic Messages shape | POST /v1/messages | This route uses shared access, input, tool, output, and audit stages with an Anthropic-shaped body. |
| Embeddings | POST /v1/embeddings | Gives the vector-generation path. Use a documented embeddings provider. |
| Audio transcription | POST /v1/audio/transcriptions | This route translates speech to text. |
| Audio speech | POST /v1/audio/speech | This route returns binary text-to-speech audio. |
| Moderation | POST /v1/moderations | The runtime applies route-specific behavior. |
| Models | GET /v1/models and GET /v1/models/:model_id | These routes give published model discovery. |
| WebSocket | /v1/chat/completions/ws, /v1/responses/ws | Applies request and response policy to complete text frames. Rejects binary frames and malformed JSON-like text. |
| Published-host MCP | GET /mcp, POST /mcp | These routes give the published agent-hostname MCP surface and its documented capability limits. |
Before you select a route, read Runtime Request Families. Do not infer policy parity when request bodies have the same fields.
Documented live provider setup guides
The gateway implements the adapters or OpenAI-compatible contracts for these customer setup guides:
- AIML API
- Azure OpenAI
- Cerebras
- Cloudera AI Inference
- Cloudflare AI Gateway
- Databricks
- DeepSeek
- Fireworks AI
- Google AI Studio
- Google Vertex AI
- Groq
- Hugging Face
- Mistral
- OpenAI
- OpenRouter
- Perplexity
- QuiverAI
- Replicate
- Amazon SageMaker
- Together AI
- Vercel AI Gateway
- Voyage AI
- xAI
Use the specified page in Integrations. Follow its request-family, credential, endpoint, and production caveats. Do not use this list as authoritative guidance.
The catalog entry is not live verification. Validate the specified provider, region, model, credential, request family, streaming mode, and necessary policy path before production use.
SDK guidance
For production application integration, use a standard OpenAI-compatible client against a supported gateway request family:
- Read Node.js Workflow.
- Read Python Workflow.
- Read Java and Spring Workflow.
- Read .NET Workflow.
How to verify a claimed capability
Before you use a feature:
- Find it in this matrix and its owning guide.
- Make sure that
/v1/openapi.jsonor the activeverdictan --helpcontains the operation. - Validate the specified environment and credentials.
- Test a representative success case.
- Test the specified deny or failure case.
- Verify active state and evidence in the owning surface.
If public docs and public discovery do not contain the feature, identify it as unsupported. Do not infer support from a previous README, generated type, catalog count, or undocumented route.
Next steps
- Read Public API Basics.
- Read Runtime Request Families.
- Read CLI Command Groups.
- Read Troubleshooting.