b2a2d.vin
Become a partner

Motion door · the partners’ line · held

Embed the capability.
The membrane comes with it.

Embed.Carry.Finish.

The credential wall is the desk at wholesale: the reserved act that breaks a downstream build mid-flow and hard-codes “have your customer call a licensed someone” into the middle of software. Every flow it fractures is a deal that leaves your product at the step that pays.

For the downstream builder: DMS vendors, dealer-website providers, marketplaces, and vertical SaaS embedding VIN capability, where a third party is the ultimate beneficiary. This door is held: it is posted as parked until the embed payload surfaces land.

2025 Mazda CX-5 · check digit 1 · verified

The membrane, act by actb2a2d.vin/JM3KFBXY1S0597748

JM3KFBXY1S0597748

2025 Mazda CX-5

  • notaryfn:Human, credentialed: the signed artifact returns to your flowPlatform leaf
  • f&ifn:Human, credentialed: the platform performs it on your behalfPlatform leaf
  • insurance-bindfn:Human, credentialed: the bind posts back to your flowPlatform leaf
  • everything elseThe rest of the payload (decode, value, recalls, listing): yours to callOpen to your build

Every act in the payload is flagged open or routes to a platform leaf. Reserved acts answer with the typed NEEDS_HUMAN Handoff, exactly as your build would receive it.

The membrane travels.

When your downstream hits a reserved act, the platform's own credentialed leaf performs it on your behalf.

When your downstream hits a notary, F&I, or insurance-binding act, the platform routes to its own credentialed fn:Human leaf on your behalf: the signed artifact returns to your flow.

You’ve shipped the flow that stops at the credential wall. Every act here is posted: which are open to your build, which are reserved, and where the reserved ones route. Reserved acts return typed NEEDS_HUMAN Handoffs, never a dead end, never contact-sales, routed to platform credentialed leaves (notary · F&I · insurance-bind).

Nothing to license, nothing to hide from your counsel.

The flow, finishedOne reserved act
  1. 01Your build callsDecode, value, recalls, listing: the payload, open to your buildOpen
  2. 02A reserved act is reachedNotary · F&I · insurance-bind: the step the credential wall would breakNEEDS_HUMAN
  3. 03The platform's leaf performs itfn:Human, credentialed, on your behalf: nothing for you to licensePlatform leaf
  4. 04The signed artifact returnsIt posts back to your flow; your customer never leaves your softwareYour flow

The Embed Plan’s own steps, drawn: the structure of the motion, not a session.

The dependency is the distribution.

The agent reads the same record you do.

An agent mid-task writes the call into code, and the build carries it from then on: B2A’s distribution and B2H2A’s wholesale channel fused into one motion. One platform MCP and one SDK as the dependency shapes; every embedded call metered and priced on the page at apis.vin.

A reserved act, typedNEEDS_HUMAN
1// a reserved act, as your downstream build receives it
2// it routes to the platform leaf: fn:Human, credentialed
3{
4 "type": "NEEDS_HUMAN",
5 "handoff": {
6 "url": <the human twin of this exact step>,
7 "pollUrl": <your flow resumes here>,
8 "expiresAt": <RFC 3339 timestamp>
9 }
10}
The dependency viewapis.vin/mcp
1# as it would sit committed in a downstream build
2# an agent wrote this line; the build carries it now
3
4decode_vin({ "vin": "JM3KFBXY1S0597748" })
5 -> https://apis.vin/mcp
6
7# the unit price, posted at apis.vin
8# every embedded call metered and priced on the page

The channel is already live.

The motion runs in production today.

listings.vin’s ADF lead export is this motion in production: VIN capability disappearing into dealer CRMs and DMS builds today, posted, metered, attributed.

The Embed Plan: embed, carry, finish
  1. 01EmbedThe call goes into your build: the platform MCP tool or the SDK method, keyed at apis.vin. An agent can commit this step for you.
  2. 02CarryThe membrane ships with the dependency: reserved acts are typed in the responses, each flagged with where it routes. Nothing to license, nothing to hide from your counsel.
  3. 03FinishYour product completes flows it legally never could alone; the platform's leaf signs, the artifact posts back to your flow, your customer never leaves your software. The deal stays yours.

Distance to done: 3 steps.

The key, the SDK, the platform MCP: a key mints at POST apis.vin/keys. Wiring is an endpoint, not a form.

Get the key at apis.vin

The motions.

Five motions, one grammar: who the principal is, and where the human appears.

The buyers’ motions put an agent in front of a seller. The partners’ line is the other side: the businesses agents trade with, and the products that carry the capability downstream.

Held names stay quiet marks until they go live: b2a2b.vin and b2a2d.vin post the motion now and transact nothing.

Posted.

What this page is, where the keys and prices live, what this door settles.

  • This pageSells a motion, not a meter. b2a2d.vin has no take rate.
  • The railsThe keys, prices, and settlement live at apis.vin, and every number this page cites is posted there or on the sibling door that owns it.
  • This doorHeld: it goes live when the embed payload surfaces (platform MCP and ADF-style export) land.

Questions with posted answers.

What can my product legally finish?

Everything up to the membrane, plus every reserved act the platform’s credentialed leaves perform on your behalf. Each act in the payload is flagged “open” or “routes to platform leaf”.

Where do I get keys and pricing?

apis.vin. This door describes the motion; apis.vin transacts it: one hop, no duplicated job.

Is this live anywhere today?

Yes: listings.vin’s ADF lead export ships VIN capability into dealer CRMs now. This door goes live when the embed payload surfaces (platform MCP and ADF-style export) land; until then it is posted as parked.

The motion is one face of the record.

The other addresses read the same seventeen characters.

For the agent you send.

The agent reads the same record you do.

Same two routes, three representations: the numbers never differ between them.

Three representationsb2a2d.vin
1curl https://b2a2d.vin/ -H 'accept: text/markdown'
2 # the markdown twin of this page
3curl https://b2a2d.vin/{VIN} -H 'accept: application/json'
4 # the record as typed evidence objects
5curl https://b2a2d.vin/{VIN} -H 'accept: text/markdown'
6 # the record's markdown twin
On this host
  • Motionsb2a2dThe capability embeds downstream: reserved acts route back to a credentialed human leaf
  • Machine surfaces/llms.txt/icp.json/.well-known/agents.json
  • One MCP serverapis.vin/mcp serves the whole platform: every door’s tools in one server, each result carrying its door’s URL.
  • AttributionX-Client-Type: html | md | json | mcp names which reader arrived; it never changes the record.