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

# 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 photography for a vehicle addressed by FIN or VIN. It serves whole-vehicle images with controllable perspective and lighting, plus component renders for engine, paint, rim, trim, upholstery, and equipment. The output is the same studio imagery used on mercedes-benz.com, which keeps third-party listings and configurator UIs visually consistent with the official brand.

## For AI agents

Fetch official Mercedes-Benz vehicle and component images by FIN/VIN across 8 endpoints with controllable perspective and lighting.

## Scope

Does not handle vehicle configuration, telematics, dealer search, or order fulfilment - use for retrieving Mercedes-Benz vehicle and component imagery by FIN/VIN only.

## Capabilities

- Retrieve a whole-vehicle image for a Mercedes-Benz FIN/VIN with a chosen perspective
- Render component-level images for engine, paint, rim, trim, and upholstery on the configured vehicle
- Generate equipment-specific imagery to illustrate option packages on a build
- Switch between day and night lighting variants for marketing or comparison shots
- Embed brand-consistent Mercedes-Benz imagery inside dealer or comparison sites without licensed photo libraries

## Use cases

### Configurator-aligned imagery

Sites that integrate the Mercedes-Benz Car Configurator pair it with the Vehicle Image API so each option choice updates the on-screen render. Calls to /{finorvin}/components/paint, /rim, /trim, and /upholstery return fresh imagery for the new combination, keeping the visual preview in sync with the saved configuration.

Example prompt: After the user changes paint, GET /{finorvin}/components/paint to retrieve the updated render and replace the on-screen image.

### Dealer inventory listings

Dealer websites use the API to display official Mercedes-Benz photography on their inventory listings instead of stock or smartphone photos. /{finorvin}/vehicle returns the matched whole-vehicle image and component endpoints surface engine and equipment details on the spec tab.

Example prompt: GET /{finorvin}/vehicle for the inventory FIN to fetch the hero image, and GET /{finorvin}/components/engine for the engine bay shot.

### Marketing creative automation

Marketing teams generate model-specific creative at scale by iterating FINs and pulling a consistent set of perspectives and components. The /perspectives and /components endpoints provide enough variety for a hero, two angle shots, and three close-ups per vehicle without commissioning new photography.

Example prompt: For each FIN in the campaign list, GET /{finorvin}/vehicle, /{finorvin}/components/engine, /{finorvin}/components/rim, and /{finorvin}/components/upholstery, then upload the four files to the asset library.

### Agent-driven image preview via Jentic

An AI assistant uses Jentic to fetch a Mercedes-Benz vehicle image during a sales conversation. The agent calls /{finorvin}/vehicle by intent, receives a render URL, and embeds it in the chat reply. Jentic securely stores the apiKey so the agent never handles the credential.

Example prompt: Search Jentic for 'show mercedes-benz image by vin', load the /{finorvin}/vehicle schema, execute it with the customer's FIN, and return the image URL.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{finorvin}/vehicle` | Get whole-vehicle image for a FIN/VIN |
| GET | `/{finorvin}/components` | List available component images |
| GET | `/{finorvin}/components/paint` | Render the paint component |
| GET | `/{finorvin}/components/rim` | Render the rim component |
| GET | `/{finorvin}/components/upholstery` | Render the upholstery component |

## Key resources

- **Vehicle** — Whole-vehicle imagery for a FIN/VIN with controllable perspective and lighting
- **Components** — Component-level renders: engine, paint, rim, trim, upholstery, and equipments
- **Perspectives** — Camera angle and lighting variants for whole-vehicle images

## Why Jentic

- **Setup:** Wiring the Mercedes-Benz Vehicle Image API by hand means obtaining a developer-portal apiKey, sending it with each request against the image_tryout host, and assembling the FIN/VIN and component paths yourself. Through Jentic you install once, import the Vehicle Image API from the API Directory, store the apiKey once, and your agent calls it.
- **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 paint, rim, and upholstery lookups without exposing any write.
- **Credential handling:** Your Mercedes-Benz apiKey is stored once, encrypted, by your own Jentic One instance and injected at request time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'show a Mercedes image by VIN' or 'render the paint component', and Jentic returns the matching Vehicle Image operation with its FIN/VIN and component parameters so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Car Configurator** — Builds the saved configurations whose component images the Vehicle Image API renders.
- **Dealer** — Routes the customer to a dealer once a vehicle render and configuration are ready.
- **CarsXE** — Multi-brand vehicle imagery and VIN data covering many manufacturers, not just Mercedes.

## 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 Mercedes-Benz Vehicle Image API use?

The Image API uses an apiKey from the Mercedes-Benz developer portal in the request header. Jentic securely stores the apiKey and injects it at request time so the credential never reaches the agent.

### Can I render only a vehicle's rims or paint with the Image API?

Yes. The /{finorvin}/components endpoints render specific parts on demand - `/components/rim` for wheels, `/components/paint` for body colour, `/components/upholstery` for interior, and `/components/trim` for trim packages.

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

Numeric limits are not in the spec. Production traffic is throttled per developer portal contract; the tryout host is intended for evaluation rather than high-volume rendering.

### How do I display a Mercedes-Benz vehicle image in my app through Jentic?

Search Jentic for 'show mercedes-benz image by vin', load the /{finorvin}/vehicle schema, and execute it with the FIN. The response gives the agent the image URL or binary to embed in the UI.

### Can I switch between day and night perspectives?

Yes. The Perspectives tag exposes parameters to alter camera angle and lighting (including day/night variants), so the same FIN can be rendered for hero, comparison, or marketing creative.

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

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials the agent may use. Because this API puts the FIN or VIN 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 for whole-vehicle and component renders, you can grant paint, rim, trim, and upholstery lookups without exposing any write. The apiKey stays with your instance and is injected at request time, so the agent calls only the endpoints your rules allow.