# explore.vin
> Every address in the Vin estate, and what it does — the family's domain map, one walkable tree: pillar, lane, door, mark.

explore.vin is the Vin estate's domain map: the ratified hierarchy — Data, Services, Commerce, AI, and the Platform beneath them — rendered as one nested tree. Every live door links; every held name renders as a plain mark with its placement and its why. One search field filters the tree; the markdown twin is the sitemap itself.

Motions: B2A
Routes: GET / (this document's page) · GET /{VIN} (the record for one vehicle)
Representations: text/html · text/markdown · application/json (Accept header; same URL)
Evidence: every field posts value · source · timestamp · verification state; empty states are typed EMPTY, invalid VINs are typed INVALID_VIN — never a faked 200.
Agent surface: one estate MCP server — https://apis.vin/mcp (all .vin doors are lenses over one spine; tools: decode_vin, vehicle_history, market_value, window_sticker, out_the_door_price, open_recalls, search_listings, cash_offer, transport_quote, finance_prequal, insurance_quote, start_purchase)
Gates: typed OFFER (posted price, hard ceiling, x402) or NEEDS_HUMAN handoff URL — no account walls.
Auth: https://auth.vin (issuer) · keys/metering via id.org.ai
Siblings:
https://vin.company/ — The family home: one VIN field, every door, one posted record — vin.company/
https://data.vin/ — The Data pillar anchor — the catalog: coverage, license, posted price.
https://services.vin/ — The Services pillar anchor — five lanes, one dispatch counter.
https://commerce.vin/ — The Commerce pillar anchor — the Deal ledger; every order line at its own member address.