Receipt-required execution for AI agent tool calls.
Verified MCP tool calls for compatible agent runtimes. Drop the GeoClear MCP wrapper into supported MCP servers. Capability-level integration. Agents discover the tool, request the action, and receive a customer-held operational receipt they can verify independently.
GeoClear does not certify that the AI was right. It proves whether the action followed the approved receipt path before the customer system accepted it.
No valid receipt, no high-stakes tool execution. Every agent action is gated by a real-time operational receipt the customer retains for downstream audit.
The decision problem
An autonomous agent acts on location: routes a shipment, prices a quote, triages a claim, dispatches a drone. The agent reads a JSON field and proceeds. The decision is final the moment the response is parsed, there is no human review step. When the agent's decision is later questioned, what proves what the agent actually saw?
Why unsigned location creates risk
Vendor logs are mutable. Vendor employees can edit them. The vendor can be acquired or wind down. An auditor reviewing the agent's behavior has no independent record of what the API returned at the millisecond the agent acted. 'Trust the vendor logs' fails as evidence the moment a regulator, partner, or customer asks for verification.
Signals GeoClear returns
- MCP tool catalog (verify_address, climate_risk_decision, hmda_compliance_check, drone_deliverability, full_risk_assessment)
- x402 402 Payment Required → sign → retry → 200 + result flow
- Every MCP tool response carries a customer-held operational receipt
- Per-decision receipts the agent can pass downstream
Result example
{ "tool": "climate_risk_decision", "input": { "address": "..." }, "verdict": { "composite": 0.24, "decision": "low_risk" }, "payment_tx": "base:0x7a3f…e91b" }The receipt, your verifiable record
Every MCP tool response carries a customer-held operational receipt. The agent acts on the result; the customer (or downstream agent) retains the receipt. Verification runs locally using retained verification material. No vendor-side check, no support-ticket dependency. Agent-to-agent handoffs preserve the provenance: when one agent passes a result to another, the receipt travels with it.
🛡 customer-held operational receipt industry frameworks SOC 2 Type I, Q3 2026
Business value
Closes the 'how do we audit an autonomous decision' question with a customer-held, independently verifiable answer. Makes agent-product procurement faster (no signup, x402 settles in seconds, verification is independent). Enables multi-agent workflows where each agent verifies the previous agent's result before acting.
Updated 2026-04-28 ·