Every function in the shop, available to your code and to your AI.

Zero to an authenticated call#

Mint a key in Settings → API keys, put it in your shell, and call /me. A 200 naming your shop means you are connected.

export SERVICEVIN_API_KEY=svk_live_…

curl https://www.servicevin.com/api/v1/me \
  -H "Authorization: Bearer $SERVICEVIN_API_KEY"

Then read Getting started, which explains what a capability is before you call one.

The surfaces#

Five ways in, one registry behind them, and one audited path through the same four gates — ring, plan, permission, scope — whichever door a call comes through.

A shipping endpoint is documented here because its contract is settled and generated from the same registry — build against it, and it answers the day it lands. The status on this page is read from the route file itself, not from a note somebody remembered to update.

Guides#

Capability domains#

Grouped the way the registry groups them: the customer and their car, the money funnel, the day on the floor, the shop itself, then everything that reaches outward.

For a reader that is not a person#

Half the traffic here is an agent, a crawler or an answer engine. Four documents exist for them, and every one is generated from the registry rather than written beside it.

• /llms-full.txtThe whole reference — every guide and every capability, contract, fields and examples — as one plain-text document. One fetch, nothing withheld.
• /llms.txtThe index: what is here, and the URL of each page, in the llms.txt convention.
• /openapi.jsonThe OpenAPI 3.1 document for the REST surface, generated from the same spec the routes are checked against.
• /.well-known/mcp.jsonBoth MCP servers, described for discovery — transport, auth and what each one is for.