reinsurance
The reinsurance noun — identity, lifecycle, events, and every capability as an anchored section: 5 capabilities, 0 live, 5 sandbox, 0 declared.
reinsurance is one of the estate's 317 automotive nouns — a job a car needs done. It carries 5 capabilities: 0 live, 5 sandbox, 0 declared · doors aggregator.vin.
Identity
| Noun | reinsurance |
| Pillar | Commerce (facets: 1 data · 4 commerce) |
| Capabilities | 5 — 0 live · 5 sandbox · 0 declared |
| Entities | Insurer |
| Doors | aggregator.vin |
| SDK | Vin.reinsurance.* from apis.vin |
| Address | /catalog/reinsurance#{action} — the anchor IS the wire name minus reinsurance. |
Events
The vocabulary this noun can append to the record — 4 past-tense, versioned event types, each linked to the capability that emits it:
Reinsurance.ceded@1— emitted bycedeReinsurance.dividendPaid@1— emitted bydividendReinsurance.participated@1— emitted byparticipateReinsurance.reserveReleased@1— emitted byreserveRelease
Lifecycle & state
reserveRelease
reinsurance.reserveRelease · POST /reinsurances/reserve-release · gate key · sandbox · answers ReinsuranceReserveRelease@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5XYP5DGC0RG432375 (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 — Reinsurance.reserveReleased@1.
import { reinsurance } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await reinsurance.reserveRelease()curl -X POST https://apis.vin/reinsurances/reserve-release \
-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": "ReinsuranceReserveRelease@1",
"value": {
"partyId": "reinsurance_5365ec01",
"type": "organization",
"name": "name-2f627a4b",
"identifiers": [],
"roles": [],
"status": "option-1"
},
"evidence": {
"partyId": "reinsurance_5365ec01",
"type": "organization",
"name": "name-2f627a4b",
"identifiers": [],
"roles": [],
"status": "option-1"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "reinsurance-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}More actions
cede
reinsurance.cede · POST /reinsurances/cede · gate key · sandbox · answers ReinsuranceCede@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5XYP5DGC0RG432375 (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 — Reinsurance.ceded@1.
import { reinsurance } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await reinsurance.cede()curl -X POST https://apis.vin/reinsurances/cede \
-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": "ReinsuranceCede@1",
"value": {
"partyId": "pty_9aeb6f8d",
"type": "organization",
"name": "acme-mutual",
"identifiers": [
{
"kind": "naic",
"value": "46517"
}
],
"roles": [
{
"role": "insurer"
},
{
"role": "cedent"
}
],
"cession": "cession_2b752231",
"treaty": "treaty_da1fd924",
"status": "ceded",
"quotaSharePct": 30,
"cededPremium": {
"amount": "25000000",
"currency": "USD"
},
"retainedPremium": {
"amount": "17500000",
"currency": "USD"
},
"cededAt": "2026-08-10T00:00:00.000Z"
},
"evidence": {
"partyId": "pty_9aeb6f8d",
"type": "organization",
"name": "acme-mutual",
"identifiers": [
{
"kind": "naic",
"value": "46517"
}
],
"roles": [
{
"role": "insurer"
},
{
"role": "cedent"
}
],
"cession": "cession_2b752231",
"treaty": "treaty_da1fd924",
"status": "ceded",
"quotaSharePct": 30,
"cededPremium": {
"amount": "25000000",
"currency": "USD"
},
"retainedPremium": {
"amount": "17500000",
"currency": "USD"
},
"cededAt": "2026-08-10T00:00:00.000Z"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "reinsurance-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}claimsExperience
reinsurance.claimsExperience · GET /reinsurances/claims-experience · gate none · sandbox · answers ReinsuranceClaimsExperience@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5XYP5DGC0RG432375 (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.
import { reinsurance } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await reinsurance.claimsExperience()curl 'https://apis.vin/reinsurances/claims-experience'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": "ReinsuranceClaimsExperience@1",
"value": {
"partyId": "reinsurance_c984c785",
"type": "organization",
"name": "name-b23ee56f",
"identifiers": [],
"roles": [],
"status": "option-2"
},
"evidence": {
"partyId": "reinsurance_c984c785",
"type": "organization",
"name": "name-b23ee56f",
"identifiers": [],
"roles": [],
"status": "option-2"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "reinsurance-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}dividend
reinsurance.dividend · POST /reinsurances/dividend · gate key · sandbox · answers ReinsuranceDividend@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5XYP5DGC0RG432375 (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 — Reinsurance.dividendPaid@1.
import { reinsurance } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await reinsurance.dividend()curl -X POST https://apis.vin/reinsurances/dividend \
-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": "ReinsuranceDividend@1",
"value": {
"partyId": "reinsurance_c0bd00d8",
"type": "organization",
"name": "name-644afa50",
"identifiers": [],
"roles": [],
"status": "option-1"
},
"evidence": {
"partyId": "reinsurance_c0bd00d8",
"type": "organization",
"name": "name-644afa50",
"identifiers": [],
"roles": [],
"status": "option-1"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "reinsurance-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}participate
reinsurance.participate · POST /reinsurances/participate · gate key · sandbox · answers ReinsuranceParticipate@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5XYP5DGC0RG432375 (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 — Reinsurance.participated@1.
import { reinsurance } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await reinsurance.participate()curl -X POST https://apis.vin/reinsurances/participate \
-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": "ReinsuranceParticipate@1",
"value": {
"partyId": "reinsurance_d83cbc60",
"type": "organization",
"name": "name-c713de68",
"identifiers": [],
"roles": [],
"status": "option-2"
},
"evidence": {
"partyId": "reinsurance_d83cbc60",
"type": "organization",
"name": "name-c713de68",
"identifiers": [],
"roles": [],
"status": "option-2"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "reinsurance-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.
Insurer
Modeled
The noun drawn out — its record shape, its lifecycle, and how it is exercised end to end. 4 diagrams, rendered from the estate model.
Reinsurance · Class model
Reinsurance · State machine
Reinsurance · Class model
Reinsurance · State machine
Generated from the catalog. Every capability, answer, gate, and entity on this page is a rendered descriptor — it cannot drift from the wire.