Terms of service

1. The service

Vehicles.dev is a paid, server-to-server HTTP API providing vehicle identity, factory specifications, recalls, market value, depreciation, ownership costs, dealer listings, photos, and vehicle-history reports. Access is authenticated with an API key you mint and manage in your dashboard. You are responsible for keeping keys secret and for all usage billed to your account until a key is revoked.

2. Plans and billing

• Usage is metered per request against the published per-endpoint price catalog. Each call you make — including every valuation refresh in a recurring or scheduled integration — is a billable event.
• A standard commercial plan covers use of the API inside your own product or internal systems, including consumer-facing and subscription products that present your own analysis built on our responses.
• You are responsible for the request volume your integration generates. If a product design implies sustained or scheduled querying, contact us so we can confirm the right plan and rate limits up front.

3. Building on the data (permitted)

You may use API responses as inputs to your own analysis and present the results to your customers. On a standard plan, and without any additional license, you may:

• Compute and display your own derived values, scores, ranges, and insights — for example your own estimated value, a summarized asking-price range, or a statement that you analyzed a given number of comparable vehicles.
• Store the derived outputs your product computes (your own values and their history) inside a customer’s account for as long as you like. Those outputs are yours.
• Periodically re-query an endpoint to keep your own analysis current and to maintain a historical trend of your derived values. Each refresh is a normal metered call.
• Generate customer-facing reports (in-app or as PDFs) whose figures and narrative are your product’s analysis rather than a reproduction of our raw records.

4. Redistributing the data (separate license)

The distinction is between building on the data and re-publishing it. Storing your derived output is unrestricted; retaining or re-serving our raw output as a parallel copy of the dataset is not. The following require a separate written redistribution agreement:

• Reselling, sublicensing, or otherwise providing third parties access to the API.
• Offering bulk or downloadable exports of our raw responses or records.
• Presenting our Listings results as a standalone, browsable, or searchable listings database.
• Retaining raw API responses to build a persistent standalone copy of the dataset, beyond the caching allowed in section 5.

Need any of the above? Email support@vehicles.dev and we will put a redistribution license in writing.

5. Caching and retention

You may cache raw API responses to power a live report, session, or account view and to avoid redundant calls. What you may not do is retain those raw responses to assemble a standalone copy of our dataset that could substitute for the API. As a rule of thumb: cache freely to serve your product; do not warehouse our data. Your own derived values are not subject to this limit and may be retained indefinitely.

6. Attribution

Attribution is not required inside your application or in reports you generate for your customers. A discreet “Vehicle data powered by Vehicles.dev” is welcome and appreciated, but optional. Do not imply that Vehicles.dev endorses, certifies, or is responsible for your product’s conclusions.

7. Acceptable use

• Do not circumvent, disable, or misreport usage metering, or exceed plan rate limits.
• Do not use the API to build a product whose primary purpose is to compete with the API as a raw data source.
• Do not use the data to identify, profile, or make eligibility decisions about individuals. This is a vehicle-data service, not a consumer-reporting or background-check tool.
• Do not misrepresent our data or your derived outputs as official or authoritative records.

8. Third-party data and accuracy

• Specifications, recalls, and ownership costs are derived from public NHTSA and EPA data and are passed through with their own accuracy limits, which are described on each endpoint in the documentation.
• Photo URLs point at CDNs owned by the source marketplace. We link to them; we do not license the imagery, and it is not ours to sublicense.
• Market value and depreciation figures are model estimates of asking prices, not realized transaction prices or a guarantee of value. You are responsible for how you present them to your customers.
• The API is provided on an as-is basis. To the extent permitted by law, Vehicles.dev is not liable for decisions made on the basis of the data or your derived outputs.

9. Changes and contact

We may update these terms as the product evolves; the “Last updated” date above reflects the current revision, and material changes will be communicated to account holders. For a redistribution license, a data-processing agreement, vendor-security paperwork, or anything else not covered here, email support@vehicles.dev and we will put it in writing. The per-endpoint usage notes in the documentation remain part of these terms.