Anyone comparing car image APIs runs into the same wall: almost nobody publishes a price list. That is not evasion so much as a property of the product. The monthly cost depends on variables that differ by an order of magnitude between customers, so providers quote rather than list. This article explains what actually drives the number, what the free options do and do not cover, and how to estimate your own bill before talking to anyone's sales team, including ours.
The four factors that drive the price
- Request volume: how many image calls per month, which mostly follows your traffic and your caching policy
- Views per vehicle: one hero angle is a different product from eight exteriors plus interior
- Feature scope: factory colours, transparency, shadow variants and lookup methods
- Licence scope: a website is one thing; quotes, printed documents and customer-kept files are another
Of the four, request volume is the one you control. An image URL that is cached in your CDN or stored in your own bucket is a request that never bills. Most integrations settle into a pattern where each vehicle-view is fetched once per catalogue update, not once per page view. That changes the arithmetic completely.
What our plans look like
| Plan | Requests / month | Views | For |
|---|---|---|---|
| Trial | Unlimited for 7 days | 1 view, 3 makes | Testing against your own data, no credit card |
| Startup | Up to 100,000 | 1 to 3 views | Early-stage products, individual pricing |
| Basic | Unlimited | Up to 11 views | Production platforms, individual pricing |
Individual pricing means the number is set by the four factors above, not that it is mysterious. The fastest way to get it is to describe your volume and views on the pricing page or in a short call.
What about free car image APIs?
The honest answer to that search: there is no free, licensed, production-grade car image API, because the underlying vehicle data and the rendering both cost money. What the free tier of the internet actually offers:
- Manufacturer press kits: free, but editorial licences and launch-spec coverage only
- Open datasets: assembled for machine learning, not licensed for commercial display
- Scraped collections: cheap until legal asks where the images came from
- Free trials: real APIs, time-boxed, which is what a trial is for
If a source is free and licensed and complete, one of the three adjectives is wrong.
Estimating your own number
Take your catalogue size, multiply by the views you will actually display, and decide how often a vehicle's images refresh. A marketplace with 40,000 listings showing four angles that re-resolves weekly makes roughly 160,000 requests a week before caching, and a fraction of that after. That estimate, plus the licence scope you need, is everything a quote requires.
Where budgets actually leak
In practice the surprises on the bill rarely come from the rate card. They come from integrations that resolve on every page view instead of caching, from serving full-resolution images into thumbnail slots, and from forgotten test environments hammering the API around the clock. All three are visible in a request log within an hour of looking, and all three are fixed in configuration rather than negotiation.
Start with the free trial against twenty of your own vehicles; the vehicle image API page covers what the integration looks like.
