usage.get
Get — the commerce face of usage (transact it), at `GET /usages/get`.
This capability earned a standalone page by the computed promotion function (2 of 4 signals): live on the wire + carries its own stateSet. Its frozen address never moved — /catalog/usage#get 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.
The acceptance suite is green. This capability answers on the wire today.
Noun usage · Pillar Commerce
Descriptor
The catalog row, rendered. This is the same descriptor that answers GET /catalog?select=….
| Field | Value |
|---|---|
| Noun | usage |
| Facet | Commerce |
| Side | facilitator |
| Pillar | Commerce |
| Kind | read |
| Status | live |
| Gate | key |
| Mandate | none |
| Price | not posted — see /pricing |
| Door | apis.vin |
The two spellings
One capability, two addresses — generated from one descriptor, so they cannot disagree:
- The catalog name —
usage.get. What the SDK, the CLI, and the MCP index call it. - The wire route —
GET /usages/get. What HTTP calls it.
Call it
import { usage } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await usage.get()curl 'https://apis.vin/usages/get'Input
No input — this capability takes no request body.
Answers
A typed OK envelope carrying Usage@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 keyed — mint an anonymous key with POST /keys; no account, no email.
The door
apis.vin serves this noun on its two routes: / (the landing) · /5XYP6DGC0SG586605 (the VIN lens).
Try it
Live: answers on the wire today. A sandbox key still selects the deterministic simulated mode — drive the full outcome range with the magic triggers.
Data model
Backs the Usage entity. See the schema, relationships, and state set on usage 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.