docs.vin

reputation

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

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

Identity

Nounreputation
PillarServices (facets: 1 services)
Capabilities1 — 0 live · 1 sandbox · 0 declared
EntitiesDealer
Doorsaggregator.vin
SDKVin.reputation.* from apis.vin
Address/catalog/reputation#{action} — the anchor IS the wire name minus reputation.

Events

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

Discover & read

monitor

reputation.monitor · POST /reputations/monitor · gate key · sandbox · answers ReputationMonitor@1

No input — this capability takes no request body.

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

EmitsReputation.monitored@1.

the SDK — reputation.monitor
import { reputation } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await reputation.monitor()
POST /reputations/monitor
curl -X POST https://apis.vin/reputations/monitor \
  -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-17T00:18:27.798Z · HTTP 200
{
  "type": "OK",
  "answers": "ReputationMonitor@1",
  "value": {
    "noun": "reputation",
    "asOf": "2026-08-10",
    "dealerId": "DLR-b9066ade",
    "rooftopIds": [
      "DLR-b9066ade"
    ],
    "dealerLicense": "DL-7bcdd2ef",
    "auctionStanding": "active",
    "monitor": {
      "rating": {
        "ratingTenths": 46,
        "outOfTenths": 50,
        "reviews": 100
      },
      "feedId": "RF-7bddf297",
      "status": "monitored"
    }
  },
  "evidence": {
    "noun": "reputation",
    "asOf": "2026-08-10",
    "dealerId": "DLR-b9066ade",
    "rooftopIds": [
      "DLR-b9066ade"
    ],
    "dealerLicense": "DL-7bcdd2ef",
    "auctionStanding": "active",
    "monitor": {
      "rating": {
        "ratingTenths": 46,
        "outOfTenths": 50,
        "reviews": 100
      },
      "feedId": "RF-7bddf297",
      "status": "monitored"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "back-office-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.

Dealer

Modeled

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

Reputation · Class model

Reputation · State machine


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