stips

stips 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

Lifecycle

Stip — StipFSM: 4 states, 3 transitions — Pending · Verified · Failed · Waived. Each transition is a past-tense event on the record.

Events

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

• Stip.completed@1 — emitted by submit
• Stip.failed@1 — emitted by submit · verify
• Stip.raised@1 — emitted by submit
• Stip.submitted@1 — emitted by submit
• Stip.verified@1 — emitted by submit · verify
• Stip.waived@1 — emitted by submit · waive

Discover & read

verify

stips.verify · POST /stips/verify · gate human · sandbox · answers StipsVerify@1

The gate is a 403 NEEDS_HUMAN — the human verb authorize (credential: stips-desk) · supply side, routed to a named, staffed, priced terminus with a poll rail. Never a dead end. Price: not posted — see /pricing.

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

import { stips } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await stips.verify({"subject":"subject"})

curl -X POST https://apis.vin/stips/verify \
  -H 'content-type: application/json' \
  -d '{"subject":"subject"}'

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": "StipsVerify@1",
  "value": {
    "id": "sub_ceb208e7",
    "dealId": "subject",
    "requirement": "proof-of-income",
    "status": "Verified",
    "verifiedBy": "stips-desk",
    "relevantFields": "last4-only"
  },
  "evidence": {
    "id": "sub_ceb208e7",
    "dealId": "subject",
    "requirement": "proof-of-income",
    "status": "Verified",
    "verifiedBy": "stips-desk",
    "relevantFields": "last4-only"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "stips-sandbox"
  },
  "events": [
    "Stip.verified@1"
  ],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Apply & book

submit

stips.submit · POST /stips/submit · gate key · sandbox · answers StipVerification@1

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1GKS2JKL4MR460820 (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 — Stip.completed@1 · Stip.failed@1 · Stip.raised@1 · Stip.submitted@1 · Stip.verified@1 · Stip.waived@1.

import { stips } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await stips.submit({"subject":"subject","documentType":"documenttype"})

curl -X POST https://apis.vin/stips/submit \
  -H 'content-type: application/json' \
  -d '{"subject":"subject","documentType":"documenttype"}'

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": "StipVerification@1",
  "value": {
    "id": "sub_c6422ceb",
    "dealId": "subject",
    "requirement": "documenttype",
    "status": "Pending",
    "evidence": null,
    "relevantFields": "last4-only"
  },
  "evidence": {
    "id": "sub_c6422ceb",
    "dealId": "subject",
    "requirement": "documenttype",
    "status": "Pending",
    "evidence": null,
    "relevantFields": "last4-only"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "stips-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Authorize & resolve

waive

stips.waive · POST /stips/waive · gate human · sandbox · answers StipsWaive@1

The gate is a 403 NEEDS_HUMAN — the human verb authorize (credential: stips-desk) · supply side, routed to a named, staffed, priced terminus with a poll rail. Never a dead end. Price: not posted — see /pricing.

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

import { stips } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await stips.waive({"subject":"subject"})

curl -X POST https://apis.vin/stips/waive \
  -H 'content-type: application/json' \
  -d '{"subject":"subject"}'

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": "StipsWaive@1",
  "value": {
    "id": "sub_ceb208e7",
    "dealId": "subject",
    "requirement": "proof-of-income",
    "status": "Waived",
    "waivedBy": "stips-desk",
    "relevantFields": "last4-only"
  },
  "evidence": {
    "id": "sub_ceb208e7",
    "dealId": "subject",
    "requirement": "proof-of-income",
    "status": "Waived",
    "waivedBy": "stips-desk",
    "relevantFields": "last4-only"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "stips-sandbox"
  },
  "events": [
    "Stip.waived@1"
  ],
  "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.

Stip

Schema

Relationships

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