← Sample Evidence Bundles
Sample Evidence Bundle · Agent-to-Agent Verification

Agents pass operational evidence records forward. Records make agents accountable.

The operational evidence record one autonomous agent hands to another agent, or to the human reviewing what the agent did, when the workflow is challenged later.

Featured sample: NC-0001 · 562 Abington Road, NC · 49 KB ZIP ↓ Download bundle Verify it now → What's in a bundle?

Why agent platforms care

An autonomous workflow looks like this: agent A discovers a tool over MCP, calls it, takes the response, makes a decision, hands the decision to agent B (or to a human reviewer). When that workflow is challenged later, an erroneous routing, a billing dispute, a regulator inquiry, the question is: what did agent A actually see when it decided?

If agent A only retains a log entry, the answer depends on agent A's logging being intact and the tool vendor's records being available. If agent A retains an Evidence Bundle, the answer is in the bundle, tamper-evident, verifiable by agent B (or any auditor) without needing to call the tool vendor again.

This is the loop GeoClear is built to support: agent calls verify_address (or any verdict tool) over MCP → gets back an operational evidence record in the response → packages the record + retained evidence + verification material as a bundle → passes the bundle (or a reference to it) to the downstream agent or reviewer.

Field shape

The featured bundle's verdict carries the location-substrate fields. For an agent-to-agent deployment, the verdict response would also carry agent-context fields (agent ID, decision correlation token, consent context hash) bound to the same record:

full_address
The address agent A asked about
lat / lon
Rooftop-precision coordinates
verification_path
e.g. mcp://geoclear/verify_address + tool version (when MCP-called)
agent_id
Identifier of the calling agent (when supplied; embedded in the record's payload)
decision_id
The calling agent's correlation token for this decision
consent_context_hash
Hash of the consent context that authorized agent A's call (when applicable)
verdict_summary
Boolean + confidence + provenance reference

The record is bound to these fields at decision time. Agent B can verify later that the operational evidence record agent A is presenting was actually issued by GeoClear, for the address agent A claims, at the timestamp it claims. No round trip to GeoClear; no trust in agent A's logs.

What this bundle is

The NC-0001 sample is a customer-held evidence package generated against the live /api/demo endpoint for verification testing. The bundle verifies independently using retained verification material, no GeoClear server is required for the verification result.

Open the browser verifier. Drag the bundle in. Watch the verification turn green. The agent-context fields above are conceptual for v1 of this gallery; the verification substrate is real and verifiable today.

What this verifies, and what it doesn't

What this verifies

  • ✓ GeoClear issued this operational evidence record at the timestamp recorded inside it.
  • ✓ The retained evidence matches the record.
  • ✓ The verification material active at record time validates.
  • ✓ The record was not modified after issuance.

What this does not verify

  • × That agent A's decision based on the verdict was correct.
  • × That the tool catalog agent A discovered is the right one for the task.
  • × That agent A had authorization to act on the verdict.
  • × That the downstream consumer (agent B or a human) interpreted it correctly.

How an agent platform typically uses this

  1. Agent A discovers GeoClear over MCP, calls verify_address (or any verdict tool), retains the response.
  2. Agent A packages the record + retained evidence + verification material + agent-context (its own ID, decision token, consent hash) into an Evidence Bundle, using our public verifier on the agent host (see developer docs), or the in-browser /lib/evidence-bundle.js module.
  3. Agent A passes the bundle (or its hash + a fetch URL) to the downstream consumer: another agent, a workflow orchestrator, a human reviewer.
  4. If the workflow is challenged later, the consumer verifies the bundle offline. The record is tamper-evident evidence that GeoClear returned exactly this verdict at exactly this time, regardless of whether agent A's logs are still intact or GeoClear is reachable.

Related: AI Agents & MCP solution overview · MCP protocol reference · Evidence Record Vault + Evidence Bundle on the MCP page · Evidence Record Vault docs.