Real-time verification, built for your stackApache 2.0 Wyrd / Hosted from $15/mo
BOHMIAN / AGENT & WORKFLOW VERIFICATION

Verify the workflow.
Not just the output.

From autonomous agents and support workflows to payment APIs and ML services, Wyrd checks requirements against what actually ran. Keep your existing execution framework; add independent, versioned verification across steps and outcomes.

AGENTS & APISML & DATA SERVICESMULTI-STEP RUNS
SERVICE / SUPPORT-AGENTRELEASE 1.8.0
SERVICE CARDsupport-deskExact version · declared components
COMPONENTsupport-agent
POLICYrefund-policy
MODELopenai/gpt-4o
run_id: 8b42…observedverified
INDEPENDENT VERIFIERevidence attached
✓ PASSED

Refund response complied with the declared policy.

requirement: policy-004 · cited policy check
ILLUSTRATIVE RUNS · REQUIREMENTS AND EVIDENCE ARE CONFIGURED
01 / VERIFICATION FOR AI/ML SERVICES AND WORKFLOWS

The whole execution.
Not just the output.

Declare components and obligations for an agent, API or ML workflow; preserve real execution evidence; then check the relevant requirements independently.

01 / DECLARE

Version the system

Register Service, Agent, Model, Data and Verifier Cards with exact versions and relationships.

02 / OBSERVE

See what ran

Capture a run across service steps, model calls, custom data, and other relevant operations.

03 / VERIFY

Verify what matters

Use assertions, trace checks, code, or cited model judges for the requirements that apply.

02 / THE TECHNICAL FOUNDATION

Your system does the work.
Wyrd checks the requirements.

Wyrd is not an agent orchestrator or general workflow runner. Your application or framework handles execution; Wyrd records evidence and evaluates explicit, versioned requirements for the relevant Service or component.

01
Declare

Bind a versioned Verifier to a Service, Agent or other declared component.

02
Observe

Record relevant data under the same run_id and exact component version.

03
Verify

Ask for a synchronous verdict, submit an asynchronous check, or schedule a drift check.

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
Diagram adapted from the Wyrd docs’ “Where Wyrd sits in your stack” graphic.
03 / THE PRACTICAL PATH

Any service.
One verification model.

Use the same foundation for agent responses, API decisions, and ML/data pipelines—each with different requirements and the evidence those checks need.

AGENT WORKFLOWS

Verify agent decisions

Check that an agent followed policy and used required tools before responding.

APIS & SERVICES

Verify required steps

Check that a payment or fulfillment service followed its business process.

ML PIPELINES

Verify data and model logic

Check that features, metrics and evaluation logic satisfy versioned requirements.

BUILT ON WYRD / INDEPENDENT VERIFICATION ENGINE

The shared foundation.
Not another silo.

Wyrd can verify many kinds of Service. The workflow still runs in your own application or agent framework.

01 / DECLARE

Declare

Version the Service and its applicable obligations, including component-specific requirements.

02 / OBSERVE

Observe

Record the actual sequence, data, model activity and other evidence appropriate to that Service.

03 / VERIFY

Verify

Run a matching Verifier and tie its verdict to the exact Service and Verifier versions.

REQUIREMENT → EVIDENCE → VERDICT

Agent orchestration remains in your stack. Wyrd provides independent checks and stores evidence-backed results.

Explore the verification engine ↗
START WITH ONE REQUIREMENT

Agents, APIs, ML.
One standard of evidence.