The terms that come with the key.

These terms are between you — the company whose name is on the account — and [Registered company name], trading as CarHub. Creating an account or calling the API accepts them.

If you also sign an order form or a data processing agreement with us, those documents win where they disagree with this page, in that order. Nothing said in a sales conversation changes any of the three.

One account belongs to one organisation. You are responsible for what your keys do, including calls made by anyone you gave a key to, so keep them server-side, scope them, and rotate them when people leave. A key embedded in a shipped mobile binary is a published key.

Keep your account details accurate — we send deprecation notices and incident mail to the address on file, and "we did not see it" is not a defence we can do much with. You must be able to enter a contract in your own jurisdiction, and the service is sold for business use rather than to consumers.

Build whatever product you like on top of the platform. The limits are narrow and they exist for reasons we can point at.

• Do not resell the data layer as a data feed. Lookup results are licensed to us per country for use inside your application. Republishing them, or reselling them as a dataset, breaks the licence upstream and ends your access here.
• Do not mine the API to rebuild it. No bulk enumeration of identifiers, no scraping the surface to reconstruct the underlying records, no using our outputs as training data for a competing model.
• Do not point it at people. The models are for vehicles. Using them to identify, track or profile individuals — or uploading media collected for that purpose — is prohibited regardless of what your local law permits.
• Send only media you are entitled to send, with a lawful basis for the people who appear in it. See the privacy policy.
• Do not attack the platform — no probing other accounts, no evading rate limits, no reverse engineering beyond what the law lets you do without our permission.

Every one of the 24 endpoints carries its own rate limit, so a burst of renders cannot throttle your damage detection. Your limits are on your account and we will raise them for a volume you can describe.

Reading job status and receiving webhooks is free and unlimited in the sense that matters: polling never counts against your meter. It is still a network call, so back off when we ask you to, and honour 429 and Retry-After rather than tightening the loop. Sustained abuse of a free endpoint gets throttled like anything else.

You pay for the unit you sent. Each endpoint bills on exactly one meter — per vehicle, per image, per video, per detection, per link, or free — and nothing is metered twice. Pricing lists the meter for every endpoint, and your rate card sets the price of each.

POST /v1/inspections chains all 8 stages and bills once as a blended inspection rather than as 8 separate calls. A failed job that produced no result is not billed; a job you cancel after inference has run is.

We invoice monthly in arrears against metered usage. Invoices are due 30 days from issue, in the currency on your order form, exclusive of VAT and any withholding. Query a line within 30 days and we will investigate it against the job records; after that the invoice stands. We may suspend the account for invoices more than 30 days overdue, with notice first.

Your media, your identifiers and your results stay yours. You grant us only the licence we need to run the service you called: to store, transmit and process your content so the endpoint can return a result, and to keep it for the retention window on your account.

We do not train models on your media. Not on your photographs, not on your videos, not on your corrections in the review UI — unless you opt in for a named dataset, in writing, with a scope and an end date. Nothing in the ordinary course of using the API is that opt-in.

We do keep operational metrics that carry no customer content — request counts, latencies, error rates, which endpoints run hot — and those are ours, because that is how the platform gets faster. Anything you tell us in support of a bug report is used to fix the bug.

Every model output is an estimate produced by inference. Damage detections, severity grades, repair costs, valuations and rendered images are probabilistic, and they are wrong sometimes in ways that will look obvious to a human afterwards.

So, plainly: an inspection is not a roadworthiness certificate, not a professional appraisal, not a warranty about a vehicle's condition or history, and not a legal determination of anything. Lookup results are only as accurate as the national register they came from.

Where an output feeds a decision with a legal or financial effect on somebody — settling a claim, pricing a trade-in, charging a renter for damage — keep a human in the loop and give the affected person a route to challenge it. The damage review UI ships in Layer 1 for exactly that. You are responsible for the decisions your product makes.

Inference is asynchronous by design: you get a job, you poll it or you receive a webhook. Queue times move with load, and a slow job is not an outage.

Uptime commitments, support response times and credits, if you have them, are on your order form. Without one, the service is provided on a commercially reasonable basis. We schedule maintenance outside European business hours where we can and announce anything with downtime in advance.

Paths are versioned. Inside /v1 we add endpoints and add fields to responses, and you should ignore fields you do not recognise rather than break on them. We will not remove a field or change the meaning of one inside a version.

Model weights improve continuously, so the same photograph may grade differently next month. That is the point of a hosted model, not a breach of these terms. When an endpoint has to go, we give at least 12 months' notice to the account addresses and keep the old behaviour available for the notice period.

Each of us will keep the other's non-public information — your roadmap and volumes, our rate cards, benchmarks and unreleased endpoints — confidential, use it only for this agreement, and protect it as carefully as our own. This survives the agreement by three years and does not cover what is already public or independently developed.

We would like to name you as a customer; we will ask first, and we will stop if you ask us to.

The agreement runs from your first call until either of us ends it. You can close the account at any time and stop being billed for anything metered after that. We can end it on 30 days' notice, or immediately if you breach acceptable use, put the platform or its upstream licences at risk, or leave an invoice unpaid after notice.

We may suspend a key immediately, without notice, if it is being used in a way that threatens the platform or another customer, and we will tell you why as soon as we have stopped it.

On termination you have 30 days to export your data through the API. After that we delete it on the schedule in the privacy policy. Fees already incurred remain payable, and clauses that only make sense afterwards — confidentiality, liability, governing law — survive.

We warrant that we provide the service with reasonable skill and care and that we have the right to license it to you. Beyond that, and beyond any warranty your order form adds, the service is provided as is: we do not warrant that inference is accurate, that a provider's register is complete, or that the platform is uninterrupted or error-free.

Neither of us is liable for indirect or consequential loss, lost profits, lost revenue, or loss of data that a reasonable backup would have prevented. Each party's total liability is capped at the fees paid or payable in the 12 months before the claim.

Those limits do not apply to death or personal injury caused by negligence, to fraud, to your obligation to pay, or to anything else that cannot be limited by law.

We update these terms as the platform changes. Material changes are emailed to account holders at least 30 days before they take effect; continuing to call the API after that is acceptance. If a change genuinely does not work for you, tell us within those 30 days and you can end the agreement without penalty for the remainder of the term.

These terms are governed by the laws of [Jurisdiction], and the courts of [Jurisdiction] have exclusive jurisdiction. Neither of us may assign the agreement without the other's consent, except to a successor of the whole business.

If a clause turns out to be unenforceable, the rest stands. Questions about any of this: legal@carhub.example.