Native signals
Send OTLP spans, logs and metrics alongside application-owned rows from SDKs and gateway metadata.
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.
Wyrd brings traces, logs, metrics, and application evidence together with verification results, across AI/ML services—not just agent applications.
Send OTLP spans, logs and metrics alongside application-owned rows from SDKs and gateway metadata.
Use run_id and exact Card versions to connect evidence from the same request or workflow.
Use read-only SQL or MCP to investigate traces, verdicts, model usage and custom datasets.
The diagram uses Wyrd’s documented Bifrost architecture: Gate authorizes requests, Scribe ingests, Oracle queries, and Forge manages background compaction and retention.
Authenticated writes enter through Gate, then Scribe acknowledges and publishes them.
Query published Parquet and the current live tail with read-only SQL.
Manage file compaction and retention in the background.
A green HTTP status reveals very little about internal steps. Join the recorded run to a requirement-level check when one is configured.
Inspect OTLP spans, logs, and application records that share a run_id.
When gateway capture is enabled, inspect caller, requested model, outcome and token usage.
Join the run’s evidence to a Verifier result and the exact requirement and version checked.