A neutral, append-only settlement-and-receipt ledger for agent-to-business transactions. Every booking, purchase, or commitment resolves into a Gera-signed, verifiable receipt — verdict, evidence, source, escrow state, dispute hook — queryable by any party later.
Working MCP tools today — signed, verifiable receipts · still gauging demand for the hosted + insured tiers.
Live in the Gera trust-layer MCP as issue_receipt + verify_receipt: once an agent acts, it mints an Ed25519-signed receipt of what happened — optionally linking the Vouch attestation and Agent Mandate it acted under — and any party verifies it independently. This completes the chain: verify → vouch → mandate → receipt, every step signed. The hosted, queryable append-only ledger + dispute resolution is the roadmap.
Tools an agent can call:
issue_receipt — mint a signed proof-of-action receiptverify_receipt — confirm Gera recorded the action, unaltered (fails closed)Call it now — two live ways:
# stdio (any MCP client — Claude Desktop, Cursor, …)
npx -y @gera-services/mcp-gera-verify
# hosted HTTP (Streamable MCP)
POST https://gera-verify-mcp-production.up.railway.app/mcpOpen source in the Gera monorepo at packages/mcp-gera-verify (real FSA/CQC data, Ed25519-signed attestations). Both the npm package and the hosted endpoint are live today; a branded verify-mcp.gera.services domain is next — tell us if you want early access.
When agents transact at scale, disputes need a neutral, tamper-evident record of what was agreed and what happened.
An agent records a commitment to the ledger.
The counterparty confirms; the entry becomes immutable.
Any party queries the signed history to settle disputes.
Almost entirely machine-to-machine: buyer-side and supply-side agents write and confirm commitments.
The accumulated immutable history becomes the authoritative record — a network effect that compounds with every receipt.
Register your interest and we will let you know when it goes live. No spam.