registration.renew

Renew — the services face of registration (do it), at `POST /registrations/renew`.

Promoted — earned, computed, recomputed on every regen

This capability earned a standalone page by the computed promotion function (2 of 4 signals): price posted + carries its own stateSet. Its frozen address never moved — /catalog/registration#renew still answers as an anchored section on the noun page. Promotion is a regen event, not a meeting: lose the signals and this page folds back to the anchor while the redirect map retargets automatically.

Sandbox — a caller mode, never a status claim

The key selects the mode. Wire-compatible simulated responses, deterministic and replayable. Every payload is provenance-labeled { environment, simulated } in the body itself — where the row's live rail is a certified connection, it is live via connection: certified, connect to activate. Connecting is the ceremony: a credential submission at integrates.vin (dealer systems) or connects.vin (consumer accounts) enters the activation queue, and submissions rank live rollout.

Noun registration · Pillar Services

Descriptor

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

Field	Value
Noun	`registration`
Facet	Services
Side	`both`
Pillar	Services
Kind	`act`
Status	`sandbox`
Gate	`offer`
Mandate	`required-when-delegated`
Price	posted at /pricing
Door	`registration.vin`
Motions	`B2A` · `B2A2C`

The two spellings

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

The catalog name — registration.renew. What the SDK, the CLI, and the MCP index call it.
The wire route — POST /registrations/renew. What HTTP calls it.

Call it

the SDK — registration.renew

import { registration } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await registration.renew({"vin":"1GC4KVEY9TF100140","state":"state"})

POST /registrations/renew

curl -X POST https://apis.vin/registrations/renew \
  -H 'content-type: application/json' \
  -d '{"vin":"1GC4KVEY9TF100140","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:16.584Z · HTTP 200

{
  "type": "OK",
  "answers": "RegistrationOrder@1",
  "value": {
    "vin": "1GC4KVEY9TF100140",
    "state": "state",
    "renewed": true,
    "plate": "state-TTL1",
    "registrationExpires": "2027-08-10T00:00:00.000Z",
    "status": "Active"
  },
  "evidence": {
    "vin": "1GC4KVEY9TF100140",
    "state": "state",
    "renewed": true,
    "plate": "state-TTL1",
    "registrationExpires": "2027-08-10T00:00:00.000Z",
    "status": "Active"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-registration-rail-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": true
  }
}

Input

Field	Type	Required	Notes
`vin`	`string`	yes	—
`state`	`string`	yes	—
`plate`	`string`	no	—
`work`	`string`	no	one of `renewal`, `new-plate`, `transfer-plate`, `temp-tag`
`authority`	`string`	no	—

Answers

A typed OK envelope carrying RegistrationOrder@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

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