Public receipt proof

Receipt Explorer

Human-readable proof fetched from the authoritative receipt API.

Loading receipt…

Back to APIVouch

Receipt JSON

—

Proof-of-outcome infrastructure

One goal. Many APIs.
One verified outcome.

APIVouch calls independent providers, rejects broken or disagreeing results, honors cost and latency limits, and returns proof an autonomous agent can verify.

Consensus routingConstraint-boundTamper-evident receipts

verified-outcome.receipt

$ agent → apivouch.resolve(goal)

Providers attempted   4
Schema rejected       Legacy Ship
Unavailable           Offline Express
Independent agreement 2 / 2

OUTCOME               VERIFIED
Selected provider     Beacon Logistics
Quoted call price     $0.003
Evidence receipt      sha256:91c4…

Live independent proof

Three APIs. One usable truth.

Resolve the current USD→EUR reference rate across three independently operated public data origins. APIVouch requires agreement, enforces runtime constraints, and binds the result to a content-addressed receipt.

Agent goal→3 live origins→Evidence gate→Receipt

—Verdict

—Selected

—Agreement

—Quoted call price

Receipt awaiting verification

—

Deterministic safety evidence

Chaos & Refusal Lab

Deterministic in-process safety evidence — no live-provider claim. Each scenario runs the real verified-outcome path with fixed in-process providers, a fixed fixture timestamp (not live freshness), and isolated lab storage that never evicts production evidence. Each stored receipt is proven canonical JSON round-trip exactly equal on retrieval. A correct UNVERIFIED refusal is a passing safety result, not a broken test.

Agent-ready endpoint

Connect once. Verify every call.

The product-level MCP server exposes verified-outcome routing to compatible agents. Generate project-specific tools in the provider lab below.

Generate MCP tools →Read API docs

Product MCP endpoint

—

Build a trusted provider

Inspect any public OpenAPI 3.x or Swagger 2.0 contract, collect runtime evidence, and generate callable MCP tools. No API credentials are stored.

Project name

OpenAPI URL

or see the complete loop

Paste JSON or upload a JSON/YAML file

OpenAPI JSON

File (.json, .yaml, .yml)

Project

Evidence workspace

01 · InspectContract diagnostics

02 · ProveBounded live calls

03 · AgentizeEvidence-bound contract

04 · ConnectDynamic MCP tools

Before

—

Source contract readiness

After

—

Evidence-bound contract

Coverage

0/0

Endpoints with live evidence

Endpoint evidence

Operation	Method & path	Live state	Avg latency	Shape drift

Score breakdown

Actionable findings

Server-owned Exhaustiveness Gate

APIVouch starts at page one and collects the evidence itself. The caller cannot submit record counts, cursors, snapshots, or page evidence.

Collection operation

Claim

Expected count

Numeric field for min/max

Candidate ID (optional)

Non-pagination arguments (JSON)

Proof result

Run a proof to see the verdict, certificate, and bounded evidence trail.

Generated tools

Generate the agent contract to create tools.

MCP endpoint

Stateless Streamable HTTP / JSON-RPC. Read-only tools can be called immediately.

Project endpoint

—

Initialize

Legacy client example

—

Capability boundary

Automatic live probes and generated calls are restricted to GET, HEAD, and OPTIONS. State-changing operations remain visible in the contract but return CONFIRMATION_REQUIRED; APIVouch never silently converts them to GET.