Can a notary or licensed producer sell their reserved act to AI agents as an API?

Yes. If you are a notary, an insurance producer, an attorney, a CPA, or an appraiser, the act the law reserves for your credential can become an addressable, credentialed, per-act-paid leaf inside an AI agent's flow. The agent walks the whole deal — reads the record, settles the priced steps under its Mandate ceiling, posts every move to the deal ledger — and when it reaches the one moment that requires your license, it hands you a signed, expiring link to exactly that act. You appear, you perform the reserved act, the signed artifact returns to the deal record, and you are paid per act. You show up for the single moment the law reserves for you, not the whole afternoon around it. That is the inversion: delegation without dispossession.

This is the complete answer. What follows is how the leaf actually works, what you are and are not committing to when you type your act onto the rails, and where it already runs — because a licensed professional deciding whether to expose a reserved act deserves the mechanics, not a pitch.

What the desk does today, and what a leaf changes

Today the desk holds the human hostage for the whole transaction when the law needs them for 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. That arrangement is not a feature of your credential — it is a feature of the desk. Your notarization takes a minute; the wait, the intake, the shuffle of paper, and the scheduling around it take the afternoon.

A Handoff separates the reserved act from the afternoon. The agent does everything up to your act and everything after it. You are inserted at exactly the load-bearing moment, and you are paid for the act, on the deal record, at the moment you perform it. The reserved act is the same; what changes is that you stop selling afternoons at the desk's pace and start selling the one thing the law actually reserves for you — priced per act, settled where it is posted.

The leaf, as a shape

When an agent reaches your step, it receives a typed NEEDS_HUMAN Handoff — url · signed shortUrl · pollUrl · expiresAt. You receive the signed, expiring shortUrl. It opens the one act and nothing else: no dashboard to learn, no account to build, no adjacent actions to worry about. You perform the reserved act — sign, notarize, consent, bind — and the signed artifact posts to the deal record. The agent, which has been polling pollUrl per RFC 8628 (GET, side-effect-free), resumes the instant your approval lands.

Three properties make the leaf safe to sell:

• Typed — the envelope is url · signed shortUrl · pollUrl · expiresAt. A gate that returns anything else is a conformance failure, so your act is never the place a flow silently mangles.
• Credentialed — the reserved act performs as an fn:Human leaf in the Function graph, and your credential is verified at the membrane (auth.vin / id.org.ai) before the act runs. You are not lending your license to an automation; you are performing the act yourself, verified, at the moment it is needed.
• Per-act — payment posts per act on the deal record, and fees settle where they are posted. You are paid for the reserved act, not for being on call for the afternoon around it.

What you are — and are not — committing to

The scope is narrow by design: the reserved act only. The agent orchestrates everything up to — never through — the reserved act. It does not perform your act, does not hold your credential, and does not proceed past your step without your signed artifact. Your credential is verified at the membrane, the act is performed against the record, the signed artifact is returned, and payment posts per act. That is the full extent of the commitment.

This matters because the alternative — the one every licensed professional is right to fear — is that a machine somewhere types your act on your behalf and the credential becomes theater. The Handoff is the opposite arrangement. It is precisely because the law reserves the act for you that the flow is built to stop and wait for you, typed, every time. The Handoff points are the moments you appear in person in your own story. You are not being automated away; you are being addressed directly, at exactly the moment your license is the thing the deal cannot proceed without.

Where reserved acts already run as leaves

This is a shipped shape, not a slide. Two live specimens show reserved acts on the rails:

• On insure.vin, Bind is a licensed-producer reserved act — the supply leaf and the demand-side consent sit on one record. Quotes render as evidence statements (premium · carrier · coverage · timestamp), and the bind — the act only a licensed producer can perform — is the credentialed leaf inside that record.
• On financing.vin, the FCRA consent and the application signature are Handoffs — the agent shops the rates and prices the fees, and the human authorizes the credit pull and signs the application. The written instruction the law requires before a credit pull is exactly the reserved moment, typed and handed off.

Both run on the same plug-in surface every Handoff uses — one key, one MCP server, the reserved act paid per act on the deal record. There is no take rate on the door itself: b2h2a.vin renders the description free and keyless; the transaction is the per-act leaf, and fees settle where they are posted.

The choice in front of a licensed professional is not whether AI agents will reach these moments — they already do. It is whether your reserved act meets them as a typed, credentialed, per-act-paid leaf, or whether the moment the law reserves for you is left to whoever types it first. Delegation without dispossession: you appear for exactly the act that is yours, paid per act, on the record — and the deal shows both sides.