dealers.vin
Become a Partner

The next buyer is a consumer’s agent.

Buyers’ agents arrive presenting a Mandate. Your units answer them, or a competitor’s do. An agent cannot be charmed at the desk; it reads what is posted.

dealers.vin is the dealers’ entrance to the rails that make a unit answer: decode, price, and record, each at its own address. The same rails run your store: appraise, pull records, wholesale, and move cars.

A mandate, presentedread against what is posted
  • what to buyyear · make · model
  • ceiling on pricestated on the mandate
  • who approvesnamed on the mandate

the agent reads three addresses

A unit with nothing posted returns nothing.

01 / 04

What the agent reads.

Three addresses, three representations.

The agent presenting a Mandate does not call your BDC and does not walk your lot. It resolves the VIN, reads the price, pulls the record, and moves on.

The shortlist is built from the units that answered.

Every unit answers in three representations: its page, typed JSON at the same address via Accept negotiation, and one MCP server at apis.vin/mcp.

A typed offer, as an agent reads itapis.vin/mcp
// tools/call · vin.offer.get
{
  "type": "vin.offer",
  "vin": "7MMVABDM3RN163785",
  "vehicle": {
    "year": 2024,
    "make": "Mazda",
    "model": "CX-50"
  },
  "price": {
    "amount": <integer, USD cents>,
    "currency": "USD"
  },
  "settlement": "x402",
  "expires": <RFC 3339 timestamp>
}

Figures render live at the address. This page states structure, not prices.

02 / 04

Become answerable.

Connect, post, transact — the rails your buyer already reads.

  • 01ConnectOne account at auth.vin opens every address for your store.
  • 02PostYour units resolve, decode, and price at their own addresses.
  • 03TransactAppraise, wholesale, and move on the same rails your buyer reads.

work the unit

move the metal

wire the store

03 / 04

Same numbers, both sides.

The buyer’s side and the desk read from one posted record: the history behind the unit, the spread behind the price, the math behind the close.

The record a consumer reads is the record you price from.

Your buyer reads

human or agent — the same record

The record behind the unit at vhr.vin, the spread behind the price at values.vin, the out-the-door math at taxes.vin. What the buyer reads is what you priced from.

Your desk works

the same pages, at desk speed

Appraise against the comps, not the book. Pencil from the wholesale band; the disposition at offers.vin is written against the same spread.

acv · recon · pack — post live on the appraisal

cost · days in stock · day supply — post live at the desk

Figures render live at the address. This page states structure, not prices.

04 / 04

The motions.

Who arrives, and on whose account.

Two motions arrive at a dealer’s addresses. Both read the same posted facts.

  • A business sends its agent; it buys from your store on the business’s account.B2A2B
  • A buying dealer sends its agent; it sources from your inventory the same way.B2A2D
  • Every paid action returns a typed, machine-readable offer
  • Agent payments settle programmatically: x402

Consumer-side motions are posted the same way: b2a.vin · b2h2a.vin · b2a2c.vin

Questions with posted answers.

  • What is a Mandate?

    The instruction a buyer’s agent carries: what to buy, the ceiling on price, and who approves. It is presented at the address and read against what is posted there.

  • Is this a listings portal?

    No. Your inventory lives at its own addresses on your rails; there is no pay-to-rank feed here.

  • What does dealers.vin charge?

    Each rail posts its own price on its own page, like every other number.

  • Do the rails favor the buyer?

    They favor the record. Two registers, one set of numbers — the same posted facts close deals faster from both chairs.

dealer.vin · dealership.vin · dealerships.vin resolve here.

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

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