apis.vin valid

apis.vin

The estate API. Every capability is addressed by VIN: decode and listings reads, the buy pillar's deal lifecycle (open, desk, sign, insure, settle, deliver), the F&I pillar's rating, menu, and contract verbs, and credit prequalification. One worker serves them all behind typed envelopes — OK, EMPTY, BLOCKED, OFFER — and

For agents: Estate API addressed by VIN: decode and listings reads, deal lifecycle, F&I rating and contracts, and credit prequalification for vehicles.

vehicle apivin decodeauto listingsvehicle financingcredit prequalification

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T09:02:45.245Z. Cached copy · Source on apis.vin

# apis.vin

The estate API. Every capability is addressed by VIN: decode and listings reads,
the buy pillar's deal lifecycle (open, desk, sign, insure, settle, deliver), the
F&I pillar's rating, menu, and contract verbs, and credit prequalification. One
worker serves them all behind typed envelopes — OK, EMPTY, BLOCKED, OFFER — and
never answers 406.

Sandbox doctrine: counterparty rails are deterministic sandbox ports behind real
wire shapes. Every simulated payload carries `"environment": "sandbox",
"simulated": true` — a simulated answer is never presented as a live one, and
the keyless /listings corpus is a fixed [sandbox]-labeled demo set, never a
fabricated market.

Modes, not promises: the key selects the mode. Every catalog row posts
`modes` — `sandbox` (a caller MODE, always answerable deterministically and
always labeled; never a status claim) and `live: platform | connection |
account | null` (which rail answers the live mode). platform rows answer real
platform bytes when keyed; connection rows are live via connection —
certified, connect to activate (a certified counterparty class awaiting your
credential; where the class's real adapter has not yet landed, an active
credential still answers sandbox with a typed adapter-pending disclosure —
capable and active are never conflated); account rows ride the account/money
posture; only `live: null`
rows have no rail anywhere, and only those may read as roadmap. Provenance
still tells the truth on every answer — a simulated payload always says so.

The record face: GET /{VIN} — 17 characters in the VIN alphabet reserve the
segment — answers the record composition with links into /buy/{VIN} and
/fi/inforce/{VIN}. Everything else at the root is a namespace.

Machine-face truth (founder ruling 2026-08-18): apis.vin is the machine
representation. GET / is the ONE HTML address — the landing, negotiated for
a browser. Every other address answers JSON always, whatever the Accept
header or User-Agent says. Markdown is served only where addressed — the
.md face extensions and /llms.txt — and a .html face address outside /
answers a typed JSON 404.

Every POST door publishes its requestBody JSON Schema in /openapi.json, and
a validation refusal aggregates: one BLOCKED answer lists EVERY missing or
invalid field with its expected type (reason + a structured problems array)
— never one field per round-trip.

Money on writes is ONE convention, estate-wide: every money field accepts the
decimal string the estate itself emits ("18750.00"), the response-side money
object ({"amount":"18750.00","currency":"USD"}), or a number of dollars — on
every write door (desk, /fi/quotes, all of them). Reads answer decimal
strings. The one deliberate exception: settle's amount_total is integer
CENTS, because that door mirrors the payments.do settlement-forward wire.

## Quickstart

One copy-pasteable curl per pillar, request bodies included (sandbox,
keyless unless noted):

Keys — mint an anonymous sandbox key (shown onc
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=apis.vin · GET /v1/domain/apis.vin · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for apis.vin:
1. POST https://agentwebmap.com/v1/sites/apis.vin/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://apis.vin/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/apis.vin/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/apis.vin).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.