Partners

We do not hold every piece of this.

CarHub joins model endpoints, sourced vehicle data and front-end components. Partners can contribute data, deliver integrations, embed the platform or discuss a branded product surface. Four tracks, depending on which side you are on.

4 tracks · technical fit before commercial terms

The tracks

Pick the one that describes what you already have.

01

Data providers

VIN, valuation, history, compliance and parts data sources

Layer 3 normalises supported vehicle-data sources into one schema behind one key. If you hold authoritative data in one of the 9 domains — for one market or many — that is a supply conversation.

You bring
Coverage in a market we do not have, with a documented schema and a rate limit we can build against.
You get
A defined integration route for making that data available through the corresponding CarHub workflows.
02

Implementation partners

Agencies and integrators shipping vehicle products for clients

The models return data; something has to put it in front of an end customer. Teams that already build for dealer groups, insurers or fleets can deliver the 4 SDKs of Layer 1 as part of a project instead of writing a 360 player and a guided-capture flow from scratch.

You bring
Delivery capacity and a client base that needs this built, not explained.
You get
Reusable APIs and SDK components to deliver without rebuilding the common vehicle workflow surface.
03

Technology partners

DMS, CRM, auction and inspection platforms

If your platform already holds the vehicle record, the fastest path is a native integration rather than a per-customer one. One key on your side, the endpoints exposed as features on ours, and your users never leave your product.

You bring
An existing surface where vehicles are already managed.
You get
Inference and data features you did not have to train, host or license.
04

White-label and resale

Vendors selling inspection or listing products under their own brand

Supported components can carry customer branding, and reports can export under that identity. The exact resale surface and permitted use are defined in the commercial terms.

You bring
A market and a brand your customers already trust.
You get
A composable product surface with branding, pricing and support boundaries agreed in writing.

How it starts

A key before a contract.

You should know the integration works before either side negotiates. The order is deliberate.

  1. 01

    Tell us the overlap

    Which track, which market, and what you already have in production. A paragraph is enough to know whether this is worth a call.

  2. 02

    Technical fit

    We map your surface against the endpoints and the data schema, and say plainly where the gaps are before anyone signs anything.

  3. 03

    Sandbox key

    A real key against real endpoints. Build the integration far enough to know it works, before commercial terms.

  4. 04

    Terms

    Pricing, support boundaries and who owns the customer relationship — written down, in one document.

The programme is still being written. There is no partner directory or certification tier yet — if you want in early, that is an advantage rather than a problem.

Tell us where we overlap.

One paragraph on what you run and which track fits. We will come back with the technical gaps first and the commercial conversation second.

Get a sandbox keySee what you would build on