listing.status
Status — the data face of listing (know it), at `GET /listings/status`.
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/listing#status 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 listing · Pillar Data
Descriptor
The catalog row, rendered. This is the same descriptor that answers GET /catalog?select=….
| Field | Value |
|---|---|
| Noun | listing |
| Facet | Data |
| Side | supply |
| Pillar | Data |
| Kind | fact |
| Status | live |
| Gate | none |
| Mandate | none |
| Price | not posted — see /pricing |
| Door | listings.vin |
| Motions | B2A2C · B2A2B · B2A2D |
The two spellings
One capability, two addresses — generated from one descriptor, so they cannot disagree:
- The catalog name —
listing.status. What the SDK, the CLI, and the MCP index call it. - The wire route —
GET /listings/status. What HTTP calls it.
Call it
import { listing } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await listing.status({"vin":"W1Y4EDHY4NT115660"})curl 'https://apis.vin/listings/status?vin=W1Y4EDHY4NT115660'Input
| Field | Type | Required | Notes |
|---|---|---|---|
vin | string | no | — |
Answers
A typed OK envelope carrying ListingStatus@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 open — no gate; a keyless read.
The door
listings.vin serves this noun on its two routes: / (the landing) · /W1Y4EDHY4NT115660 (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 Listing entity. See the schema, relationships, and state set on listing 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.