The Agentic Commerce Protocol
GeraNexus is an open protocol that lets AI agents transact across real-world services on behalf of users. One spec. Book a doctor, hire a plumber, order food, hail a car, sign a lease, settle payment — all from any AI agent, across 22 real-world verticals.
Why this matters in 2030
In three to four years, the primary interface to the internet is not a website, not an app, and not a chat window. It is a personal AI agent that acts on your behalf. Your phone’s AI books your doctor. Your AR glasses identify what you’re looking at and order it. Your voice assistant handles everything by conversation.
In that world, every agent needs a way to transact — book, pay, dispute, refund — across real-world services. Today there is no standard protocol. Whoever publishes and operationalises the first one becomes the Stripe of agent commerce: foundational infrastructure, recurring transaction fees, protocol-level lock-in.
GeraNexus is that protocol. The moat isn’t the spec itself — it’s the real-world supply that sits behind it. Gera already runs doctors, plumbers, restaurants, rides, rentals, and payments across 60+ countries. The protocol is the fastest way for the agent economy to reach that supply.
How it works
Service publishes a descriptor
Every service exposes /.well-known/gera-nexus.json declaring the protocol actions it supports — negotiate, book, pay, cancel, refund, dispute, verify-completion.
Agent discovers and speaks
Any AI agent can discover the service via MCP, read the descriptor, and call signed, structured actions. The spec standardises request format, error codes, idempotency, and retry semantics.
Escrow, completion, audit
Payment is held in escrow until verify-completion. Signed audit trails are written for every step. Disputes route to a neutral arbitration layer. Refunds and rollbacks are first-class actions, not afterthoughts.
Integrated with Gera’s 22 products
GeraNexus is born with real-world supply. Every Gera vertical ships its protocol descriptor from day one. That means an AI agent built against GeraNexus can, on day one, reach:
- Heliodoc — book telemedicine consultations
- Wrkdo — dispatch plumbers, electricians, cleaners
- GeraEats — place food orders
- GeraRide — hail rides and deliveries
- Agorivo — purchase from marketplace sellers
- GeraCash — settle payments and track balances
- GeraRent — view listings and sign leases
- GeraSure — quote and bind microinsurance
- GeraFarm — order agricultural supplies
- GeraLearn — enrol in courses
- GeraJobs — apply to roles
- GeraCoins — earn and redeem loyalty balance
Frequently asked questions
- What exactly is GeraNexus?
- GeraNexus is an open protocol specification that lets AI agents transact across real-world services. Today, protocols like MCP let agents read data. GeraNexus lets them book, pay, cancel, refund, dispute, and verify service delivery — with standardized error handling, escrow, and audit trails.
- How is this different from MCP?
- MCP is query-only. GeraNexus is transactional. Think of MCP as read access and GeraNexus as read plus write plus payments plus dispute resolution. GeraNexus treats MCP as its underlying discovery layer and adds a commerce surface on top.
- Which AI agents will support it?
- Any agent that speaks HTTP and can follow a spec. Our first reference integrations target Claude (via MCP), ChatGPT apps, Gemini extensions, and any agent framework that can sign a structured action payload.
- Do I need to be a Gera product to implement it?
- No. The spec is open. Any service provider can publish a /.well-known/gera-nexus.json descriptor and become reachable by agents. Gera ships the reference implementation on top of its 22 verticals — healthcare, home services, food, ride-hailing, payments, and more — but adoption is not limited to Gera.
- How does payment and escrow work?
- GeraNexus defines a pluggable settlement layer. The reference implementation uses GeraCash and Stripe, with escrow held until the verify-completion step. Services can integrate any PSP that supports authorise, capture, and refund semantics.
- What about safety and user consent?
- Every agent-initiated action can be routed through a human-in-the-loop review layer (see GeraWitness). Protocol-level signing, audit trails, and per-user spend limits are part of the spec, not optional add-ons.
- When can I start building against it?
- Join the waitlist. We are publishing the draft spec and reference implementation in phases through 2026. Early partners get priority support and input on the spec.