vehicle.decode

Noun vehicle · Pillar Data

Descriptor

The catalog row, rendered. This is the same descriptor that answers GET /catalog?select=….

The two spellings

One capability, two addresses — generated from one descriptor, so they cannot disagree:

• The catalog name — vehicle.decode. What the SDK, the CLI, and the MCP index call it.
• The wire route — GET /vehicles/decode. What HTTP calls it.

Call it

import { vehicle } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await vehicle.decode({"vin":"3GCUKDED9TG130308"})

curl 'https://apis.vin/vehicles/decode?vin=3GCUKDED9TG130308'

Input

Answers

A typed OK envelope carrying VehicleDecode@1. Every fact inside it is an evidence object — { value, source, timestamp, verification } — and act-minted facts carry a dereferenceable pointer to the event that minted them. Absence is typed (EMPTY), never a faked 200.

The gate

This capability is open — no gate; a keyless read.

The door

data.vin serves this noun on its two routes: / (the landing) · /3GCUKDED9TG130308 (the VIN lens).

Try it

Live: answers on the wire today. A sandbox key still selects the deterministic simulated mode — drive the full outcome range with the magic triggers.

Composed by

Workflows that lean on this leaf: buy · sell-trade · concierge-broker · new-vehicle-build · dealer-stocking.

Data model

Backs the Vehicle entity. See the schema, relationships, and state set on vehicle and in the data model.

Generated from the catalog descriptor. It shows only what the descriptor declares — the provider behind a fact is never named here; evidence source names the attesting authority at the estate's own level of abstraction.