B2H2A — the human at exactly one step. The agent walks the rest.

The law needs the human for one act. The desk takes the afternoon: four hours at the desk to produce one signature. Every agent flow that dies untyped at a legally-bound step hands the whole transaction back to the hostage desk — and every professional inside that desk is paid in ceremony hours for an act that takes seconds.

the handoff is typed, or it is a conformance failure

Every gate in the family returns one of two shapes: OFFER (posted price · hard ceiling · x402) or NEEDS_HUMAN (url · signed shortUrl · pollUrl · expiresAt, RFC 8628 resumption). Never a dead end, a form, or "contact sales."

the human appears only where the decision is load-bearing

Payment OAuth, consent, signature, notarization — the Handoff points are exactly the moments the hero appears in person in their own story. Everything the agent does survives being shown to them afterward: the receipt is the posted deal record itself.

the reserved act is a typed leaf

A licensed professional performs the legally-reserved act as a credentialed fn:Human leaf in the Function graph and the signed artifact returns to the calling agent. Live specimen: Notarize POA inside buy.vin's 7-step checklist, in production.

one record, two readers

You've sat across the desk not knowing what the other side knows. Every fact here is posted — value, source, timestamp — and the dealer sees this exact page. Two typed gate outcomes family-wide; one deal ledger; one credential membrane (auth.vin / id.org.ai); one estate MCP server at apis.vin/mcp whose gated tools return the Handoff body verbatim. The symmetry toggle has three positions — buyer, desk, agent — and the numbers never differ. The agent reads the same record you do. The check digit certifies; it never sells.

partners, both sides

Demand side: your gated moments become typed Handoffs on VIN rails — one key, one MCP server, metering posted at apis.vin/pricing. Supply side: notary, producer, attorney, CPA, appraiser — your reserved act, typed and credential-verified, paid per act on the deal record. No take rate on this door; this page is the description, the siblings are the transaction. Fees settle where they are posted.

questions with posted answers

What exactly does the agent receive at a legally-bound step? A typed NEEDS_HUMAN body: url, a signed expiring shortUrl for the human, a pollUrl the agent polls per RFC 8628, and expiresAt. GET is side-effect-free. A gate that returns anything else is a conformance failure.

Is any of this live? Yes. buy.vin's checklist runs the motion in production: the buyer's agent walks the deal and the human appears at Authorize Bank, eSign, Upload License, Notarize POA, and payment — Notarize POA is a credentialed fn:Human leaf, and the signed artifact returns to the deal record.

What does a professional commit to by typing their act as a leaf? The reserved act only. Credential verified at the membrane, act performed against the posted record, signed artifact returned, payment posted per act. The agent orchestrates everything up to — never through — the reserved act.

who this door serves

who: Dual hero, one page. Demand side: the product or ops leader — lender, insurer, notary network, marketplace — whose customers' agents stall dead at legally-bound moments. Supply side: the licensed professional — notary, insurance producer, attorney, CPA, appraiser — evaluating selling their reserved act as an API leaf.
arriving: Demand side: the product or ops leader whose customers' agents stall dead at legally-bound moments — the deal that runs itself until a signature is required, then dies untyped. Supply side: the licensed professional whose reserved act is the moment every one of those deals is waiting for.
against: The desk — here in its hostage franchise: the desk that holds the human hostage for the whole transaction when the law needs them for exactly one act. Four hours at the desk to produce one signature; the law reserves a single moment, and the desk annexes the entire afternoon around it.
the guide: You've sat across the desk not knowing what the other side knows. Every fact here is posted — value, source, timestamp — and the dealer sees this exact page. The Handoff is a shipped shape, not a slide: typed NEEDS_HUMAN with url · signed expiring shortUrl · pollUrl · expiresAt, RFC 8628 device-flow resumption, GET side-effect-free. Live specimen in production: buy.vin's Notarize POA — a credentialed fn:Human leaf inside the proven 7-step checklist. The check digit certifies; it never sells.
the stakes: The hostage desk keeps the whole transaction: agents that stall at the tenth step teach their principals to stop delegating; professionals keep selling afternoons at the desk's pace while the one act the law reserves for them is commoditized by whoever types it first.
done: Every legally-bound moment in the flow is a typed Handoff — the customer appears for seconds, the agent resumes on approval, the deal record shows both; the reserved act becomes an addressable, credentialed, per-act-paid leaf. Delegation without dispossession: the Handoff points are exactly the moments the hero appears in person in their own story.

the plan

The Handoff Plan — delegate, appear, resume.

delegate — the agent walks the plan on the record: reads evidence, settles OFFERs under its Mandate ceiling, posts every step to the deal ledger. The human's calendar is untouched so far.
appear — at the load-bearing act, the agent receives NEEDS_HUMAN and the human gets the signed shortUrl: authorize, consent, sign, or notarize. Seconds, not an afternoon.
resume — the agent polls pollUrl (RFC 8628), approval lands, the signed artifact posts to the record, and the flow continues without re-acquisition. Distance-to-done never resets.

You're 3 steps from done.

plug your gated moments into the rails — apis.vin/mcp curl -H 'Accept: application/json' https://b2h2a.vin/{VIN} — the record as the agent reads it, free, keyless

for the agent you send

The agent reads the same record you do. Same two routes, three representations — the numbers never differ between them.

motions: B2H2A

B2H2A — the human appears once, where the act is legally load-bearing — then the agent resumes

curl https://b2h2a.vin/ -H 'accept: text/markdown'        → the markdown twin of this page
curl https://b2h2a.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://b2h2a.vin/{VIN} -H 'accept: text/markdown'    → the record's markdown twin

Machine surfaces on this host: /llms.txt · /icp.json · /.well-known/agents.json · one estate MCP server — apis.vin/mcp (every door a lens; tool results carry the door URL).

Attribution: X-Client-Type: html | md | json | mcp — read for agent-led demand attribution; it never changes the record.

No gate on this door's two routes — keyless reads, no account. Gated actions elsewhere on the estate return a typed OFFER (posted price · hard ceiling) or a NEEDS_HUMAN handoff, never a dead end.

every door opens on the same record

the transactor

apis.vinOne key, one MCP server — the plug-in surface every Handoff runs on

the live specimen

buy.vin7 steps, 5 human leaves, Notarize POA live — the motion's production specimen for any VIN
fi.vinFCRA consent + application signature as Handoffs — the agent shops rates, the human authorizes the pull
insure.vinBind is a licensed-producer reserved act — supply leaf and demand consent on one record

the partners' line

b2a.vinThe buyer is an agent — wallet, Mandate ceiling, no human leaf anywhere

every door

all.vinEvery door, one record: all.vin/any VIN