docs.vin

scra

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

scra 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

Nounscra
PillarServices (facets: 2 data · 3 services)
Capabilities5 — 0 live · 5 sandbox · 0 declared
EntitiesLoanServicing
Doorsaggregator.vin
SDKVin.scra.* from apis.vin
Address/catalog/scra#{action} — the anchor IS the wire name minus scra.

Events

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

Discover & read

eligibilityCheck

scra.eligibilityCheck · GET /scras/eligibility-check · gate none · sandbox · answers ScraEligibilityCheck@1

No input — this capability takes no request body.

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

the SDK — scra.eligibilityCheck
import { scra } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await scra.eligibilityCheck()
GET /scras/eligibility-check
curl 'https://apis.vin/scras/eligibility-check'

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.040Z · HTTP 200
{
  "type": "OK",
  "answers": "ScraEligibilityCheck@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "checkRef": "SCRA-001O",
    "activeDutyStatus": "not-active",
    "scraProtected": false,
    "rateCapEligible": false,
    "maxInterestRate": null,
    "protections": [],
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "checkRef": "SCRA-001O",
    "activeDutyStatus": "not-active",
    "scraProtected": false,
    "rateCapEligible": false,
    "maxInterestRate": null,
    "protections": [],
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

ordersVerify

scra.ordersVerify · GET /scras/orders-verify · gate none · sandbox · answers ScraOrdersVerify@1

No input — this capability takes no request body.

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

the SDK — scra.ordersVerify
import { scra } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await scra.ordersVerify()
GET /scras/orders-verify
curl 'https://apis.vin/scras/orders-verify'

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.040Z · HTTP 200
{
  "type": "OK",
  "answers": "ScraOrdersVerify@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "verificationRef": "SOV-001O",
    "serviceMemberVerified": true,
    "ordersType": "active-duty",
    "ordersEffectiveDate": "2026-06-01",
    "scraProtectionsActive": true,
    "protections": [
      "interest-rate-cap-6pct",
      "repossession-stay",
      "lease-termination-right"
    ],
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "verificationRef": "SOV-001O",
    "serviceMemberVerified": true,
    "ordersType": "active-duty",
    "ordersEffectiveDate": "2026-06-01",
    "scraProtectionsActive": true,
    "protections": [
      "interest-rate-cap-6pct",
      "repossession-stay",
      "lease-termination-right"
    ],
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Apply & book

rateCapApply

scra.rateCapApply · POST /scras/rate-cap-apply · gate key · sandbox · answers ScraRateCapApply@1

No input — this capability takes no request body.

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

the SDK — scra.rateCapApply
import { scra } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await scra.rateCapApply()
POST /scras/rate-cap-apply
curl -X POST https://apis.vin/scras/rate-cap-apply \
  -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.040Z · HTTP 200
{
  "type": "OK",
  "answers": "ScraRateCapApply@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "applicationRef": "SRC-001O",
    "originalApr": "12.90",
    "cappedApr": "6.00",
    "excessInterestForgiven": true,
    "effectiveDate": "2026-08-10",
    "applied": true
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "applicationRef": "SRC-001O",
    "originalApr": "12.90",
    "cappedApr": "6.00",
    "excessInterestForgiven": true,
    "effectiveDate": "2026-08-10",
    "applied": true
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Lifecycle & state

leaseTerminate

scra.leaseTerminate · POST /scras/lease-terminate · gate key · sandbox · answers ScraLeaseTerminate@1

No input — this capability takes no request body.

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

the SDK — scra.leaseTerminate
import { scra } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await scra.leaseTerminate()
POST /scras/lease-terminate
curl -X POST https://apis.vin/scras/lease-terminate \
  -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.040Z · HTTP 200
{
  "type": "OK",
  "answers": "ScraLeaseTerminate@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "scra",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "scra": {
      "status": "no-protection-on-file",
      "basis": "cast-carries-no-scra-axis"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "scra",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "scra": {
      "status": "no-protection-on-file",
      "basis": "cast-carries-no-scra-axis"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "hardship-desk-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

repossessionStay

scra.repossessionStay · POST /scras/repossession-stay · gate key · sandbox · answers ScraRepossessionStay@1

No input — this capability takes no request body.

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

the SDK — scra.repossessionStay
import { scra } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await scra.repossessionStay()
POST /scras/repossession-stay
curl -X POST https://apis.vin/scras/repossession-stay \
  -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.040Z · HTTP 200
{
  "type": "OK",
  "answers": "ScraRepossessionStay@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "scra",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "scra": {
      "status": "no-protection-on-file",
      "basis": "cast-carries-no-scra-axis"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "scra",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "scra": {
      "status": "no-protection-on-file",
      "basis": "cast-carries-no-scra-axis"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "hardship-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.

LoanServicing

Modeled

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

Scra · Class model

Scra · Sequence

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

safetyInspection

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

settlementStatement

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

On this page

Identity
Events
Discover & read
eligibilityCheck
ordersVerify
Apply & book
rateCapApply
Lifecycle & state
leaseTerminate
More actions
repossessionStay
Data model
LoanServicing
Modeled