title.order

Noun title · Pillar Services

Descriptor

The catalog row, rendered. This is the same descriptor that answers GET /catalog?select=….

The two spellings

One capability, two addresses — generated from one descriptor, so they cannot disagree:

• The catalog name — title.order. What the SDK, the CLI, and the MCP index call it.
• The wire route — POST /titles/order. What HTTP calls it.

Call it

import { title } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await title.order({"vin":"4S4GUHM69T3775945","work":"transfer","state":"state"})

curl -X POST https://apis.vin/titles/order \
  -H 'content-type: application/json' \
  -d '{"vin":"4S4GUHM69T3775945","work":"transfer","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.

{
  "type": "OK",
  "answers": "TitleWorkOrder@1",
  "value": {
    "vin": "4S4GUHM69T3775945",
    "state": "state",
    "workOrder": {
      "orderId": "serviceorder_EMVh3MmY1dFQ",
      "titleNumber": "state-TTL-1",
      "filingType": "paper",
      "titleStatus": "clear"
    },
    "status": "Complete"
  },
  "evidence": {
    "vin": "4S4GUHM69T3775945",
    "state": "state",
    "workOrder": {
      "orderId": "serviceorder_EMVh3MmY1dFQ",
      "titleNumber": "state-TTL-1",
      "filingType": "paper",
      "titleStatus": "clear"
    },
    "status": "Complete"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-registration-rail-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": true
  }
}

Input

Answers

A typed OK envelope carrying TitleWorkOrder@1. Every fact inside it is an evidence object — { value, source, timestamp, verification } — and act-minted facts carry a dereferenceable pointer to the event that minted them. Absence is typed (EMPTY), never a faked 200.

The gate

This capability 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".

When an agent acts on a principal's behalf, a typed Mandate is required — { ceiling, perAction, expires, tripwires }. The ceiling is a field, not a conversation; sub-delegation only narrows it.

The door

title.vin serves this noun on its two routes: / (the landing) · /4S4GUHM69T3775945 (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

On success this capability appends to the record and emits:

• ServiceOrder.settled@1
• Title.completed@1
• Title.dispatched@1
• Title.failed@1
• Title.ordered@1
• Title.requested@1
• TitleWork.ordered@1
• TitleWork.submitted@1
• Vehicle.registered@1
• Vehicle.titled@1

Subscribe on the universal /webhooks rail, or replay from the subject snapshot.

Composed by

Workflows that lean on this leaf: sell-trade · private-party · refinance · lease-return · consignment · total-loss-to-salvage · repo-to-remarketing · end-of-life.

Data model

Backs the Title entity. See the schema, relationships, and state set on title and in the data model.

Generated from the catalog descriptor. It shows only what the descriptor declares — the provider behind a fact is never named here; evidence source names the attesting authority at the estate's own level of abstraction.