b2a2dvin

Embed the capability. The membrane comes with it.

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.

the membrane travels

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.

the dependency is the distribution

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. The agent reads the same record you do.

the channel is already live

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

every act, posted

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); one estate MCP and one SDK as the dependency shapes; every embedded call metered and priced on the page at apis.vin. The check digit certifies; it never sells.

posted

This page sells a motion, not a meter. b2a2d.vin has no take rate; the 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.

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 (estate MCP + ADF-style export) land; until then it is posted as parked.

who this door serves

who
The downstream builder: DMS vendors, dealer-website providers, marketplaces, and vertical SaaS embedding VIN capability into their own product — where a third party (their dealer, their dealer's customer) is the ultimate beneficiary.
arriving
The downstream builder — a DMS vendor, dealer-website provider, marketplace, or vertical SaaS — embedding VIN capability into their own product, where a third party is the ultimate beneficiary. Their customer's customer is the one the flow must finish for.
against
The desk — here in its embed franchise: the credential wall. The reserved act that breaks a downstream build mid-flow, forcing "have your customer call a licensed someone" into the middle of software — how the desk taxes at wholesale.
the guide
You've shipped the flow that stops at the credential wall — the screen that says "a licensed representative will contact your customer." Every act here is posted: which are open to your build, which are reserved, and where the reserved ones route. listings.vin's ADF lead export is this motion already live: VIN capability disappearing into dealer CRMs today. Reserved acts return NEEDS_HUMAN Handoffs that route to platform fn:Human credentialed leaves — notary · F&I · insurance-bind — the signed artifact returning to your downstream's flow. The check digit certifies; it never sells.
the stakes
Keep shipping flows with the hole in the middle: "contact a licensed someone" hard-coded into your product, your customer's deal walking out of your software at exactly the step that pays, and a competitor whose embed carries the membrane finishing what yours can't.
done
Your product finishes flows it legally never could alone — reserved acts route to platform leaves on your behalf and the signed artifact returns to your flow. From integrator-with-a-gap to the platform whose embed is whole.

the plan

The Embed Plan — embed, carry, finish.
  1. embed — the call goes into your build: the estate MCP tool or the SDK method, keyed at apis.vin. An agent can commit this step for you.
  2. carry — the 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. finish — your 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.
You're 3 steps from done.

apis.vin/keys — the key, the SDK, the estate MCPb2a2d.vin/{VIN} — the embed payload for a real VIN, rendered

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: B2A2D

curl https://b2a2d.vin/ -H 'accept: text/markdown'        → the markdown twin of this page
curl https://b2a2d.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://b2a2d.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.

every door opens on the same record

the transactor
  • apis.vinThe record as a response — every call priced on the page; keys, SDK, the estate MCP
the live channel
  • listings.vinThe ADF embed channel — live in dealer CRMs today
the partners' line
  • b2a2b.vinAgent-brokered trade the same dealer zones carry — Mandate presented, fee disclosed
every door
  • all.vinPart of the Vin family — all.vin/any VIN: which faces hold records for this VIN