subrogation

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

Identity

Events

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

• Subrogation.opened@1 — emitted by open
• Subrogation.pursued@1 — emitted by pursue

Apply & book

open

subrogation.open · POST /subrogations/open · gate key · sandbox · answers SubrogationOpen@1

No input — this capability takes no request body.

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

import { subrogation } from 'apis.vin'

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

curl -X POST https://apis.vin/subrogations/open \
  -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": "SubrogationOpen@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "subrogation",
    "asOf": "2026-08-10",
    "claim": {
      "status": "no-claim-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "subrogation",
    "asOf": "2026-08-10",
    "claim": {
      "status": "no-claim-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "claim-desk-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

pursue

subrogation.pursue · POST /subrogations/pursue · gate key · sandbox · answers SubrogationPursue@1

No input — this capability takes no request body.

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

import { subrogation } from 'apis.vin'

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

curl -X POST https://apis.vin/subrogations/pursue \
  -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": "SubrogationPursue@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "subrogation",
    "asOf": "2026-08-10",
    "claim": {
      "status": "no-claim-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "subrogation",
    "asOf": "2026-08-10",
    "claim": {
      "status": "no-claim-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "claim-desk-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.

Claim

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.

Subrogation · 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.