Composite Case Study: A Home-Services Agent Booking Through GeraNexus
Published 21 April 2026 · 10 min read
Label: This is a composite scenario built from the integration discussions we have had with several marketplaces. No single customer is being described. No real numbers are claimed.
The setup
“HomeHub” (composite) is a regional home-services marketplace operating in three countries with ~40,000 pros. A consumer uses a general-purpose AI assistant and asks it to find and book an emergency plumber within the next two hours.
Step 1 — Intent
The agent sends an IntentEnvelope to HomeHub’s GeraNexus endpoint. The envelope carries scoped consent (location, problem description, budget cap), a nonce and the user’s verifiable ID. HomeHub’s intent handler runs a quick eligibility check: can we source a plumber in 45 minutes for under the budget cap?
Step 2 — Commit quote
HomeHub returns a CommitQuote: price, arrival window, plumber ID, cancellation terms and a 60-second TTL. The agent shows the quote to the user, gets countersigned consent (or not), and either confirms or walks.
Step 3 — Settle
Funds move to escrow via the user’s preferred rail. For this scenario, the rail is Stripe. The escrow holds until the plumber reports job complete, the user approves, or a dispute is raised.
Step 4 — Receipt
HomeHub emits a ReceiptEnvelope signed by all three parties. The receipt hash includes the original intent so nothing can be backdated. Both the user and HomeHub keep copies.
What happens when it goes wrong
- Plumber cancels at the door. Escrow releases to the user. A partial fee to HomeHub for sourcing is documented in the original commit quote.
- Plumber does the work but it’s wrong. Dispute is raised; escrow holds until resolution; a reviewer from a GeraWitness-style network adjudicates.
- Agent went over-scope. The consent token capped spend at £150; the quote came back at £230. The intent is rejected automatically at the intent handler.
What HomeHub saved
HomeHub did not have to build agent plumbing from scratch. It implemented the four verbs, bound them to its existing booking engine and moved on. That is the point of a protocol.
See also the RFC draft and the implementation checklist.
Help shape the protocol.
Join the waitlist