docs.vin

ppi

The ppi noun — identity, lifecycle, events, and every capability as an anchored section: 14 capabilities, 0 live, 14 sandbox, 0 declared.

ppi is one of the estate's 317 automotive nouns — a job a car needs done. It carries 14 capabilities: 0 live, 14 sandbox, 0 declared · doors aggregator.vin.

Identity

Nounppi
PillarData (facets: 5 data · 5 services · 4 commerce)
Capabilities14 — 0 live · 14 sandbox · 0 declared
EntitiesInspection
Doorsaggregator.vin
SDKVin.ppi.* from apis.vin
Address/catalog/ppi#{action} — the anchor IS the wire name minus ppi.

Events

The vocabulary this noun can append to the record — 23 past-tense, versioned event types, each linked to the capability that emits it:

Discover & read

status

ppi.status · GET /ppis/status · gate none · sandbox · answers PpiStatus@1

FieldTypeRequiredNotes
vinstringno

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

the SDK — ppi.status
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.status({"vin":"1G1FW6S00H4181977"})
GET /ppis/status
curl 'https://apis.vin/ppis/status?vin=1G1FW6S00H4181977'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.729Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiStatus@1",
  "value": {
    "id": "ppi_0304aff8",
    "vin": "vin-2073c562",
    "type": "option-3",
    "location": "location-bd3dd93e",
    "inspectorId": "provider_b012066b",
    "grade": "grade-8a6b470c",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_0304aff8",
    "vin": "vin-2073c562",
    "type": "option-3",
    "location": "location-bd3dd93e",
    "inspectorId": "provider_b012066b",
    "grade": "grade-8a6b470c",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

report

ppi.report · GET /ppis/report · gate none · sandbox · answers PpiReport@1

FieldTypeRequiredNotes
vinstringno

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

the SDK — ppi.report
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.report({"vin":"1G1FW6S00H4181977"})
GET /ppis/report
curl 'https://apis.vin/ppis/report?vin=1G1FW6S00H4181977'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.725Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiReport@1",
  "value": {
    "id": "ppi_53d5cbe0",
    "vin": "vin-81d1f38a",
    "type": "option-1",
    "location": "location-eea002a6",
    "inspectorId": "provider_72f73393",
    "grade": "grade-4f34d934",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_53d5cbe0",
    "vin": "vin-81d1f38a",
    "type": "option-1",
    "location": "location-eea002a6",
    "inspectorId": "provider_72f73393",
    "grade": "grade-4f34d934",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

photos

ppi.photos · GET /ppis/photos · gate none · sandbox · answers PpiPhotos@1

FieldTypeRequiredNotes
vinstringno

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

the SDK — ppi.photos
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.photos({"vin":"1G1FW6S00H4181977"})
GET /ppis/photos
curl 'https://apis.vin/ppis/photos?vin=1G1FW6S00H4181977'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.725Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiPhotos@1",
  "value": {
    "id": "ppi_d29c0e7f",
    "vin": "vin-d2985b83",
    "type": "option-1",
    "location": "location-6db0fb71",
    "inspectorId": "provider_cd410a16",
    "grade": "grade-34c1f325",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_d29c0e7f",
    "vin": "vin-d2985b83",
    "type": "option-1",
    "location": "location-6db0fb71",
    "inspectorId": "provider_cd410a16",
    "grade": "grade-34c1f325",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Quote & price

quote

ppi.quote · POST /ppis/quote · gate offer · sandbox · answers PpiQuote@1

FieldTypeRequiredNotes
vinstringno

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.quoteRequested@1 · Ppi.quoted@1.

the SDK — ppi.quote
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.quote({"vin":"1G1FW6S00H4181977"})
POST /ppis/quote
curl -X POST https://apis.vin/ppis/quote \
  -H 'content-type: application/json' \
  -d '{"vin":"1G1FW6S00H4181977"}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.725Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiQuote@1",
  "value": {
    "id": "ppi_0c527bbd",
    "vin": "vin-c09bc84d",
    "type": "option-2",
    "location": "location-9e0cf847",
    "inspectorId": "provider_8dbbd0cc",
    "grade": "grade-19a0b697",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_0c527bbd",
    "vin": "vin-c09bc84d",
    "type": "option-2",
    "location": "location-9e0cf847",
    "inspectorId": "provider_8dbbd0cc",
    "grade": "grade-19a0b697",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Apply & book

order

ppi.order · POST /ppis/order · gate offer · sandbox · answers PpiOrder@1

FieldTypeRequiredNotes
vinstringno

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.completed@1 · Ppi.dispatched@1 · Ppi.ordered@1 · ServiceOrder.settled@1.

the SDK — ppi.order
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.order({"vin":"1G1FW6S00H4181977"})
POST /ppis/order
curl -X POST https://apis.vin/ppis/order \
  -H 'content-type: application/json' \
  -d '{"vin":"1G1FW6S00H4181977"}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.713Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiOrder@1",
  "value": {
    "id": "ppi_4ae4030c",
    "vin": "vin-7582d406",
    "type": "option-1",
    "location": "location-92f703b2",
    "inspectorId": "provider_8e239d47",
    "grade": "grade-4aba98c8",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_4ae4030c",
    "vin": "vin-7582d406",
    "type": "option-1",
    "location": "location-92f703b2",
    "inspectorId": "provider_8e239d47",
    "grade": "grade-4aba98c8",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

schedule

ppi.schedule · POST /ppis/schedule · gate offer · sandbox · answers PpiSchedule@1

FieldTypeRequiredNotes
vinstringno

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.scheduleRequested@1 · Ppi.scheduled@1.

the SDK — ppi.schedule
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.schedule({"vin":"1G1FW6S00H4181977"})
POST /ppis/schedule
curl -X POST https://apis.vin/ppis/schedule \
  -H 'content-type: application/json' \
  -d '{"vin":"1G1FW6S00H4181977"}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.725Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiSchedule@1",
  "value": {
    "id": "ppi_2117c286",
    "vin": "vin-7cd6c3cc",
    "type": "option-1",
    "location": "location-6a6e86cc",
    "inspectorId": "provider_26536509",
    "grade": "grade-59db5186",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_2117c286",
    "vin": "vin-7cd6c3cc",
    "type": "option-1",
    "location": "location-6a6e86cc",
    "inspectorId": "provider_26536509",
    "grade": "grade-59db5186",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Pay & settle

pay

ppi.pay · POST /ppis/pay · gate offer · sandbox · answers PpiPay@1

FieldTypeRequiredNotes
vinstringno

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.paid@1 · Ppi.payFailed@1 · Ppi.payRequested@1.

the SDK — ppi.pay
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.pay({"vin":"1G1FW6S00H4181977"})
POST /ppis/pay
curl -X POST https://apis.vin/ppis/pay \
  -H 'content-type: application/json' \
  -d '{"vin":"1G1FW6S00H4181977"}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.721Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiPay@1",
  "value": {
    "id": "ppi_c2c3770e",
    "vin": "vin-c5b56514",
    "type": "option-1",
    "location": "location-a6481f74",
    "inspectorId": "provider_759fe971",
    "grade": "grade-63434cee",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_c2c3770e",
    "vin": "vin-c5b56514",
    "type": "option-1",
    "location": "location-a6481f74",
    "inspectorId": "provider_759fe971",
    "grade": "grade-63434cee",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

invoice

ppi.invoice · POST /ppis/invoice · gate offer · sandbox · answers PpiInvoice@1

FieldTypeRequiredNotes
vinstringno

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.invoiceFailed@1 · Ppi.invoiceRequested@1 · Ppi.invoiced@1.

the SDK — ppi.invoice
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.invoice({"vin":"1G1FW6S00H4181977"})
POST /ppis/invoice
curl -X POST https://apis.vin/ppis/invoice \
  -H 'content-type: application/json' \
  -d '{"vin":"1G1FW6S00H4181977"}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.712Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiInvoice@1",
  "value": {
    "id": "ppi_1c4a1140",
    "vin": "vin-b0db8e6a",
    "type": "option-1",
    "location": "location-e5137b06",
    "inspectorId": "provider_56a31db3",
    "grade": "grade-515f2f14",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_1c4a1140",
    "vin": "vin-b0db8e6a",
    "type": "option-1",
    "location": "location-e5137b06",
    "inspectorId": "provider_56a31db3",
    "grade": "grade-515f2f14",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Fulfill & operate

perform

ppi.perform · POST /ppis/perform · gate offer · sandbox · answers PpiPerform@1

FieldTypeRequiredNotes
vinstringno

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.performFailed@1 · Ppi.performRequested@1 · Ppi.performed@1.

the SDK — ppi.perform
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.perform({"vin":"1G1FW6S00H4181977"})
POST /ppis/perform
curl -X POST https://apis.vin/ppis/perform \
  -H 'content-type: application/json' \
  -d '{"vin":"1G1FW6S00H4181977"}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.725Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiPerform@1",
  "value": {
    "id": "ppi_19fba005",
    "vin": "vin-2c8a25b5",
    "type": "option-3",
    "location": "location-0c0ceeef",
    "inspectorId": "provider_fd809af4",
    "grade": "grade-f893dd5f",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_19fba005",
    "vin": "vin-2c8a25b5",
    "type": "option-3",
    "location": "location-0c0ceeef",
    "inspectorId": "provider_fd809af4",
    "grade": "grade-f893dd5f",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

complete

ppi.complete · POST /ppis/complete · gate offer · sandbox · answers PpiComplete@1

FieldTypeRequiredNotes
vinstringno

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.completeRequested@1 · Ppi.completed@1.

the SDK — ppi.complete
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.complete({"vin":"1G1FW6S00H4181977"})
POST /ppis/complete
curl -X POST https://apis.vin/ppis/complete \
  -H 'content-type: application/json' \
  -d '{"vin":"1G1FW6S00H4181977"}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.687Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiComplete@1",
  "value": {
    "id": "ppi_5d8613d4",
    "vin": "vin-54fdff6e",
    "type": "option-2",
    "location": "location-91a0455a",
    "inspectorId": "provider_af4c3d2f",
    "grade": "grade-37091cd0",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_5d8613d4",
    "vin": "vin-54fdff6e",
    "type": "option-2",
    "location": "location-91a0455a",
    "inspectorId": "provider_af4c3d2f",
    "grade": "grade-37091cd0",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

dispatchMechanic

ppi.dispatchMechanic · POST /ppis/dispatch-mechanic · gate offer · sandbox · answers PpiDispatchMechanic@1

FieldTypeRequiredNotes
vinstringno

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.dispatchMechanicRequested@1 · Ppi.mechanicDispatched@1.

the SDK — ppi.dispatchMechanic
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.dispatchMechanic({"vin":"1G1FW6S00H4181977"})
POST /ppis/dispatch-mechanic
curl -X POST https://apis.vin/ppis/dispatch-mechanic \
  -H 'content-type: application/json' \
  -d '{"vin":"1G1FW6S00H4181977"}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.689Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiDispatchMechanic@1",
  "value": {
    "id": "ppi_e0f4a9d6",
    "vin": "vin-ba9cb0dc",
    "type": "option-1",
    "location": "location-fc3f2efc",
    "inspectorId": "provider_482b2c39",
    "grade": "grade-aab6c116",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_e0f4a9d6",
    "vin": "vin-ba9cb0dc",
    "type": "option-1",
    "location": "location-fc3f2efc",
    "inspectorId": "provider_482b2c39",
    "grade": "grade-aab6c116",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

findings

ppi.findings · GET /ppis/findings · gate none · sandbox · answers PpiFindings@1

FieldTypeRequiredNotes
vinstringno

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

the SDK — ppi.findings
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.findings({"vin":"1G1FW6S00H4181977"})
GET /ppis/findings
curl 'https://apis.vin/ppis/findings?vin=1G1FW6S00H4181977'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.691Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiFindings@1",
  "value": {
    "id": "ppi_62ac7f7c",
    "vin": "vin-fb241db6",
    "type": "option-1",
    "location": "location-5ff7e442",
    "inspectorId": "provider_116f7f57",
    "grade": "grade-17f345f8",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_62ac7f7c",
    "vin": "vin-fb241db6",
    "type": "option-1",
    "location": "location-5ff7e442",
    "inspectorId": "provider_116f7f57",
    "grade": "grade-17f345f8",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

roadTest

ppi.roadTest · POST /ppis/road-test · gate offer · sandbox · answers PpiRoadTest@1

FieldTypeRequiredNotes
vinstringno

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.roadTestRequested@1 · Ppi.roadTested@1.

the SDK — ppi.roadTest
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.roadTest({"vin":"1G1FW6S00H4181977"})
POST /ppis/road-test
curl -X POST https://apis.vin/ppis/road-test \
  -H 'content-type: application/json' \
  -d '{"vin":"1G1FW6S00H4181977"}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.725Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiRoadTest@1",
  "value": {
    "id": "ppi_da3774b9",
    "vin": "vin-e0189509",
    "type": "option-2",
    "location": "location-cb698643",
    "inspectorId": "provider_d3cecae0",
    "grade": "grade-b0d5620b",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_da3774b9",
    "vin": "vin-e0189509",
    "type": "option-2",
    "location": "location-cb698643",
    "inspectorId": "provider_d3cecae0",
    "grade": "grade-b0d5620b",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

severity

ppi.severity · GET /ppis/severity · gate key · sandbox · answers PpiSeverity@1

FieldTypeRequiredNotes
vinstringno

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /1G1FW6S00H4181977 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

EmitsPpi.severitied@1.

the SDK — ppi.severity
import { ppi } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await ppi.severity({"vin":"1G1FW6S00H4181977"})
GET /ppis/severity
curl 'https://apis.vin/ppis/severity?vin=1G1FW6S00H4181977'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-17T12:42:15.727Z · HTTP 200
{
  "type": "OK",
  "answers": "PpiSeverity@1",
  "value": {
    "id": "ppi_cfa3f0a4",
    "vin": "vin-6c8b973e",
    "type": "option-2",
    "location": "location-425a1d4a",
    "inspectorId": "provider_3f165e1f",
    "grade": "grade-96871de0",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "evidence": {
    "id": "ppi_cfa3f0a4",
    "vin": "vin-6c8b973e",
    "type": "option-2",
    "location": "location-425a1d4a",
    "inspectorId": "provider_3f165e1f",
    "grade": "grade-96871de0",
    "damages": [],
    "photos": [],
    "status": "Inspection-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "ppi-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Data model

The record shape behind this noun — one entity, each property an evidence field. See the whole estate model on the data model page.

Inspection


Generated from the catalog. Every capability, answer, gate, and entity on this page is a rendered descriptor — it cannot drift from the wire.