canonical: https://jentic.com/apis/mercedes-benz.com/mercedes-benz-vehicle-image

# Mercedes Benz Vehicle Image

Jentic publishes the only available OpenAPI specification for Vehicle Image, keeping it validated and agent-ready. The Mercedes-Benz Vehicle Image API returns original Mercedes-Benz vehicle imagery for a given FIN or VIN, including exterior and interior views with controllable perspective, time-of-day, and background. It also exposes component imagery for engine, paint, rim, trim, upholstery, and equipment options, so dealer sites and configurators can render an accurate, vehicle-specific gallery without sourcing photos manually.

## For AI agents

Fetch official Mercedes-Benz exterior, interior, and component images by FIN or VIN with perspective and night-mode parameters.

## Scope

Does not handle pricing, inventory levels, vehicle diagnostics, or dealer location lookups - use for fetching original Mercedes-Benz vehicle and component imagery only.

## Capabilities

- Retrieve exterior vehicle images by FIN or VIN with selectable perspective and day or night background
- Pull interior cabin images and component close-ups for a specific vehicle identifier
- Render engine, paint, rim, trim, upholstery, and equipment imagery for sales and configurator pages
- Drive a build-and-price tool with images that match the actual vehicle specification
- Populate dealer inventory listings with manufacturer-original photography instead of stock images

## Use cases

### Dealer Inventory Galleries

Dealer websites can populate vehicle detail pages with manufacturer-original Mercedes-Benz photography keyed to each car's FIN or VIN. Instead of relying on stock photos or staff photography, the API returns exterior, interior, and component shots that exactly match the build, with controllable perspective and night or day backgrounds. Setup typically takes a day for a single integration.

Example prompt: Call GET /{finorvin}/vehicle for VIN WDD2050471F123456 and return the exterior image URL for the front-three-quarter perspective.

### Build-and-Price Configurator

Online configurators need the rendered image to update as buyers change paint, rim, trim, upholstery, and equipment selections. The Vehicle Image API returns a component-specific image for each option so the configurator gallery reflects the current build state. Component endpoints under /{finorvin}/components cover engine, paint, rim, trim, upholstery, and equipment.

Example prompt: Call GET /{finorvin}/components/paint and GET /{finorvin}/components/rim for the active configuration and update the gallery thumbnails.

### Marketing Asset Pipeline

Marketing teams producing campaign creative for specific models can pull the canonical Mercedes-Benz imagery directly rather than coordinating photo shoots for every variant. The API supports selecting perspective and background so the same VIN can be rendered for hero banners, social posts, and email templates with consistent treatment.

Example prompt: Retrieve a daytime exterior front-three-quarter image and a matching night-time rear-three-quarter image for VIN WDD2050471F123456 for a launch campaign.

### Agent-Driven Vehicle Listing Enrichment

An AI agent assembling a vehicle listing or comparison page can call the Vehicle Image API via Jentic to fetch the matching exterior, interior, and component images for each FIN or VIN. The agent searches Jentic for the image operation, loads the schema, and executes the request without writing custom Mercedes-Benz client code.

Example prompt: Search Jentic for 'fetch Mercedes vehicle image by VIN', load the operation schema, and execute GET /{finorvin}/vehicle with finorvin set to the listing's VIN.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{finorvin}/vehicle` | Retrieve exterior or interior vehicle image |
| GET | `/{finorvin}/components` | List available component images for a vehicle |
| GET | `/{finorvin}/components/engine` | Get engine component image |
| GET | `/{finorvin}/components/paint` | Get paint component image |
| GET | `/{finorvin}/components/rim` | Get rim component image |
| GET | `/{finorvin}/components/trim` | Get trim component image |
| GET | `/{finorvin}/components/upholstery` | Get upholstery component image |
| GET | `/{finorvin}/components/equipments` | Get equipment component image |

## Key resources

- **Perspectives** — Exterior and interior vehicle images for a FIN or VIN, with selectable perspective and time-of-day
- **Components** — Component-level images for engine, paint, rim, trim, upholstery, and equipment options on the configured vehicle

## Why Jentic

- **Setup:** The Mercedes-Benz Vehicle Image API needs no key, but wiring it by hand still means coding the FIN/VIN and component paths against the image_tryout host and handling retries and errors yourself. Through Jentic you install once, import the Vehicle Image API from the API Directory, and your agent calls it through the same path as your keyed APIs.
- **Permission scoping:** The Vehicle Image API puts the FIN or VIN in the URL path (/{finorvin}/vehicle), so a rule can pin your agent to one vehicle's imagery. Every operation here is a read-only GET for vehicle and component images, so a rule can grant engine, paint, rim, and trim lookups without exposing any write.
- **Credential handling:** This API is unauthenticated, so there is no credential to store, and your own Jentic One instance still runs the call through the same audited path as your keyed APIs. No key or token enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'fetch a Mercedes vehicle image by VIN' or 'get the engine component image', and Jentic returns the matching Vehicle Image operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mercedes-Benz Configurator API** — Build vehicle configurations whose FIN or VIN is then passed to the Vehicle Image API
- **Mercedes-Benz Dealer API** — Look up dealer inventory and pair listings with Vehicle Image renderings
- **Mercedes-Benz Diagnostics API** — Different Mercedes-Benz API focused on diagnostic data rather than imagery

## FAQ

### Why is there no official OpenAPI spec for Vehicle Image?

Mercedes-Benz does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Vehicle Image via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Vehicle Image API use?

The spec exposes the public image_tryout sandbox at https://api.mercedes-benz.com/image_tryout/v1/vehicles, which does not declare a security scheme. Production access from Mercedes-Benz Developer requires an API key managed in the Mercedes-Benz developer portal; through Jentic, that key is stored in the credential vault so agents call the API with a scoped token rather than a raw key.

### Can I fetch component images like paint and rims with the Vehicle Image API?

Yes. The API exposes dedicated endpoints under /{finorvin}/components for engine, paint, rim, trim, upholstery, and equipment, plus a /{finorvin}/components index. Each returns the component image for the configuration tied to that FIN or VIN.

### What are the rate limits for the Vehicle Image API?

The OpenAPI spec does not declare rate limits. The Mercedes-Benz Developer portal applies tier-specific quotas to the production endpoint and the tryout sandbox is intended for low-volume evaluation, so production rollouts should plan for caching the returned images per VIN.

### How do I retrieve a vehicle image by VIN through Jentic?

Install the SDK with pip install jentic, search for 'fetch Mercedes vehicle image by VIN', load the GET /{finorvin}/vehicle operation, and execute it with the finorvin path parameter set to the target VIN. Jentic handles authentication and returns the image URL.

### Can the Vehicle Image API render night-time or different perspectives?

Yes. The vehicle and component endpoints accept query parameters that control perspective and time-of-day, so the same FIN or VIN can be rendered as a day or night exterior in multiple angles for galleries and configurators.

### Can I limit what my agent is allowed to do with the Vehicle Image API?

Yes. Jentic One runs on your own infrastructure, so your rules decide which Vehicle Image operations and credentials the agent may use. Because the FIN or VIN sits in the URL path (/{finorvin}/vehicle), you can pin the agent to a single vehicle's imagery, and since every operation is a read-only GET you can grant just the lookups you want, such as the engine, paint, rim, and trim component endpoints, without exposing any write. The agent only ever calls the endpoints your configuration allows.