What a Receipt is
An Operational Receipt is the portable, tamper-evident proof of what GeoClear returned at decision time. Two views, same artifact:
The header view
- An operational receipt returned on every signed response (
/api/*,/v1/*,/v2/*,/mcp*); header name documented in developer docs. - Browser verify: drag any bundle into /security/offline-verifier.
- Server-side verify: see developer docs for the public verifier package.
The bundle view
- Customer-held evidence package.
- Includes the operational receipt, retained operational evidence, verification material, supporting references, and independent review tooling.
- Self-contained; verifies independently on the customer's own infrastructure.
- File-by-file breakdown: /docs/receipt-vault.
Why a common receipt profile matters
Receipts are decision-domain-agnostic. The same operational-receipt format covers:
- A flood determination (the Flood Verdicts bundle).
- A location verification (the Locations bundle).
- A credit / underwriting / AI-driven Yes/No (the Decisions bundle).
The Receipt profile is stable across all three Tier 2 products, one verification model, one receipt profile, one customer-held audit artifact. Adding a new vertical doesn’t fork the receipt protocol; it just produces another bundle in the same shape.
Governance and openness
GeoClear, Inc. publishes the Open Operational Receipt Profile under permissive terms and intends for the Profile to evolve toward neutral, multi-stakeholder governance as adoption grows. Specific governance milestones will be established in collaboration with adopters, contributors, and standards bodies.
The intent is clear: this is an evidence layer, not a proprietary lock-in. Customers hold the receipts. Verifiers run offline. Reference verifiers are open-source. The receipt format itself is on a trajectory toward governance independent of any single vendor.
Verification surfaces
- Receipt Vault docsRetention guidance for customer-held receipts.
- MCP protocol referenceHow autonomous agents fetch and pass receipts.
- Developer integration guideDetailed verification material, trust-boundary topology, and verifier reference, available to qualified procurement and security reviewers under NDA.
What this proves, and what it doesn’t
What this proves
- GeoClear signed this verdict at the receipt’s timestamp.
- The retained operational evidence matches the issued receipt.
- The retained verification material verifies the receipt.
- The receipt was not modified after signing.
What this does not prove
- That every upstream dataset was perfect.
- Full legal or regulatory compliance.
- That a downstream business decision was risk-free.
- That the physical world matched the recorded values.
Try it
Companion: GeoClear Receipt Engine, the issuance layer that produces these Receipts. Together, the two Tier 1 products are the platform.