← Products
Tier 1 · The Platform · The Engine

GeoClear™ Receipt Engine.

Policy-bound Authorization and Denial receipts issued at execution time. Customer-side enforcement, customer-held proof, offline verification.

How the signing works → Connect over MCP Verify a receipt
Real-time operational receipt flow Six-stage diagram: agent action triggers receipt engine; policy and evidence check; operational receipt issued; target system verifies the receipt; customer retains receipt for later audit. Agent action machine triggers a decision 01 Receipt engine GeoClear receives the action 02 Policy + evidence check policy + evidence evaluated 03 Operational receipt durable artifact issued 04 Target verifies target accepts or rejects 05 Customer audit retained for later review 06 Real-time operational receipt flow Six-stage diagram: agent action triggers receipt engine; policy and evidence check; operational receipt issued; target system verifies the receipt; customer retains receipt for later audit. Agent action machine triggers a decision 01 Receipt engine GeoClear receives the action 02 Policy + evidence check policy + evidence evaluated 03 Operational receipt durable artifact issued 04 Target verifies target accepts or rejects 05 Customer audit retained for later review 06
Action → policy + evidence check → operational receipt → target verifies → customer audit.

What the Receipt Engine does

The Receipt Engine is the horizontal layer underneath every product GeoClear ships. For eligible GeoClear verdict responses:

The issuance substrate is decision-domain-agnostic: the same trust boundary issues operational receipts for an address verification, a flood determination, a credit decision, or an autonomous-routing verdict. The Receipt Engine doesn’t care what the decision is, it cares that the decision is bound to a tamper-evident operational receipt the customer can verify later.

Reference Implementations

Each Tier 2 product is a proof the Receipt Engine works for a specific decision domain. The Receipt Engine itself is decision-domain-agnostic.

The framing rule: GeoClear is an operational-receipt platform for machine decisions. We’ve built the Tier 2 products as the blueprints for how we issue tamper-evident operational receipts in specific decision domains. If we can issue an operational receipt for a flood verdict, we can apply the same receipt architecture to other machine decisions.

Technical anchors

The Receipt Engine’s technical surfaces, for developer + procurement audiences who need the depth:

What this Receipt Engine 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.

This is the right boundary. The Receipt Engine makes the verification path verifiable on the customer’s terms without overclaiming what cryptography can prove about the world.

Try it

The Receipt Engine issues operational receipts for eligible GeoClear verdict responses across every public API surface, and produces receipts customers can retain. Three ways to see it:

Companion: Operational Receipts, the portable operational evidence the Receipt Engine produces. Together, the two Tier 1 products are the platform.