docs.vin

probate

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

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

Identity

Nounprobate
PillarServices (facets: 3 data · 4 services · 2 commerce)
Capabilities9 — 0 live · 9 sandbox · 0 declared
EntitiesTitle
Doorsaggregator.vin
SDKVin.probate.* from apis.vin
Address/catalog/probate#{action} — the anchor IS the wire name minus probate.

Events

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

Apply & book

transferOnDeathRegister

probate.transferOnDeathRegister · POST /probate/transfer-on-death-register · gate key · sandbox · answers ProbateTransferOnDeathRegister@1

No input — this capability takes no request body.

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

EmitsProbate.transferOnDeathRegistered@1.

the SDK — probate.transferOnDeathRegister
import { probate } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await probate.transferOnDeathRegister()
POST /probate/transfer-on-death-register
curl -X POST https://apis.vin/probate/transfer-on-death-register \
  -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:09.803Z · HTTP 200
{
  "type": "OK",
  "answers": "ProbateTransferOnDeathRegister@1",
  "value": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "probate",
    "asOf": "2026-08-10",
    "registration": {
      "status": "no-title-on-file"
    }
  },
  "evidence": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "probate",
    "asOf": "2026-08-10",
    "registration": {
      "status": "no-title-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Fulfill & operate

transferOnDeathExecute

probate.transferOnDeathExecute · POST /probate/transfer-on-death-execute · gate key · sandbox · answers ProbateTransferOnDeathExecute@1

No input — this capability takes no request body.

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

EmitsProbate.transferOnDeathExecuted@1.

the SDK — probate.transferOnDeathExecute
import { probate } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await probate.transferOnDeathExecute()
POST /probate/transfer-on-death-execute
curl -X POST https://apis.vin/probate/transfer-on-death-execute \
  -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:09.803Z · HTTP 200
{
  "type": "OK",
  "answers": "ProbateTransferOnDeathExecute@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "todRef": "TOD-001O",
    "beneficiary": "SANDBOX, PAT",
    "instrument": "transfer-on-death-designation",
    "probateBypassed": true,
    "titleReissueEligible": true,
    "titleReissueExecuted": true,
    "requiredDocuments": [
      "recorded-tod-designation",
      "certified-death-certificate",
      "title-application"
    ],
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "todRef": "TOD-001O",
    "beneficiary": "SANDBOX, PAT",
    "instrument": "transfer-on-death-designation",
    "probateBypassed": true,
    "titleReissueEligible": true,
    "titleReissueExecuted": true,
    "requiredDocuments": [
      "recorded-tod-designation",
      "certified-death-certificate",
      "title-application"
    ],
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Authorize & resolve

decedentTitleClaim

probate.decedentTitleClaim · GET /probate/decedent-title-claim · gate none · sandbox · answers ProbateDecedentTitleClaim@1

No input — this capability takes no request body.

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

EmitsProbate.titleClaimed@1.

the SDK — probate.decedentTitleClaim
import { probate } from 'apis.vin'

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

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.802Z · HTTP 200
{
  "type": "OK",
  "answers": "ProbateDecedentTitleClaim@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "claimRef": "PROB-001O",
    "decedentName": "ESTATE OF SANDBOX, A",
    "claimantRole": "executor",
    "instrument": "letters-testamentary",
    "authorityEstablished": true,
    "titleTransferEligible": true,
    "requiredDocuments": [
      "certified-death-certificate",
      "letters-testamentary",
      "title-application"
    ],
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "claimRef": "PROB-001O",
    "decedentName": "ESTATE OF SANDBOX, A",
    "claimantRole": "executor",
    "instrument": "letters-testamentary",
    "authorityEstablished": true,
    "titleTransferEligible": true,
    "requiredDocuments": [
      "certified-death-certificate",
      "letters-testamentary",
      "title-application"
    ],
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

deceasedRegistrationHold

probate.deceasedRegistrationHold · GET /probate/deceased-registration-hold · gate none · sandbox · answers ProbateDeceasedRegistrationHold@1

No input — this capability takes no request body.

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

EmitsProbate.registrationHeld@1.

the SDK — probate.deceasedRegistrationHold
import { probate } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await probate.deceasedRegistrationHold()
GET /probate/deceased-registration-hold
curl 'https://apis.vin/probate/deceased-registration-hold'

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.802Z · HTTP 200
{
  "type": "OK",
  "answers": "ProbateDeceasedRegistrationHold@1",
  "value": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "probate",
    "asOf": "2026-08-10",
    "hold": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    }
  },
  "evidence": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "probate",
    "asOf": "2026-08-10",
    "hold": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Lifecycle & state

probateOrderTitleTransfer

probate.probateOrderTitleTransfer · POST /probate/probate-order-title-transfer · gate key · sandbox · answers ProbateProbateOrderTitleTransfer@1

No input — this capability takes no request body.

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

EmitsProbate.probateOrderTitleTransferred@1.

the SDK — probate.probateOrderTitleTransfer
import { probate } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await probate.probateOrderTitleTransfer()
POST /probate/probate-order-title-transfer
curl -X POST https://apis.vin/probate/probate-order-title-transfer \
  -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:09.802Z · HTTP 200
{
  "type": "OK",
  "answers": "ProbateProbateOrderTitleTransfer@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "orderRef": "POT-001O",
    "decedentName": "ESTATE OF SANDBOX, A",
    "transferTo": "SANDBOX, PAT",
    "instrument": "certified-probate-order",
    "authorityEstablished": true,
    "titleTransferExecuted": true,
    "newTitleState": "issued-to-heir",
    "requiredDocuments": [
      "certified-probate-order",
      "certified-death-certificate",
      "title-application"
    ],
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "orderRef": "POT-001O",
    "decedentName": "ESTATE OF SANDBOX, A",
    "transferTo": "SANDBOX, PAT",
    "instrument": "certified-probate-order",
    "authorityEstablished": true,
    "titleTransferExecuted": true,
    "newTitleState": "issued-to-heir",
    "requiredDocuments": [
      "certified-probate-order",
      "certified-death-certificate",
      "title-application"
    ],
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

survivingSpouseTransfer

probate.survivingSpouseTransfer · POST /probate/surviving-spouse-transfer · gate key · sandbox · answers ProbateSurvivingSpouseTransfer@1

No input — this capability takes no request body.

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

EmitsProbate.survivingSpouseTransferred@1.

the SDK — probate.survivingSpouseTransfer
import { probate } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await probate.survivingSpouseTransfer()
POST /probate/surviving-spouse-transfer
curl -X POST https://apis.vin/probate/surviving-spouse-transfer \
  -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:09.803Z · HTTP 200
{
  "type": "OK",
  "answers": "ProbateSurvivingSpouseTransfer@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "transferRef": "SST-001O",
    "survivingSpouse": "SANDBOX, PAT",
    "instrument": "surviving-spouse-affidavit",
    "probateBypassed": true,
    "titleReissueEligible": true,
    "requiredDocuments": [
      "certified-death-certificate",
      "marriage-certificate",
      "surviving-spouse-affidavit"
    ],
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "transferRef": "SST-001O",
    "survivingSpouse": "SANDBOX, PAT",
    "instrument": "surviving-spouse-affidavit",
    "probateBypassed": true,
    "titleReissueEligible": true,
    "requiredDocuments": [
      "certified-death-certificate",
      "marriage-certificate",
      "surviving-spouse-affidavit"
    ],
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

heirDisposition

probate.heirDisposition · POST /probate/heir-disposition · gate key · sandbox · answers ProbateHeirDisposition@1

No input — this capability takes no request body.

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

EmitsProbate.heirDisposed@1.

the SDK — probate.heirDisposition
import { probate } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await probate.heirDisposition()
POST /probate/heir-disposition
curl -X POST https://apis.vin/probate/heir-disposition \
  -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:09.802Z · HTTP 200
{
  "type": "OK",
  "answers": "ProbateHeirDisposition@1",
  "value": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "probate",
    "asOf": "2026-08-10",
    "disposition": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    }
  },
  "evidence": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "probate",
    "asOf": "2026-08-10",
    "disposition": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

lienPayoffFromEstate

probate.lienPayoffFromEstate · POST /probate/lien-payoff-from-estate · gate key · sandbox · answers ProbateLienPayoffFromEstate@1

No input — this capability takes no request body.

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

EmitsProbate.lienPayoffSettled@1.

the SDK — probate.lienPayoffFromEstate
import { probate } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await probate.lienPayoffFromEstate()
POST /probate/lien-payoff-from-estate
curl -X POST https://apis.vin/probate/lien-payoff-from-estate \
  -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:09.802Z · HTTP 200
{
  "type": "OK",
  "answers": "ProbateLienPayoffFromEstate@1",
  "value": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "probate",
    "asOf": "2026-08-10",
    "payoff": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    }
  },
  "evidence": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "probate",
    "asOf": "2026-08-10",
    "payoff": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

smallEstateAffidavit

probate.smallEstateAffidavit · POST /probate/small-estate-affidavit · gate key · sandbox · answers ProbateSmallEstateAffidavit@1

No input — this capability takes no request body.

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

EmitsProbate.smallEstateAffidavitFiled@1.

the SDK — probate.smallEstateAffidavit
import { probate } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await probate.smallEstateAffidavit()
POST /probate/small-estate-affidavit
curl -X POST https://apis.vin/probate/small-estate-affidavit \
  -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:09.803Z · HTTP 200
{
  "type": "OK",
  "answers": "ProbateSmallEstateAffidavit@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "affidavitRef": "SEA-001O",
    "estateValue": {
      "amount": "42000.00",
      "currency": "USD"
    },
    "stateThreshold": {
      "amount": "75000.00",
      "currency": "USD"
    },
    "qualifiesSmallEstate": true,
    "waitingPeriodDays": 40,
    "probateRequired": false,
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "affidavitRef": "SEA-001O",
    "estateValue": {
      "amount": "42000.00",
      "currency": "USD"
    },
    "stateThreshold": {
      "amount": "75000.00",
      "currency": "USD"
    },
    "qualifiesSmallEstate": true,
    "waitingPeriodDays": 40,
    "probateRequired": false,
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-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. 3 diagrams, rendered from the estate model.

Probate · Class model

Probate · State machine

Probate · Sequence


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