Read the title before the wire.
Read. Quote. Clear.
The record’s title line posts at the address — titling state, title type, brands where reported, the lien line — each fact with its source and timestamp beside it. The read is free. No account. The work a title needs quotes on request, state by state.
Hand this record to your agent: it reads the title line and walks the quote through the services counter, and you appear only where you’re load-bearing — sign where the state requires a signature.
A VIN is 17 characters and never uses I, O, or Q.
- Titling stateposts livethe state that holds the paper — the office the work files with
- Title typeposts liveas the state reports it — stated, sourced, timestamped
- Brandspost where reportedwhere reported — none is stated as a fact, never assumed
- Lienstatus posts liveopen · released · none reported — the payoff that still reads open says so
- Postedthe source · the timestampevery fact posts as value · source · timestamp
A line that is reported but not yet verified says so on the line — an open finding, stated, never hidden. Figures render live at the address; this page states structure, not prices.
The problem the paper discovers last.
A lien surfaces at signing. A brand surfaces at resale. The office queue starts after the money moved. Here the line reads first — free — and the counterparty sees this exact page.
- Is the paper clean?title type and brands post from the record — value, source, timestamp
- Is there a lien?the lien line posts — open, released, or none reported
- Which state holds it?the titling state posts — the one office the work files with
- Was the payoff recorded?paid off but still reading open is an open finding — stated on the line
Money moved against a title nobody read — that is the failure this line is posted against. Read it before the wire.
The work, ordered by the number.
Four jobs cover title work. Each quotes on request through the services counter — the state named first, the quote posted before anything files, the cleared title posted back to the record as evidence.
- TransferA sale, a gift, an inheritance — the transfer files with the state.quote on request · state named first
- Lien releasePaid off but still reading open — the release papers and files.quote on request · state named first
- CorrectionA name, an odometer line, a brand recorded wrong — the correction files with the state.quote on request · state named first
- DuplicateLost or destroyed — the duplicate orders from the titling state.quote on request · state named first
not yet open · per-state DMV licensing and runner registration verified before title work fulfills (the gigs.expert route, specced not live)
Order actions render through the compliance gate: per-state DMV licensing and runner registration verify state by state before title work fulfills. Until a state clears, nothing on this page takes a paid order there — the row reads “not yet offered in that state” as a fact. The read is live today — free, no account.
services.vinthe transacting counter — quoted on request, tracked to done
One office visit.
Title and registration are one counter at the state — and two doors here, one chassis.
The title
this door — the paper
The title clears here: status read free from the record, the four jobs quoted on request, the cleared title posted back as evidence.
The plates
the co-peer — registration
Renewal, plates, and tags post at the peer door — the same office visit, read and worked on the same record.
Both transact as service orders through services.vin, on one record, settling on one invoice.
The title clears inside the one order.
A deal that moves money before the paper settles is the old order of operations. On this record the sequence is posted: the line reads first, the work rides the deal’s order, and settlement waits on the paper.
Questions with posted answers.
Can I order title work today?
Not yet. Per-state DMV licensing and runner registration verify state by state before title work fulfills; the order action posts on this record as each state clears. The read is live today — paste a VIN above and the title line posts, free, no account.
Is the read free?
Yes — the title line posts free at the address, every VIN, every visit, no account. The full posted history is a deeper read at vhr.vin — the free line comes first.
Which states does the work cover?
The quote names the state first. Where a state’s fulfillment gate has not cleared, the row says so as a fact — nothing files there until it does.
The title reads wrong — now what?
A name, an odometer line, a brand recorded wrong — the correction is one of the four jobs. It quotes on request with the state named first, and the corrected title posts back to the record as evidence.
Buying or selling — who orders the work?
Either side. Buying, title work attaches to the deal at buy.vin; selling, the transfer is the close’s last step at offers.vin — either way it is one order on one record.
How does title.vin make money?
The read is free. Title work is quoted, per job and per state, through the services counter — the quote posts before anything files, and no fee appears at filing that wasn’t on the quote.
The title is one face of the record.
If an agent clears the paper for you, it reads this same record: the posted line · the quote · the filing tracked to done is the receipt that survives being shown to you.
The third reader.
Humans read this page; agents read the same line, typed. Every fact on the title line — state, type, brands, lien — is a value with a source and a timestamp, at the same address: the page at title.vin/{VIN}, the JSON at the same address via Accept, the tools at apis.vin/mcp.
- An agent reads the title line and walks the quote on its own account.b2a.vin
- The one human step stays human: you sign where the state requires a signature — the agent walks everything else.b2h2a.vin
- Every fact posts as value · source · timestamp — a reported-not-verified line says so
- The title line reads free at the address; ordering obeys the same posted gate as this page
- One MCP server for the whole platform: apis.vin/mcp
// resources/read · title_line { "type": "vin.title.line", "vin": "7MMVABDM3RN163785", "state": <the titling state>, "title_type": <as the state reports it>, "brands": [ <each with source + timestamp> ], "lien": { "status": <open | released | none reported>, "posted": <RFC 3339 timestamp> }, "work": [ { "service": "transfer", "quote": <integer, USD cents — on request>, "gate": <per-state, attested> } ] }
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: B2A · B2H2A
- B2A — the buyer is an agent — no human leaf; discover, bind, pay, worst-case cost posted before the call
- B2H2A — the human appears once, where the act is legally load-bearing — then the agent resumes
curl https://title.vin/ -H 'accept: text/markdown' → the markdown twin of this page
curl https://title.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://title.vin/{VIN} -H 'accept: text/markdown' → the record's markdown twinMachine 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.