The product in a paragraph

GeraNexus is a protocol. It extends Model Context Protocol (MCP) from read-only queries into transactional territory. An AI agent using GeraNexus can negotiate price, book a slot, pay via escrow, cancel within policy, open a dispute, and verify completion — across any service that implements the spec. Our reference implementation wraps the twenty-two live Gera verticals; we are publishing the spec under a permissive licence so any marketplace can adopt it.

The thesis, in four paragraphs

First: agents are already here. Anthropic launched the Model Context Protocol in November 2024 with read-only tool integrations. By late 2025 Anthropic, OpenAI, Google and Microsoft had all shipped agent products that can call external tools. What is missing is a commerce layer — agents can query the world but cannot yet transact at scale.

Second: the glue that HTTP provided for human-to- server traffic is now needed for agent-to-service traffic. Without a standard, every integration is bespoke, every dispute is manual, and every service has to build agent support from scratch.

Third: supply-side liquidity is the hardest thing to bootstrap. A protocol with no live services is a PDF. Gera Services already operates twenty-two verticals across 50+ countries — healthcare, home services, commerce, food, transport, payments, rentals, insurance, farming, learning, jobs — which is exactly the supply-side liquidity a transactional protocol needs to prove itself before asking others to adopt it.

Fourth: if agent commerce is a 2027–2030 shift, the protocol has to be open and the economics have to be fair. A 2% take on agent-initiated transactions is enough to fund the platform without distorting adoption. Proprietary rivals that charge 15–30% will not win; the web would not be the web if HTTP had a tax.

What GeraNexus is not

Not an MCP replacement. It sits on top.
Not an LLM provider. Use whatever model you like.
Not a closed marketplace. The spec is public; third-party implementers welcome.
Not shipping today. The public spec is drafting; the reference implementation wraps live Gera MCPs; launch is late 2026.

Timeline

Q2 2026 — public spec v0.1, reference implementation for five Gera verticals.
Q4 2026 — spec v0.5, external pilots with two non-Gera marketplaces.
2027 — spec v1.0, open governance, third-party certification programme.
2028–2030 — cross-protocol interoperability with MCP, A2A, and whatever else emerges.

How to follow along

We publish spec drafts to the research section, open questions go up on this blog, and the waitlist is for integrators who want first access to the reference implementation. If you are building anywhere near this space — an agent, a marketplace, a payments rail, a trust layer — we want to hear from you.