docs.vin

cosigner

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

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

Identity

Nouncosigner
PillarData (facets: 2 data · 2 services)
Capabilities4 — 0 live · 4 sandbox · 0 declared
EntitiesCreditApplication
Doorsaggregator.vin
SDKVin.cosigner.* from apis.vin
Address/catalog/cosigner#{action} — the anchor IS the wire name minus cosigner.

Events

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

Discover & read

liabilityStatus

cosigner.liabilityStatus · GET /cosigners/liability-status · gate none · sandbox · answers CosignerLiabilityStatus@1

No input — this capability takes no request body.

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

the SDK — cosigner.liabilityStatus
import { cosigner } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await cosigner.liabilityStatus()
GET /cosigners/liability-status
curl 'https://apis.vin/cosigners/liability-status'

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.726Z · HTTP 200
{
  "type": "OK",
  "answers": "CosignerLiabilityStatus@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "cosigner",
    "asOf": "2026-08-10",
    "application": {
      "status": "no-application-on-file"
    },
    "liability": {
      "status": "no-cosigner-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "cosigner",
    "asOf": "2026-08-10",
    "application": {
      "status": "no-application-on-file"
    },
    "liability": {
      "status": "no-cosigner-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "credit-jacket-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Lifecycle & state

release

cosigner.release · POST /cosigners/release · gate key · sandbox · answers CosignerRelease@1

No input — this capability takes no request body.

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

the SDK — cosigner.release
import { cosigner } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await cosigner.release()
POST /cosigners/release
curl -X POST https://apis.vin/cosigners/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.

receipt · executed 2026-08-16T14:50:09.726Z · HTTP 200
{
  "type": "OK",
  "answers": "CosignerRelease@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "cosigner",
    "asOf": "2026-08-10",
    "application": {
      "status": "no-application-on-file"
    },
    "release": {
      "status": "no-cosigner-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "cosigner",
    "asOf": "2026-08-10",
    "application": {
      "status": "no-application-on-file"
    },
    "release": {
      "status": "no-cosigner-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "credit-jacket-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

disclose

cosigner.disclose · POST /cosigners/disclose · gate key · sandbox · answers CosignerDisclose@1

No input — this capability takes no request body.

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

the SDK — cosigner.disclose
import { cosigner } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await cosigner.disclose()
POST /cosigners/disclose
curl -X POST https://apis.vin/cosigners/disclose \
  -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.725Z · HTTP 200
{
  "type": "OK",
  "answers": "CosignerDisclose@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "cosigner",
    "asOf": "2026-08-10",
    "application": {
      "status": "no-application-on-file"
    },
    "disclosure": {
      "status": "no-joint-applicant-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "cosigner",
    "asOf": "2026-08-10",
    "application": {
      "status": "no-application-on-file"
    },
    "disclosure": {
      "status": "no-joint-applicant-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "credit-jacket-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

invite

cosigner.invite · POST /cosigners/invite · gate key · sandbox · answers CosignerInvite@1

No input — this capability takes no request body.

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

the SDK — cosigner.invite
import { cosigner } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await cosigner.invite()
POST /cosigners/invite
curl -X POST https://apis.vin/cosigners/invite \
  -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.726Z · HTTP 200
{
  "type": "OK",
  "answers": "CosignerInvite@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "cosigner",
    "asOf": "2026-08-10",
    "application": {
      "status": "no-application-on-file"
    },
    "invitation": {
      "status": "no-joint-applicant-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "cosigner",
    "asOf": "2026-08-10",
    "application": {
      "status": "no-application-on-file"
    },
    "invitation": {
      "status": "no-joint-applicant-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "credit-jacket-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.

CreditApplication

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.

Cosigner · Class model

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

core

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

cpo

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

On this page

Identity
Events
Discover & read
liabilityStatus
Lifecycle & state
release
disclose
More actions
invite
Data model
CreditApplication
Modeled