Skip to main content

QuiverAI

Connect Verdictan to QuiverAI SVG generation through the native adapter contract. Applications call the local Verdictan endpoint. The gateway owns the upstream credential and applies the configured policy chain.

Use this page when​

  • You have access to QuiverAI and must route it through Verdictan.
  • You want one specified provider target. You can lint and review it before rollout.
  • You want a stable integration contract. You do not want mutable prices, context limits, or retirement dates in the config.

Prerequisites​

  • Install the verdictan CLI.
  • Get the upstream credential and an enabled model or endpoint from QuiverAI.
  • Get a Verdictan runtime API token for the gateway.
  • Get a different Verdictan client API token for client requests.
  • The --agent flow uses the runtime API token for agent-bound configuration.

Configure the provider​

Before you start the gateway, replace the replace-with-... values. The example uses the active quiverai runtime contract.

pack:
  name: quiverai-integration
  version: 1.0.0
  enabled: true
policies:
  chain:
    - prompt-injection
    - pii-detector
    - audit-logger
providers:
  targets:
    - id: quiverai-primary
      provider: quiverai
      model: "replace-with-quiverai-model-id"
      base_url: https://api.quiver.ai/v1
      secret_key_ref:
        env: VERDICTAN_QUIVERAI_API_KEY

The gateway process resolves the provider credential. Client applications do not send this credential to Verdictan.

Start and verify​

export VERDICTAN_API_TOKEN="replace-with-verdictan-api-token"
export VERDICTAN_QUIVERAI_API_KEY="replace-with-upstream-credential"

verdictan policy lint --file policy-config.yaml
verdictan gateway run \
  --agent quiverai-integration \
  --listen 127.0.0.1:41002 \
  --policy-config policy-config.yaml

VERDICTAN_API_TOKEN authenticates the gateway runtime and control-plane synchronization. Do not reuse it as the client credential.

In a different terminal, use these commands:

export VERDICTAN_CLIENT_TOKEN="replace-with-different-client-token"

curl -fsS http://127.0.0.1:41002/healthz
curl -fsS http://127.0.0.1:41002/v1/chat/completions \
  -H "Authorization: Bearer ${VERDICTAN_CLIENT_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"model":"replace-with-quiverai-model-id","messages":[{"role":"user","content":"Generate a simple monochrome circle as SVG."}]}'

/healthz verifies process liveness only. The authenticated Chat request verifies the client token, provider credential, model access, and request path.

If you did not configure a specified multi-model route, use the same model identifier in the request and target.

Active Verdictan contract​

SettingBehavior
providerquiverai
Upstream requestThe gateway sends QuiverAI SVG generation requests to /svgs/generations.
Upstream authenticationThe gateway uses a Bearer token from VERDICTAN_QUIVERAI_API_KEY.
Client endpointClient applications send requests to /v1/chat/completions on the Verdictan gateway.

The gateway maps the latest user message to QuiverAI's prompt. It includes the configured model and sends a non-streaming request.

The adapter test verifies this request translation and the SVG response shape. It does not call QuiverAI.

Select an enabled model from QuiverAI's live Models API. Complete the authenticated request above before rollout.

Transport and evidence boundary​

The adapter implements one buffered SVG generation request through the local Chat Completions route. This page does not establish streaming, tools, structured output, or other request-family support.

Model and production checks​

  • Before rollout, verify the model ID, region, endpoint availability, and account permissions in the official provider surface.
  • Add pricing, context, retention, or certification metadata only from the active provider contract.
  • Validate optional request features for the selected request family and model.
  • These features include streaming, tools, and structured output.
  • Do not make provider-wide assumptions.
  • Keep the upstream credential on the server.
  • Bind production listeners only to the specified interface.
  • Protect non-loopback listeners with authentication, network access controls, and TLS.

Next steps​