Put real labor data inside your platform

If you build shop-management software, an estimating tool, or a fleet product, your users hit the same wall every day: how many hours does this job take? We license the Open Labor Project database to platforms β€” flat-rate labor times, torque specs, fluids, DTC data, and DVI-to-estimate mapping β€” served from a synced copy on your infrastructure, priced per active shop instead of per lookup.

20M+
Labor-time entries
39k+
Vehicles, 1955–present
Honest
Confidence tier on every row
Zero
Per-lookup metering

Built for a synced local copy

We don't make your product depend on our uptime. The integration is a one-time bulk export plus a nightly delta β€” your shops are served from your own database, and ours just keeps it true:

1Seed once with GET /v1/bulk/labor-times β€” cursor-paginated, ordered by stable record IDs.
2Sync nightly with GET /v1/changes?since=… β€” updates and deletions (tombstones), so a cached copy never quietly rots.
3Key everything on our stable UUIDs and updatedAt. When we verify a number upward, your copy learns it the same night.
4Optional live calls for the long tail: VIN decode, fuzzy job search, engine-code lookup, and /v1/dvi-lookup to turn an inspection finding into a ready-to-quote estimate line.

The confidence tier is the product

Every row tells you how it was derived: high means verified by our blind-panel process or a real source and defensible in writing; estimated means a starting point, labeled as such. We would rather show you an honest gap than an invented number β€” and when your shops report an error, it's typically reproduced and fixed the same day, with the correction flowing to your copy through the sync feed. Read how the data is made at /data-provenance/.

Where we complement the incumbents

Many platforms run us alongside an existing labor-guide contract. We cover what those leave out: classics back to 1955 (pre-OBD2 is a specialty), current-year EVs and hybrids, commercial chassis (Transit, Sprinter, ProMaster, E-series and F-59 cutaways β€” all panel-verified), plus DVI mapping and honest confidence labels no incumbent publishes. Start us as the supplementary layer; grow us as the economics prove out.

How licensing works

Evaluate free.

Request a key at /developers and test against real vehicles today β€” no sales call required. Tell us you're a platform and we'll enable the bulk and sync endpoints for the evaluation.

Pilot on a slice.

Wire the sync, put our numbers in front of a subset of your shops for 60–90 days, and measure. Your developers can build the whole loop from the public docs.

License per shop.

A simple redistribution license priced to your active shop count β€” typically a few dollars per shop per month with volume bands and a modest floor, so the cost tracks your footprint instead of your query volume. White-label allowed. No per-lookup anxiety, ever.

Building a platform?

Tell us what you're building and roughly how many shops you serve β€” the founder answers, usually same day.

[email protected]

Or start immediately: get an API key Β· integration guide for platforms