// BLOG
Vehicle data, written down.
- 7
- posts.
- 6
- topics, from identity to versioning.
- September 2, 2026
- latest post.
- no feed yet
- the changelog carries API news.
- Identity
- Fluids
- Parts
- Labor
- Coverage
- API
Identity6 min read
What a VIN actually encodes, and what it does not
Seventeen characters carry the plant, the body, the restraint system and a check digit. They do not carry the oil capacity. Where identity ends and maintenance data begins.
Read the postLabor5 min read
Why a labor time needs a sample size
A book rate is one number with nothing behind it. A measured hour comes with n and a p25 to p75 spread, and the spread is the part that tells you how to schedule the bay.
ReadFluids4 min read
Capacity is not the service fill
Every manual prints two oil figures and they are not the same number. Which one the API returns, why it is the one you want on a work order, and what the filter has to do with it.
ReadIdentity5 min read
One model, two configs: what a 409 is for
A year, make and model can fit more than one car. Instead of guessing, the API hands back the candidates and lets you pick the config_key.
ReadParts4 min read
A price is a snapshot: reading price.as_of
Amount, MSRP and the date it was last confirmed. Three fields, and the third is the one that keeps a quote honest a month later.
ReadCoverage5 min read
What “covered” means, config by config
Coverage is not a make list. A vehicle is covered when its exact configuration is enriched, and the fill rate says how much of it came back.
ReadAPI3 min read
Ninety days of notice: how we version
/v1 only ever gains fields. /v0 can change while a dataset settles, and any version gets at least ninety days before it retires. What that means for the code you ship.
Read// ALSO
API news is on the changelog.
Every change to the API is announced there before it ships, and the reference at /docs is rendered from the live spec. If you would rather read code than prose, the console runs the sample endpoints with no key.