abandonedVehicle

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

Identity

Events

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

• AbandonedVehicle.declared@1 — emitted by declare
• AbandonedVehicle.lienSold@1 — emitted by lienSale
• AbandonedVehicle.lienTitled@1 — emitted by lienTitle
• AbandonedVehicle.ownerNotified@1 — emitted by ownerNotify

Fulfill & operate

ownerNotify

abandonedVehicle.ownerNotify · POST /abandoned-vehicles/owner-notify · gate key · sandbox · answers AbandonedVehicleOwnerNotify@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1G1ZC5ST5NF175800 (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.

Emits — AbandonedVehicle.ownerNotified@1.

import { abandonedVehicle } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await abandonedVehicle.ownerNotify()

curl -X POST https://apis.vin/abandoned-vehicles/owner-notify \
  -H 'content-type: application/json' \
  -d '{}'

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.

{
  "type": "OK",
  "answers": "AbandonedVehicleOwnerNotify@1",
  "value": {
    "id": "abandonedVehicle_30cc3d25",
    "vin": "vin-f4784455",
    "origin": "origin-78c8175a",
    "destination": "destination-734aa0f8",
    "carrierId": "carrier_bddcc019",
    "status": "Tow-01"
  },
  "evidence": {
    "id": "abandonedVehicle_30cc3d25",
    "vin": "vin-f4784455",
    "origin": "origin-78c8175a",
    "destination": "destination-734aa0f8",
    "carrierId": "carrier_bddcc019",
    "status": "Tow-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "abandoned-vehicle-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

declare

abandonedVehicle.declare · POST /abandoned-vehicles/declare · gate key · sandbox · answers AbandonedVehicleDeclare@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1G1ZC5ST5NF175800 (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.

Emits — AbandonedVehicle.declared@1.

import { abandonedVehicle } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await abandonedVehicle.declare()

curl -X POST https://apis.vin/abandoned-vehicles/declare \
  -H 'content-type: application/json' \
  -d '{}'

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.

{
  "type": "OK",
  "answers": "AbandonedVehicleDeclare@1",
  "value": {
    "id": "abandonedVehicle_5fa1add9",
    "vin": "vin-c6501da9",
    "origin": "origin-4e1c81fe",
    "destination": "destination-20555de4",
    "carrierId": "carrier_f149d9cd",
    "status": "Tow-01"
  },
  "evidence": {
    "id": "abandonedVehicle_5fa1add9",
    "vin": "vin-c6501da9",
    "origin": "origin-4e1c81fe",
    "destination": "destination-20555de4",
    "carrierId": "carrier_f149d9cd",
    "status": "Tow-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "abandoned-vehicle-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

lienSale

abandonedVehicle.lienSale · POST /abandoned-vehicles/lien-sale · gate key · sandbox · answers AbandonedVehicleLienSale@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1G1ZC5ST5NF175800 (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.

Emits — AbandonedVehicle.lienSold@1.

import { abandonedVehicle } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await abandonedVehicle.lienSale()

curl -X POST https://apis.vin/abandoned-vehicles/lien-sale \
  -H 'content-type: application/json' \
  -d '{}'

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.

{
  "type": "OK",
  "answers": "AbandonedVehicleLienSale@1",
  "value": {
    "id": "abandonedVehicle_b0b521f0",
    "vin": "vin-27f2995a",
    "origin": "origin-c6d24d3f",
    "destination": "destination-27e00d8f",
    "carrierId": "carrier_359dbd2a",
    "status": "Tow-01"
  },
  "evidence": {
    "id": "abandonedVehicle_b0b521f0",
    "vin": "vin-27f2995a",
    "origin": "origin-c6d24d3f",
    "destination": "destination-27e00d8f",
    "carrierId": "carrier_359dbd2a",
    "status": "Tow-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "abandoned-vehicle-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

lienTitle

abandonedVehicle.lienTitle · POST /abandoned-vehicles/lien-title · gate key · sandbox · answers AbandonedVehicleLienTitle@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1G1ZC5ST5NF175800 (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.

Emits — AbandonedVehicle.lienTitled@1.

import { abandonedVehicle } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await abandonedVehicle.lienTitle()

curl -X POST https://apis.vin/abandoned-vehicles/lien-title \
  -H 'content-type: application/json' \
  -d '{}'

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.

{
  "type": "OK",
  "answers": "AbandonedVehicleLienTitle@1",
  "value": {
    "id": "abandonedVehicle_fc607386",
    "vin": "vin-b04566cc",
    "origin": "origin-1a61d055",
    "destination": "destination-b4184121",
    "carrierId": "carrier_0103d9d4",
    "status": "Tow-01"
  },
  "evidence": {
    "id": "abandonedVehicle_fc607386",
    "vin": "vin-b04566cc",
    "origin": "origin-1a61d055",
    "destination": "destination-b4184121",
    "carrierId": "carrier_0103d9d4",
    "status": "Tow-01"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "abandoned-vehicle-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.

Tow

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