Skip to main content

Documentation

Verdictan Docs

Verdictan helps teams route, govern, and review AI traffic without building each application again. Define runtime behavior in config, run traffic through the gateway, and use the product surfaces to verify what changed.

Get startedHow it works
Quickstart

Install the CLI, create a starter config, and send your first governed request.

Config-first workflow

Use policy-config.yaml as the source of truth for policy, routing, and evidence behavior.

Policy controls

Select controls for prompt safety, PII handling, quality checks, routing, and human review.

Install the gateway

Run Verdictan locally or in your own environment and point applications at the governed endpoint.

A reliable first session​

Use the docs in the same sequence that traffic moves through the product:

  1. Install the CLI and gateway and make sure that the process is healthy.
  2. Create and validate a policy config before starting the gateway with that file.
  3. Send an authenticated request through a supported request family.
  4. Make sure that the client response is correct.
  5. Make sure that the applicable runtime evidence is correct. Use verdictan events tail for delivered request outcomes.
  6. Use History only for capture-enabled session context.
  7. Use Trail for audit chronology and Inbox for human-review work.

/healthz proves that the gateway process is running. It does not prove that a client token is authorized, a model is available, or a provider credential is correct. Use an authenticated model request for that end-to-end check.

Keep the credentials different​

CredentialUsed byPurpose
Gateway runtime API tokenverdictan gateway run --agent ...Connects the gateway runtime to the Verdictan control plane
Client API tokenApplication, SDK, or IDEAuthorizes a request sent to the gateway
Upstream provider credentialGateway provider targetAuthorizes the gateway with the selected model provider

Do not reuse the gateway runtime token as the client or provider credential. The setup and rotation workflows are different for each boundary.

Documentation​

Use the other sections of the site by job:

Configuration reference

Field-by-field reference for declarative config, providers, routes, tests, and policy settings.

CLI reference

Run the gateway, validate config, examine runtime signals, and automate rollout workflows.

Integrations

Connect OpenAI-compatible clients, provider SDKs, IDEs, and active application stacks.

Operator workflows

Follow the customer tasks for onboarding, rollout, investigation, evidence export, and spend review.

Next steps​