docs.vin

titleWashing

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

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

Identity

NountitleWashing
PillarData (facets: 2 data · 1 services)
Capabilities3 — 0 live · 3 sandbox · 0 declared
EntitiesTitle
Doorsaggregator.vin
SDKVin.titleWashing.* from apis.vin
Address/catalog/titleWashing#{action} — the anchor IS the wire name minus titleWashing.

Events

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

Discover & read

detect

titleWashing.detect · GET /title-washings/detect · gate none · sandbox · answers TitleWashingDetect@1

No input — this capability takes no request body.

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

EmitsTitleWashing.detected@1.

the SDK — titleWashing.detect
import { titleWashing } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await titleWashing.detect()
GET /title-washings/detect
curl 'https://apis.vin/title-washings/detect'

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:10.070Z · HTTP 200
{
  "type": "OK",
  "answers": "TitleWashingDetect@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "detectionRef": "TW-001O",
    "titleWashingDetected": false,
    "droppedBrands": [],
    "stateChain": [
      "STATE-A"
    ],
    "recommendedAction": "none",
    "confidence": "clean",
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "detectionRef": "TW-001O",
    "titleWashingDetected": false,
    "droppedBrands": [],
    "stateChain": [
      "STATE-A"
    ],
    "recommendedAction": "none",
    "confidence": "clean",
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-integrity-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Pay & settle

brandChainReconcile

titleWashing.brandChainReconcile · POST /title-washings/brand-chain-reconcile · gate key · sandbox · answers TitleWashingBrandChainReconcile@1

No input — this capability takes no request body.

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

EmitsTitleWashing.brandChainReconciled@1.

the SDK — titleWashing.brandChainReconcile
import { titleWashing } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await titleWashing.brandChainReconcile()
POST /title-washings/brand-chain-reconcile
curl -X POST https://apis.vin/title-washings/brand-chain-reconcile \
  -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.

receipt · executed 2026-08-16T14:50:10.070Z · HTTP 200
{
  "type": "OK",
  "answers": "TitleWashingBrandChainReconcile@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "reconciliationRef": "TWR-001O",
    "brandChainComplete": true,
    "washingDetected": false,
    "droppedBrand": null,
    "jurisdictionsInChain": 1,
    "canonicalBrand": "clean",
    "discloseRequired": false,
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "reconciliationRef": "TWR-001O",
    "brandChainComplete": true,
    "washingDetected": false,
    "droppedBrand": null,
    "jurisdictionsInChain": 1,
    "canonicalBrand": "clean",
    "discloseRequired": false,
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-integrity-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

discloseFinding

titleWashing.discloseFinding · POST /title-washings/disclose-finding · gate key · sandbox · answers TitleWashingDiscloseFinding@1

No input — this capability takes no request body.

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

EmitsTitleWashing.findingDisclosed@1.

the SDK — titleWashing.discloseFinding
import { titleWashing } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await titleWashing.discloseFinding()
POST /title-washings/disclose-finding
curl -X POST https://apis.vin/title-washings/disclose-finding \
  -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.

receipt · executed 2026-08-16T14:50:10.070Z · HTTP 200
{
  "type": "OK",
  "answers": "TitleWashingDiscloseFinding@1",
  "value": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "titleWashing",
    "asOf": "2026-08-10",
    "finding": {
      "washingDetected": false,
      "basis": "brand-chain-continuous",
      "brands": [],
      "titleStatus": "clear"
    }
  },
  "evidence": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "titleWashing",
    "asOf": "2026-08-10",
    "finding": {
      "washingDetected": false,
      "basis": "brand-chain-continuous",
      "brands": [],
      "titleStatus": "clear"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-annex-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.

Title

Modeled

The noun drawn out — its record shape, its lifecycle, and how it is exercised end to end. One diagram, rendered from the estate model.

TitleWashing · Class model


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