connection.accounts

Accounts — the services face of connection (do it), at `GET /connections/accounts`.

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/connection#accounts 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 connection · Pillar Services

Descriptor

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

Field	Value
Noun	`connection`
Facet	Services
Side	`facilitator`
Pillar	Services
Kind	`capability`
Status	`sandbox`
Gate	`key`
Mandate	`none`
Price	free — `$0.00`, posted
Door	`apis.vin`
Motions	`B2A`

The two spellings

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

The catalog name — connection.accounts. What the SDK, the CLI, and the MCP index call it.
The wire route — GET /connections/accounts. What HTTP calls it.

Call it

the SDK — connection.accounts

import { connection } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await connection.accounts({"id":"id","action":"read"})

GET /connections/accounts

curl 'https://apis.vin/connections/accounts?id=id&action=read'

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-16T14:50:09.705Z · HTTP 200

{
  "type": "OK",
  "answers": "Connection@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "connection",
    "asOf": "2026-08-10",
    "connId": "conn_c0f1966c",
    "status": "active",
    "scopes": [
      "read",
      "pull",
      "push"
    ]
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "connection",
    "asOf": "2026-08-10",
    "connId": "conn_c0f1966c",
    "status": "active",
    "scopes": [
      "read",
      "pull",
      "push"
    ]
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "connection-wire-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": true
  }
}

Input

Field	Type	Required	Notes
`id`	`string`	no	conn_… to read; omit to list the caller's connections
`action`	`string`	no	one of `read`, `list`, `revoke`, `health`

Answers

A typed OK envelope carrying Connection@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) · /KM8R7DGE0RU709816 (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:

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

Data model

Backs the Connection entity. See the schema, relationships, and state set on connection 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.

connection.accounts

On this page