Real-time verification, built for your stackApache 2.0 Wyrd / Hosted from $15/mo
BOHMIAN / LLM GATEWAY

Control the model call.
Verify the surrounding workflow.

Route supported models through a caller-authorized gateway with server-held provider keys. Enable capture to connect model-call metadata to the same service evidence Wyrd can use for independent verification.

SERVER-HELD KEYSPER-CALL IDENTITYOPT-IN CAPTURE
MODEL REQUEST / ROUTECONTROLLED CALL
YOUR APPLICATIONAgent / serviceWyrd access token
→
WYRD GATEWAYAuthorized requestProvider key held server-side
◇ SECURE CREDENTIAL
→
DEPLOYMENTS
OpenAI
Anthropic
Gemini
RECORD WHEN ENABLEDCaller · model · outcome · tokens
↘ Bifrost
SOURCE MODEL NAMES SHOWN AS EXAMPLES · WYRD DOES NOT HOST MODELS
01 / CONTROL AT THE FRONT DOOR

One controlled path.
A richer evidence trail.

The gateway is not itself a universal safety or verification check. It proxies model calls, enforces caller permissions, and records activity under the configured capture policy.

01 / SECRETS

Keys stay server-side

Store provider credentials as managed secrets and reference them through named provider deployments.

02 / AUTH

Know who called

Wyrd authorizes each caller before routing the request through the configured deployment.

03 / SIGNALS

Capture what matters

Enable metadata capture for caller, model, outcome, and token usage without retaining prompts or replies.

02 / HOW REQUESTS MOVE

Call models
through Wyrd.

Your app sends a request to the Wyrd endpoint using its Wyrd token. The gateway resolves the deployment and signs the upstream call with the provider credential. Model replies return to the app.

01
Configure

Store the provider credential and create a named deployment.

02
Call

Use the supported model endpoint with a name such as openai/gpt-4o.

03
Record

Opt into capture, then query call metadata in Bifrost when rows become available.

FROM WYRD DOCUMENTATION / ARCHITECTUREWYRD IN YOUR STACK
WYRD SERVERCIwyrd CLIYour appPython · Rust · TypeScript SDKCoding agentMCPDeclarationsServices · Verifiers · versionsVerification enginechecks · verdictsBifrosttelemetry · custom data · evidencePostgresdeclarations · coordinationObject storageevidence · artifacts
Wyrd server placement from documentation; the gateway is one routed capability of the server, not a model host.
03 / BUILT TO BE EXPLICIT

Control what is stored.

Capture is intentionally opt-in. When enabled, its records can be joined to service traces and Verifier results without storing prompt or reply payloads in metadata-only mode.

CAPTURE OFF BY DEFAULT

No implicit logging

A new tenant records no gateway calls until a capture policy is enabled.

METADATA MODE

Usage without payloads

Choose metadata capture with no prompt or completion payload fields.

MULTIPLE DEPLOYMENTS

Keys per deployment

Give teams or workloads separate named deployments and server-held provider credentials.

BUILT ON WYRD / INDEPENDENT VERIFICATION ENGINE

The shared foundation.
Not another silo.

The gateway creates an authorized path and, with capture enabled, useful model-call evidence. Verification is a separate check against declared rules.

01 / DECLARE

Declare

Declare the surrounding service and what its responses or decisions must satisfy.

02 / OBSERVE

Observe

Capture authorized caller, model, outcome and usage metadata; record any additional evidence needed.

03 / VERIFY

Verify

Run an applicable Verifier over the relevant service evidence, if configured.

REQUIREMENT → EVIDENCE → VERDICT

Gateway capture is off by default for a new tenant. Model routing and recording alone do not produce a verification verdict.

Explore the verification engine ↗
CONNECT / AUTHORIZE / RECORD

Keep the key.
Keep the context.