Documentation
Services
services.tiers
REST
ShippingPOST /api/v1/services/tiersMCP tool
Liveservices.tiersExposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Services domain.
Operating contract
THE REAL PRICES FOR A TIERED SERVICE. A tiered service has no single price — base_price on it is null — and quoting one number for a Miata and a Suburban is the most expensive mistake available in this domain.
Each row is one vehicle size: what the customer pays, what the shop's material costs, how much film it takes and how many labour hours it is expected to take. Those last three are the install-rate numbers, and they are STAFF-ONLY: never repeat unit_cost, material_ft or the margin they imply to a customer.
A size that is missing from this list is a size the shop has NOT priced. That is not free and it is not the cheapest tier — it is unpriced, and the honest move is to say so and let the shop quote it.
For a flat, per-square-foot or per-hour service this comes back empty and pricing_model on services.get tells you the price is the base price instead. For a custom service it comes back empty because the price is decided per job.
labor_hours is what the scheduling agent's margin projection is built on, which is why a service with none produces low-confidence suggestions.
One service's tiers, all of them, so nothing is truncated.
Who may call it
- Permission
shop.manageThe caller must hold shop.manage at the ACT level. A read-only dashboard grant on the same section is refused.- Plan
- Every planNo plan gate. Available on every Service VIN plan.
- Retries
naturalNaturally idempotent — running it twice leaves the same world as running it once. A retrying integration needs no key.- Rate class
readCounted against the read budget — the widest of the four.
Input
| Field | Type | Description |
|---|---|---|
| service_idrequired | stringuuid | The service, as returned by services.list or quotes.catalog. |
Output
| Field | Type | Description |
|---|---|---|
| service_id | string | — |
| pricing_model | string | — |
| items | object[] | — |
| items[].id | string | — |
| items[].vehicle_type | string | — |
| items[].price | number | — |
| items[].unit_cost | number | null | — |
| items[].material_ft | number | null | — |
| items[].labor_hours | number | null | — |
Examples
Built from this capability's own schema — required fields and the ones carrying a default, and nothing invented. Paste one and it validates.
export SERVICEVIN_API_KEY=svk_live_…
curl -X POST https://www.servicevin.com/api/v1/services/tiers \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"service_id":"9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"}'const res = await fetch("https://www.servicevin.com/api/v1/services/tiers", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"service_id": "9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"
}),
});
// Success and failure are both envelopes. Switch on error.code, never
// on error.message — the codes are stable, the messages are for people.
const payload = await res.json();
if (!res.ok) throw new Error(payload.error.code);
const data = payload.data;import os, requests
res = requests.post(
"https://www.servicevin.com/api/v1/services/tiers",
headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
json={
"service_id": "9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"
},
timeout=30,
)
payload = res.json()
if not res.ok:
raise RuntimeError(payload["error"]["code"])
data = payload["data"]{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "services.tiers",
"arguments": {
"service_id": "9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"
}
}
}Refusals
The four gates run in this order on every surface, and the order is not arbitrary — see Authentication.
| Status | Code | When |
|---|---|---|
| 404 | not_found | The id is unknown, or the feature is not enabled for this account. Deliberately the same answer for both. |
| 403 | forbidden | This login does not hold shop.manage. |
| 422 | validation_error | An argument was wrong. The message names the field. |
| 429 | rate_limited | Too many read calls. Back off and retry. |
| 500 | internal_error | Something failed on our side. Nothing was changed. |