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

See what happened.
Verify what it means.

Collect OpenTelemetry signals, model activity (when capture is enabled), and service records in Bifrost. Observability supplies the evidence; independent Wyrd Verifiers check whether the service actually followed its requirements.

OPENTELEMETRYSQL-QUERYABLE BIFROSTVERSIONED EVIDENCE
BIFROST / QUERYRUN-LEVEL EVIDENCE
TRACES21
LOGS8
VERDICTS2
SELECT run_id, outcome, verdict
FROM bifrost.gateway.calls
JOIN bifrost.verification.results
ON matching run_id
CORRELATED RUN / 8b42…
TRACES
21 spans
GATEWAY
1 call
VERIFY
failed
ILLUSTRATIVE QUERY · VALUES NOT FROM LIVE DATA
01 / ONE DATA PLANE

More than telemetry.
Evidence you can verify.

Wyrd brings traces, logs, metrics, and application evidence together with verification results, across AI/ML services—not just agent applications.

01 / INGEST

Native signals

Send OTLP spans, logs and metrics alongside application-owned rows from SDKs and gateway metadata.

02 / CORRELATE

Run context

Use run_id and exact Card versions to connect evidence from the same request or workflow.

03 / QUERY

Ask precise questions

Use read-only SQL or MCP to investigate traces, verdicts, model usage and custom datasets.

02 / INSIDE BIFROST

One evidence plane.
Four dedicated parts.

The diagram uses Wyrd’s documented Bifrost architecture: Gate authorizes requests, Scribe ingests, Oracle queries, and Forge manages background compaction and retention.

01
Gate + Scribe

Authenticated writes enter through Gate, then Scribe acknowledges and publishes them.

02
Oracle

Query published Parquet and the current live tail with read-only SQL.

03
Forge

Manage file compaction and retention in the background.

FROM WYRD DOCUMENTATION / ARCHITECTUREBIFROST PARTS
WYRD SERVERYour servicerun.observe.*Bifrost clientinsert · SQLOpenTelemetryOTLP exportAgentsMCP bifrost.queryGateauth · routingScribeingest · live tailOracledistributed queryForgecompaction · retentionObject storageIceberg · ParquetPostgrestable catalog
Bifrost structure and component names adapted from the Wyrd “Bifrost parts” documentation diagram.
03 / QUESTIONS YOU CAN ANSWER

From successful response
to verified behavior.

A green HTTP status reveals very little about internal steps. Join the recorded run to a requirement-level check when one is configured.

RUNTIME

What did the service do?

Inspect OTLP spans, logs, and application records that share a run_id.

MODEL ACTIVITY

Which model was called?

When gateway capture is enabled, inspect caller, requested model, outcome and token usage.

VERIFICATION

Did it meet the rule?

Join the run’s evidence to a Verifier result and the exact requirement and version checked.

BUILT ON WYRD / INDEPENDENT VERIFICATION ENGINE

The shared foundation.
Not another silo.

Observability records what happened. Verification uses the relevant observations to decide whether an explicit requirement was met.

01 / DECLARE

Declare

Define what must happen—for example, an eligibility check before a payment.

02 / OBSERVE

Observe

Record the service run, trace spans, relevant data and version identifiers.

03 / VERIFY

Verify

Run a trace or other suitable Verifier and retain the verdict with its evidence.

REQUIREMENT → EVIDENCE → VERDICT

Bifrost makes the evidence queryable; collecting telemetry alone does not assert that the workflow passed verification.

Explore the verification engine ↗
OBSERVE / QUERY / VERIFY

Keep the traces.
And the truth behind them.