docs.vin

mechanicsLien

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

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

Identity

NounmechanicsLien
PillarServices (facets: 3 services · 1 commerce)
Capabilities4 — 0 live · 4 sandbox · 0 declared
EntitiesLien
Doorsaggregator.vin
SDKVin.mechanicsLien.* from apis.vin
Address/catalog/mechanicsLien#{action} — the anchor IS the wire name minus mechanicsLien.

Events

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

Apply & book

file

mechanicsLien.file · POST /mechanics-liens/file · gate key · sandbox · answers MechanicsLienFile@1

No input — this capability takes no request body.

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

EmitsMechanicsLien.filed@1.

the SDK — mechanicsLien.file
import { mechanicsLien } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await mechanicsLien.file()
POST /mechanics-liens/file
curl -X POST https://apis.vin/mechanics-liens/file \
  -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-16T14:50:09.926Z · HTTP 200
{
  "type": "OK",
  "answers": "MechanicsLienFile@1",
  "value": {
    "lienId": "mechanicsLien_f655a89d",
    "lienholderId": "lender_0b81c9c3",
    "position": 560,
    "perfectedAt": "2027-04-07T00:00:00.000Z",
    "releasedAt": "2027-04-07T00:00:00.000Z"
  },
  "evidence": {
    "lienId": "mechanicsLien_f655a89d",
    "lienholderId": "lender_0b81c9c3",
    "position": 560,
    "perfectedAt": "2027-04-07T00:00:00.000Z",
    "releasedAt": "2027-04-07T00:00:00.000Z"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "mechanics-lien-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Lifecycle & state

release

mechanicsLien.release · POST /mechanics-liens/release · gate key · sandbox · answers MechanicsLienRelease@1

No input — this capability takes no request body.

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

EmitsMechanicsLien.released@1.

the SDK — mechanicsLien.release
import { mechanicsLien } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await mechanicsLien.release()
POST /mechanics-liens/release
curl -X POST https://apis.vin/mechanics-liens/release \
  -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-16T14:50:09.927Z · HTTP 200
{
  "type": "OK",
  "answers": "MechanicsLienRelease@1",
  "value": {
    "lienId": "mechanicsLien_5ee07d4f",
    "lienholderId": "lender_3d31c5c5",
    "position": 635,
    "perfectedAt": "2026-11-08T00:00:00.000Z",
    "releasedAt": "2026-11-08T00:00:00.000Z"
  },
  "evidence": {
    "lienId": "mechanicsLien_5ee07d4f",
    "lienholderId": "lender_3d31c5c5",
    "position": 635,
    "perfectedAt": "2026-11-08T00:00:00.000Z",
    "releasedAt": "2026-11-08T00:00:00.000Z"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "mechanics-lien-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

foreclose

mechanicsLien.foreclose · POST /mechanics-liens/foreclose · gate key · sandbox · answers MechanicsLienForeclose@1

No input — this capability takes no request body.

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

EmitsMechanicsLien.foreclosed@1.

the SDK — mechanicsLien.foreclose
import { mechanicsLien } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await mechanicsLien.foreclose()
POST /mechanics-liens/foreclose
curl -X POST https://apis.vin/mechanics-liens/foreclose \
  -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-16T14:50:09.926Z · HTTP 200
{
  "type": "OK",
  "answers": "MechanicsLienForeclose@1",
  "value": {
    "lienId": "mechanicsLien_c5993165",
    "lienholderId": "lender_72627f7b",
    "position": 988,
    "perfectedAt": "2026-12-01T00:00:00.000Z",
    "releasedAt": "2026-12-01T00:00:00.000Z"
  },
  "evidence": {
    "lienId": "mechanicsLien_c5993165",
    "lienholderId": "lender_72627f7b",
    "position": 988,
    "perfectedAt": "2026-12-01T00:00:00.000Z",
    "releasedAt": "2026-12-01T00:00:00.000Z"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "mechanics-lien-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

noticeToOwner

mechanicsLien.noticeToOwner · POST /mechanics-liens/notice-to-owner · gate key · sandbox · answers MechanicsLienNoticeToOwner@1

No input — this capability takes no request body.

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

EmitsMechanicsLien.ownerNoticed@1.

the SDK — mechanicsLien.noticeToOwner
import { mechanicsLien } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await mechanicsLien.noticeToOwner()
POST /mechanics-liens/notice-to-owner
curl -X POST https://apis.vin/mechanics-liens/notice-to-owner \
  -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-16T14:50:09.927Z · HTTP 200
{
  "type": "OK",
  "answers": "MechanicsLienNoticeToOwner@1",
  "value": {
    "lienId": "mechanicsLien_5f1ed51d",
    "lienholderId": "lender_d79d9243",
    "position": 418,
    "perfectedAt": "2027-07-29T00:00:00.000Z",
    "releasedAt": "2027-07-29T00:00:00.000Z"
  },
  "evidence": {
    "lienId": "mechanicsLien_5f1ed51d",
    "lienholderId": "lender_d79d9243",
    "position": 418,
    "perfectedAt": "2027-07-29T00:00:00.000Z",
    "releasedAt": "2027-07-29T00:00:00.000Z"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "mechanics-lien-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.

Lien


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