Where the money waits.
Money on a car deal usually moves in the dark: a wire sent on trust, conditions unwritten, release at the other side’s convenience. This page posts the escrowed-funds face of the deal (held balance, release conditions, settlement events), each with value, source, and timestamp on platform.do financial rails. Both sides read the same page. Reading it is free. No account.
An agent settling for you under a Mandate reads this same face: what it brings back is the posted state you are reading now.
JM3KFBXY1S0597748
2025 Mazda CX-5
- Held balanceFunds received into escrow for this deal · value · source · timestamp, never “in process”Posts live
- Release conditionsWhat must post before funds move (title conveyed · delivery confirmed · signatures captured): one condition per line, met or unmet, each naming the event that meets ittitle.vin/JM3KFBXY1S0597748transport.vin/JM3KFBXY1S0597748Met or unmet
- EventsReceived · conditioned · released: each dated, sourced, and typedAs they happen
- ReleasedFunds out, to whom the order names: the release posts back from the one order as an eventbuy.vin/JM3KFBXY1S0597748Posts live
Held minus released: the balance waiting, posted as a state, not a status call.
- escrow.vin read$0 · every VIN, every visit · no account
Figures render live at the address. This page states structure, not balances: a slot the record cannot fill says so in words, never an estimate.
The money railplatform.do financial rails hold the funds; settlement runs inside the one order at buy.vin. This address attests the rail and transacts nothing.
Look up. Read. Settle.
The Held-Funds Plan: three steps, and the third one is the close.
- 01Look upA VIN at escrow.vin/{VIN}: the deal’s funds face assembles from the record (what came in, what holds it, what lets it go). Reading it is free, no account.
- 02ReadHeld balance, release conditions, and settlement events, each posted with value, source, and timestamp. A condition is a line, not a vibe: a condition not yet met posts as unmet, with what would meet it named. “In process” is not a state on this page.
- 03SettleInside the one order at buy.vin: settlement is that order’s act, and the release posts back to this record as an event, dated and sourced. You are one step from the close.
- Postedescrow.vin read: $0 · every VIN, every visit · no account
- The railThis address holds no money and moves none. platform.do financial rails hold the funds; settlement runs inside the one order at buy.vin; what happens there posts back here as events: received, conditioned, released.
- AgentsThe same funds face as typed JSON at the same address, via Accept negotiation.
One page, both sides of the wire.
The same page, the same lines, the same timestamps, read from opposite sides of the wire.
That is the point.
Sending the funds
You wire against conditions, not against trust
The wire lands in the held balance and posts with source and timestamp the moment it does. Release waits on lines you can read (title conveyed, delivery confirmed, signatures captured), each a typed event the record either carries or does not. Nobody’s convenience is a condition.
The held balance · conditions, met or unmet · the release
Waiting on the funds
The money is posted before anything conveys
The seller reads the same page: the balance is posted, not promised, and the conditions name exactly what conveys before funds move. Sign the title over against a posted balance, not a screenshot of one, not an inbox that answers first.
The held balance · the release event · the payee
Questions with posted answers.
Where is my money?
In the held-balance slot, posted with value, source, and timestamp, or the slot says in words that the record does not carry it. Never “in process.”
What releases it?
The conditions, one per line. Each names the event that meets it (title conveyed posts from the paper lane at title.vin, delivery confirmed posts from transport.vin), and each event posts when it happens, dated and sourced.
Does escrow.vin hold the funds?
No. The rail holds them (platform.do financial rails), and settlement runs inside the one order at buy.vin. This address attests the rail and transacts nothing: it is the deal’s funds face, not its counterparty.
Both sides see this?
The same page, the same lines, the same timestamps. A buyer, a seller, and any agent settling under a Mandate read one funds face: that is the point.
What does a read cost?
$0, posted like every other number (escrow.vin read: $0). Every VIN, every visit, no account.
The release carries.
The funds face is one face of the deal. The other addresses read the same seventeen characters, and the close settles inside one order.
- Do the deal
- buy.vinSettlement runs inside the one order: the release posts back here as an event
- commerce.vinThe transaction layer: every line of the deal at its own address, one total
- Fund · deliver · convey
- financing.vinThe financed portion lands in the same held balance: rates posted for the VIN
- transport.vinRelease can condition on delivery: transport posts the delivered event
- title.vinTitle conveyed: the paper-lane event a release condition names
The free faces values.vin · specs.vin · listings.vin · sticker.vin, read free before any paid report; the record deepens at vhr.vin when the deal needs it.
For the agent you send.
The agent reads the same record you do.
Same two routes, three representations: the numbers never differ between them.
- Motionsb2a2cAn agent acting for a consumer: everything it does survives being shown to them afterwardb2a2bAgents brokering between businesses: Mandate presented, fee disclosed, settlement three-way
- 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.
- The gateNo gate on this door's two routes: keyless reads, no account. Gated actions elsewhere return a typed OFFER or a NEEDS_HUMAN handoff, never a dead end.