docs.vin

poa

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

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

Identity

Nounpoa
PillarServices (facets: 1 data · 6 services)
Capabilities7 — 0 live · 7 sandbox · 0 declared
EntitiesDocument
Doorsaggregator.vin · poa.vin
SDKVin.poa.* from apis.vin
Address/catalog/poa#{action} — the anchor IS the wire name minus poa.

Events

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

Discover & read

verify

poa.verify · GET /poas/verify · gate none · sandbox · answers PoaVerify@1

No input — this capability takes no request body.

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

the SDK — poa.verify
import { poa } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await poa.verify()
GET /poas/verify
curl 'https://apis.vin/poas/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:09.973Z · HTTP 200
{
  "type": "OK",
  "answers": "PoaVerify@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "verification": {
      "status": "no-document-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "verification": {
      "status": "no-document-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "paper-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Fulfill & operate

generate

poa.generate · POST /poas/generate · gate offer · sandbox · answers PoaDocument@1

FieldTypeRequiredNotes
vinstringyes—
statestringyesgoverning-state params
principalobjectno—
brandstringnowhite-label
authoritystringno—

The gate is a 402 OFFER — the price and a hard ceiling on the wire, with a durable intent that executes on settlement. Never a wall, never "contact sales". Price: not posted — see /pricing.

Delegated calls require a typed Mandate — { ceiling, perAction, expires, tripwires }; the ceiling is a field, not a conversation.

Door — poa.vin serves this noun on its two routes: / (the landing) · /1FMEE5DH8MLA60998 (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 — Poa.generated@1 · Document.generated@1.

the SDK — poa.generate
import { poa } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await poa.generate({"vin":"1FMEE5DH8MLA60998","state":"state"})
POST /poas/generate
curl -X POST https://apis.vin/poas/generate \
  -H 'content-type: application/json' \
  -d '{"vin":"1FMEE5DH8MLA60998","state":"state"}'

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-17T12:42:15.588Z · HTTP 200
{
  "type": "OK",
  "answers": "PoaDocument@1",
  "value": {
    "vin": "1FMEE5DH8MLA60998",
    "noun": "poa",
    "asOf": "2026-08-10",
    "id": "DOC-9392e8f7",
    "type": "vehicle-record",
    "subjectId": "DL-d1d232be",
    "hash": "sha256:b2d5d044b5d5d4fd",
    "signers": [
      {
        "role": "buyer",
        "identityId": "ID-11f17424",
        "name": "Ava Good",
        "status": "not-yet-requested"
      },
      {
        "role": "seller",
        "identityId": "DLR-b9066ade",
        "name": "The Estate Store",
        "status": "not-yet-requested"
      }
    ],
    "status": "Draft",
    "generation": {
      "status": "already-on-file",
      "id": "DOC-9392e8f7",
      "position": "Draft"
    }
  },
  "evidence": {
    "vin": "1FMEE5DH8MLA60998",
    "noun": "poa",
    "asOf": "2026-08-10",
    "id": "DOC-9392e8f7",
    "type": "vehicle-record",
    "subjectId": "DL-d1d232be",
    "hash": "sha256:b2d5d044b5d5d4fd",
    "signers": [
      {
        "role": "buyer",
        "identityId": "ID-11f17424",
        "name": "Ava Good",
        "status": "not-yet-requested"
      },
      {
        "role": "seller",
        "identityId": "DLR-b9066ade",
        "name": "The Estate Store",
        "status": "not-yet-requested"
      }
    ],
    "status": "Draft",
    "generation": {
      "status": "already-on-file",
      "id": "DOC-9392e8f7",
      "position": "Draft"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "paper-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

execute

poa.execute · POST /poas/execute · gate key · sandbox · answers PoaExecute@1

No input — this capability takes no request body.

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

the SDK — poa.execute
import { poa } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await poa.execute()
POST /poas/execute
curl -X POST https://apis.vin/poas/execute \
  -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.973Z · HTTP 200
{
  "type": "OK",
  "answers": "PoaExecute@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "execution": {
      "status": "no-document-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "execution": {
      "status": "no-document-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "paper-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

secureFormIssue

poa.secureFormIssue · POST /poas/secure-form-issue · gate key · sandbox · answers PoaSecureFormIssue@1

No input — this capability takes no request body.

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

the SDK — poa.secureFormIssue
import { poa } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await poa.secureFormIssue()
POST /poas/secure-form-issue
curl -X POST https://apis.vin/poas/secure-form-issue \
  -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.973Z · HTTP 200
{
  "type": "OK",
  "answers": "PoaSecureFormIssue@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "form": {
      "id": "PSF-98cd68f5",
      "kind": "secure-poa-form",
      "status": "issued"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "form": {
      "id": "PSF-98cd68f5",
      "kind": "secure-poa-form",
      "status": "issued"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "paper-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Authorize & resolve

notarize

poa.notarize · POST /poas/notarize · gate human · sandbox · answers Notarization@1

FieldTypeRequiredNotes
documentIdstringyes—
modestringnoone of in-person, ron

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

Door — poa.vin serves this noun on its two routes: / (the landing) · /1FMEE5DH8MLA60998 (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 — Document.filed@1 · Document.notarized@1.

the SDK — poa.notarize
import { poa } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await poa.notarize({"documentId":"documentid"})
POST /poas/notarize
curl -X POST https://apis.vin/poas/notarize \
  -H 'content-type: application/json' \
  -d '{"documentId":"documentid"}'

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.973Z · HTTP 200
{
  "type": "OK",
  "answers": "Notarization@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "stamp": {
      "status": "no-document-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "stamp": {
      "status": "no-document-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "paper-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

revoke

poa.revoke · POST /poas/revoke · gate key · sandbox · answers PoaRevoke@1

No input — this capability takes no request body.

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

the SDK — poa.revoke
import { poa } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await poa.revoke()
POST /poas/revoke
curl -X POST https://apis.vin/poas/revoke \
  -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.973Z · HTTP 200
{
  "type": "OK",
  "answers": "PoaRevoke@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "revocation": {
      "status": "nothing-to-revoke"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "revocation": {
      "status": "nothing-to-revoke"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "paper-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

absentBuyerSign

poa.absentBuyerSign · POST /poas/absent-buyer-sign · gate key · sandbox · answers PoaAbsentBuyerSign@1

No input — this capability takes no request body.

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

the SDK — poa.absentBuyerSign
import { poa } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await poa.absentBuyerSign()
POST /poas/absent-buyer-sign
curl -X POST https://apis.vin/poas/absent-buyer-sign \
  -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.973Z · HTTP 200
{
  "type": "OK",
  "answers": "PoaAbsentBuyerSign@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "absentSigning": {
      "status": "no-document-on-file"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "poa",
    "asOf": "2026-08-10",
    "document": {
      "status": "no-document-on-file"
    },
    "absentSigning": {
      "status": "no-document-on-file"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "paper-annex-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.

Document

Modeled

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

Poa · Class model

Poa · State machine

Poa · Sequence

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

plate

The plate noun — identity, lifecycle, events, and every capability as an anchored section: 11 capabilities, 3 live, 8 sandbox, 0 declared.

port

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

On this page

Identity
Events
Discover & read
verify
Fulfill & operate
generate
execute
secureFormIssue
Authorize & resolve
notarize
revoke
absentBuyerSign
Data model
Document
Modeled