Registered without the queue.
Quote. File. Drive.
The governing state’s registration fees post at the address — the registration fee, plates, local add-ons — one line each, where the state posts them, with source and timestamp beside every fact. The read is free. No account. The filing quotes on request, state by state.
Hand this record to your agent: it reads the state’s lines and walks the filing 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.
- Governing stateposts liveusually where the car is garaged — the schedule that governs
- Registration feeposts livethe state’s charge, on its own fee schedule
- Platesposts livestandard or specialty, the state’s schedule, one per line
- Local add-onsposts livecounty and city lines, itemized, never rolled up
- Postedthe source · the timestampevery fact posts as value · source · timestamp
Figures render live at the address — this page states structure, not prices. The source of every fee line is the state’s own fee schedule.
The counter, read before the drive.
The counter queue discovers requirements one rejection at a time — a morning surrendered to an office. Here the state’s lines read first — free — and the decode supplies what the form would have asked.
- What does my state charge?the fees post where the state posts them — value, source, timestamp
- Which state governs?usually where the car is garaged — the sheet says which, as a fact
- What will the form ask?the decode supplies it — year, make, model, weight class, from the number
- When is the renewal due?a posted fact on the record — not a surprise in the mail
A renewal missed because no record held the date — that is the failure these lines are posted against. Read them before the counter.
The filing, ordered by the number.
New registration, renewal, plates — each quotes on request through the services counter, the state named first, the quote posted before anything files, the completion posted back to the record as evidence.
- 1QuotePaste the VIN and the state. The decode supplies what the form would have asked, and the filing quotes on request through the services counter.the vendor cost · the margin — separate posted lines
- 2FileThe filing runs as a service order — status posted to the record, each step with its timestamp.the status · its timestamp, each step
- 3DriveThe completion posts to the record, and the renewal date is a posted fact, not a surprise.the renewal date, posted
not yet open · per-state DMV licensing and runner registration verified before registration filings fulfill
Order actions render through the compliance gate: per-state DMV licensing and runner registration verify state by state before filings fulfill. 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
State by state.
Each state posts its own schedule and its own requirements. The sheet says which state governs — usually where the car is garaged — and posts that state’s lines with source and timestamp.
The move
A move across a state line is a new set of lines — read before the drive, not discovered at the counter. Same VIN, same record, the new state’s schedule posted beside the old one.
the new state · its posted lines
The gate
Fulfillment clears state by state — per-state DMV licensing and runner registration, verified before a filing fulfills. Where a state has not cleared, the row says so as a fact.
not yet offered in {state} — posted, never hidden
One office visit.
Title and registration are one counter at the state — and two doors here, one chassis.
The plates
this door — registration
Registration, renewal, plates, and tags post here: the state’s lines read free from the record, the filing quoted on request, the renewal date posted back as a fact.
The title
the co-peer — the paper
The title clears 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.
Questions with posted answers.
Can I order the filing today?
Not yet. Per-state DMV licensing and runner registration verify state by state before filings fulfill; the order action posts on this record as each state clears. The read is live today — paste a VIN above and the state’s lines post, free, no account.
Is the read free?
Yes — the state’s lines post free at the address, every VIN, every visit, no account. The source of every fee line is the state’s own fee schedule, posted with its timestamp.
I moved states — now what?
A move across a state line is a new set of lines. Paste the VIN, name the new state, and its schedule posts — read before the drive, not discovered at the counter.
When is my renewal due?
A posted fact on the record — the completion posts the date, and the date stays readable at the address. A renewal missed because no record held the date is the failure this line exists against.
What about the title?
One office visit, two doors: the title clears at title.vin, the plates post here, and both transact as service orders on one record, settling on one invoice.
How does registration.vin make money?
The read is free. The filing is quoted, per state, through the services counter — vendor cost and margin as separate posted lines, and no fee appears at filing that wasn’t on the quote.
Registration is one face of the record.
If an agent registers the car for you, it reads this same record: the posted lines · 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 lines, typed. Every fact on the sheet — governing state, fee lines, renewal date — is a value with a source and a timestamp, at the same address: the page at registration.vin/{VIN}, the JSON at the same address via Accept, the tools at apis.vin/mcp.
- An agent reads the state’s lines and walks the filing 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 fee line posts as value · source · timestamp — the state’s own schedule is the source
- The lines read free at the address; ordering obeys the same posted per-state gate as this page
- One MCP server for the whole platform: apis.vin/mcp
// resources/read · registration_lines { "type": "vin.registration.lines", "vin": "7MMVABDM3RN163785", "state": <the governing state>, "lines": [ { "name": "registration fee", "amount": <integer, USD cents>, "source": <the state's fee schedule>, "posted": <RFC 3339 timestamp> } ], "filing": { "quote": <on request — vendor cost + margin, separate lines>, "gate": <per-state, attested> }, "renewal_due": <a posted fact, or null> }
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://registration.vin/ -H 'accept: text/markdown' → the markdown twin of this page
curl https://registration.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://registration.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.