docs.vin

oePart

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

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

Identity

NounoePart
PillarData (facets: 7 data · 5 services · 3 commerce)
Capabilities15 — 0 live · 15 sandbox · 0 declared
EntitiesPart
Doorsaggregator.vin
SDKVin.oePart.* from apis.vin
Address/catalog/oePart#{action} — the anchor IS the wire name minus oePart.

Events

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

Discover & read

lookup

oePart.lookup · GET /oe-parts/lookup · gate none · sandbox · answers OePartLookup@1

FieldTypeRequiredNotes
vinstringno

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /5TFJA5DBXTX436568 (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 — oePart.lookup
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.lookup({"vin":"5TFJA5DBXTX436568"})
GET /oe-parts/lookup
curl 'https://apis.vin/oe-parts/lookup?vin=5TFJA5DBXTX436568'

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:14.532Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartLookup@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "lookup": "lookup",
    "component": "replacement component",
    "fits": true,
    "partSource": "oe"
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "lookup": "lookup",
    "component": "replacement component",
    "fits": true,
    "partSource": "oe"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

availability

oePart.availability · GET /oe-parts/availability · gate none · sandbox · answers OePartAvailability@1

FieldTypeRequiredNotes
vinstringno
partNumberstringnoOEM/aftermarket part number — the PartsCatalog SKU the price/availability/supersession lookup keys on.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /5TFJA5DBXTX436568 (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 — oePart.availability
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.availability({"vin":"5TFJA5DBXTX436568","partNumber":"partnumber"})
GET /oe-parts/availability
curl 'https://apis.vin/oe-parts/availability?vin=5TFJA5DBXTX436568&partNumber=partnumber'

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:14.527Z · HTTP 200
{
  "type": "BLOCKED",
  "reason": "RAIL_FAULT",
  "message": "oePart.availability — the estimator sandbox has no seeded answer for the given input (unknown-part)",
  "events": [],
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "sandbox"
  }
}

fitment

oePart.fitment · GET /oe-parts/fitment · gate none · sandbox · answers OePartFitment@1

FieldTypeRequiredNotes
vinstringno

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /5TFJA5DBXTX436568 (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 — oePart.fitment
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.fitment({"vin":"5TFJA5DBXTX436568"})
GET /oe-parts/fitment
curl 'https://apis.vin/oe-parts/fitment?vin=5TFJA5DBXTX436568'

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:14.527Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartFitment@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "lookup": "fitment",
    "component": "replacement component",
    "fits": true,
    "partSource": "oe"
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "lookup": "fitment",
    "component": "replacement component",
    "fits": true,
    "partSource": "oe"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

interchangeLookup

oePart.interchangeLookup · GET /oe-parts/interchange-lookup · gate none · sandbox · answers OePartInterchangeLookup@1

No input — this capability takes no request body.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /5TFJA5DBXTX436568 (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 — oePart.interchangeLookup
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.interchangeLookup()
GET /oe-parts/interchange-lookup
curl 'https://apis.vin/oe-parts/interchange-lookup'

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-16T14:50:09.942Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartInterchangeLookup@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-75699500",
    "lookup": "interchangeLookup",
    "partSource": "oe",
    "crossesTo": {
      "partNumber": "AM-ad298112",
      "partSource": "aftermarket",
      "unitPriceCents": 15600
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-75699500",
    "lookup": "interchangeLookup",
    "partSource": "oe",
    "crossesTo": {
      "partNumber": "AM-ad298112",
      "partSource": "aftermarket",
      "unitPriceCents": 15600
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Quote & price

quote

oePart.quote · POST /oe-parts/quote · gate offer · sandbox · answers OePartQuote@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) · /5TFJA5DBXTX436568 (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.

EmitsOePart.quoteRequested@1 · OePart.quoted@1.

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

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

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:14.571Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartQuote@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "quote": {
      "id": "OQ-4547d07f",
      "amountCents": 24000,
      "currency": "USD",
      "status": "quoted"
    }
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "quote": {
      "id": "OQ-4547d07f",
      "amountCents": 24000,
      "currency": "USD",
      "status": "quoted"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

price

oePart.price · GET /oe-parts/price · gate none · sandbox · answers OePartPrice@1

FieldTypeRequiredNotes
vinstringno

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /5TFJA5DBXTX436568 (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 — oePart.price
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.price({"vin":"5TFJA5DBXTX436568"})
GET /oe-parts/price
curl 'https://apis.vin/oe-parts/price?vin=5TFJA5DBXTX436568'

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:14.569Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartPrice@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "unitPriceCents": 24000,
    "currency": "USD",
    "priceLevel": "retail"
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "unitPriceCents": 24000,
    "currency": "USD",
    "priceLevel": "retail"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

priceLookup

oePart.priceLookup · GET /oe-parts/price-lookup · gate none · sandbox · answers OePartPriceLookup@1

FieldTypeRequiredNotes
vinstringno
partNumberstringnoOEM/aftermarket part number — the PartsCatalog SKU the price/availability/supersession lookup keys on.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /5TFJA5DBXTX436568 (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 — oePart.priceLookup
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.priceLookup({"vin":"5TFJA5DBXTX436568","partNumber":"partnumber"})
GET /oe-parts/price-lookup
curl 'https://apis.vin/oe-parts/price-lookup?vin=5TFJA5DBXTX436568&partNumber=partnumber'

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:14.571Z · HTTP 200
{
  "type": "BLOCKED",
  "reason": "RAIL_FAULT",
  "message": "oePart.priceLookup — the estimator sandbox has no seeded answer for the given input (unknown-part)",
  "events": [],
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "sandbox"
  }
}

Apply & book

order

oePart.order · POST /oe-parts/order · gate offer · sandbox · answers OePartOrder@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) · /5TFJA5DBXTX436568 (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.

EmitsOePart.completed@1 · OePart.dispatched@1 · OePart.ordered@1 · Order.placed@1 · ServiceOrder.settled@1.

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

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

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:14.532Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartOrder@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "order": {
      "id": "ORD-91b2689f",
      "item": "replacement component",
      "status": "placed",
      "amountCents": 24000,
      "currency": "USD"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "order": {
      "id": "ORD-91b2689f",
      "item": "replacement component",
      "status": "placed",
      "amountCents": 24000,
      "currency": "USD"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Pay & settle

pay

oePart.pay · POST /oe-parts/pay · gate offer · sandbox · answers OePartPay@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) · /5TFJA5DBXTX436568 (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.

EmitsOePart.charged@1 · OePart.paid@1 · OePart.payFailed@1 · OePart.payRequested@1 · ServiceOrder.settled@1.

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

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

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:14.533Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartPay@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "payment": {
      "id": "PAY-9bcd1131",
      "status": "settled",
      "amountCents": 24000,
      "currency": "USD"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "payment": {
      "id": "PAY-9bcd1131",
      "status": "settled",
      "amountCents": 24000,
      "currency": "USD"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

refund

oePart.refund · POST /oe-parts/refund · gate offer · sandbox · answers OePartRefund@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) · /5TFJA5DBXTX436568 (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.

EmitsOePart.refunded@1.

the SDK — oePart.refund
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.refund({"vin":"5TFJA5DBXTX436568"})
POST /oe-parts/refund
curl -X POST https://apis.vin/oe-parts/refund \
  -H 'content-type: application/json' \
  -d '{"vin":"5TFJA5DBXTX436568"}'

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:14.571Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartRefund@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "refund": {
      "id": "RF-0af38af7",
      "kind": "return",
      "status": "issued",
      "amountCents": 24000,
      "currency": "USD"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "refund": {
      "id": "RF-0af38af7",
      "kind": "return",
      "status": "issued",
      "amountCents": 24000,
      "currency": "USD"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Fulfill & operate

install

oePart.install · POST /oe-parts/install · gate offer · sandbox · answers OePartInstall@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) · /5TFJA5DBXTX436568 (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.

EmitsOePart.installFailed@1 · OePart.installRequested@1 · OePart.installed@1.

the SDK — oePart.install
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.install({"vin":"5TFJA5DBXTX436568"})
POST /oe-parts/install
curl -X POST https://apis.vin/oe-parts/install \
  -H 'content-type: application/json' \
  -d '{"vin":"5TFJA5DBXTX436568"}'

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:14.532Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartInstall@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "workOrder": {
      "id": "WO-13cae938",
      "operation": "install",
      "status": "scheduled",
      "costCents": 12000,
      "currency": "USD"
    }
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "workOrder": {
      "id": "WO-13cae938",
      "operation": "install",
      "status": "scheduled",
      "costCents": 12000,
      "currency": "USD"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Lifecycle & state

return

oePart.return · POST /oe-parts/return · gate offer · sandbox · answers OePartReturn@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) · /5TFJA5DBXTX436568 (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.

EmitsOePart.returned@1.

the SDK — oePart.return
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.return({"vin":"5TFJA5DBXTX436568"})
POST /oe-parts/return
curl -X POST https://apis.vin/oe-parts/return \
  -H 'content-type: application/json' \
  -d '{"vin":"5TFJA5DBXTX436568"}'

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:14.571Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartReturn@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "refund": {
      "id": "RF-970d7857",
      "kind": "return",
      "status": "issued",
      "amountCents": 24000,
      "currency": "USD"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "refund": {
      "id": "RF-970d7857",
      "kind": "return",
      "status": "issued",
      "amountCents": 24000,
      "currency": "USD"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

warrantyReturn

oePart.warrantyReturn · POST /oe-parts/warranty-return · gate offer · sandbox · answers OePartWarrantyReturn@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) · /5TFJA5DBXTX436568 (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.

EmitsOePart.warrantyReturnRequested@1 · OePart.warrantyReturned@1.

the SDK — oePart.warrantyReturn
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.warrantyReturn({"vin":"5TFJA5DBXTX436568"})
POST /oe-parts/warranty-return
curl -X POST https://apis.vin/oe-parts/warranty-return \
  -H 'content-type: application/json' \
  -d '{"vin":"5TFJA5DBXTX436568"}'

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:14.571Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartWarrantyReturn@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "return": {
      "id": "WR-cb41aa28",
      "decision": "accepted"
    }
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "return": {
      "id": "WR-cb41aa28",
      "decision": "accepted"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

pick

oePart.pick · POST /oe-parts/pick · gate offer · sandbox · answers OePartPick@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) · /5TFJA5DBXTX436568 (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.

EmitsOePart.pickRequested@1 · OePart.picked@1.

the SDK — oePart.pick
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.pick({"vin":"5TFJA5DBXTX436568"})
POST /oe-parts/pick
curl -X POST https://apis.vin/oe-parts/pick \
  -H 'content-type: application/json' \
  -d '{"vin":"5TFJA5DBXTX436568"}'

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:14.537Z · HTTP 200
{
  "type": "OK",
  "answers": "OePartPick@1",
  "value": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "movement": {
      "id": "MV-e4780fc0",
      "operation": "pick",
      "status": "completed"
    }
  },
  "evidence": {
    "vin": "5TFJA5DBXTX436568",
    "noun": "oePart",
    "asOf": "2026-08-10",
    "partNumber": "P-22492010",
    "movement": {
      "id": "MV-e4780fc0",
      "operation": "pick",
      "status": "completed"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "counter-and-ledger-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

supersession

oePart.supersession · GET /oe-parts/supersession · gate none · sandbox · answers OePartSupersession@1

FieldTypeRequiredNotes
vinstringno
partNumberstringnoOEM/aftermarket part number — the PartsCatalog SKU the price/availability/supersession lookup keys on.

Dooraggregator.vin serves this noun on its two routes: / (the landing) · /5TFJA5DBXTX436568 (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 — oePart.supersession
import { oePart } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await oePart.supersession({"vin":"5TFJA5DBXTX436568","partNumber":"partnumber"})
GET /oe-parts/supersession
curl 'https://apis.vin/oe-parts/supersession?vin=5TFJA5DBXTX436568&partNumber=partnumber'

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:14.571Z · HTTP 200
{
  "type": "BLOCKED",
  "reason": "RAIL_FAULT",
  "message": "oePart.supersession — the estimator sandbox has no seeded answer for the given input (unknown-part)",
  "events": [],
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "sandbox"
  }
}

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.

Part


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