Vehicle Image

Name: Vehicle Image API
Brand: Vehicle Image
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage ProcessingapiKey8 EndpointsREST

For Agents

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

Connect the Vehicle Image to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Vehicle Image, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Vehicle Image API.

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

GET STARTED

Start building with Vehicle Image API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Vehicle Image, keeping it validated and agent-ready.

The Mercedes-Benz Vehicle Image API returns original Mercedes-Benz photography for a specific vehicle, addressed by FIN or VIN. It serves both whole-vehicle images (with controllable perspective and day/night lighting) and component renders for the engine, paint, rim, trim, upholstery, and other 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.

Use Cases

Patterns agents use Vehicle Image API for, with concrete tasks.

★ Configurator-aligned vehicle 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.

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

Dealer inventory listings

Dealer websites and aggregators use the API to display official Mercedes-Benz photography on their inventory listings instead of stock or smartphone photos. Each listing references a vehicle's FIN/VIN, so /{finorvin}/vehicle returns the matched whole-vehicle image, while component endpoints surface engine and equipment details on the listing's specification tab.

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 image, two angle shots, and three close-ups per vehicle without commissioning new photography.

For each FIN in the campaign list, GET /{finorvin}/vehicle for the hero, /{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 or binary, and embeds it in the chat reply. Jentic vaults the apiKey so the agent never handles the credential.

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

Key Endpoints

8 endpoints — the mercedes-benz vehicle image api returns original mercedes-benz photography for a specific vehicle, addressed by fin or vin.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Mercedes-Benz developer portal apiKey is stored in Jentic's encrypted vault. Agents receive a scoped reference and the raw key is injected at request time.

Intent-based discovery

Agents search 'show mercedes image by vin' or 'render mercedes paint' and Jentic returns the matching endpoint with its FIN/VIN and component path parameters.

Time to first call

Direct integration: 1-3 days to onboard the apiKey and wire the 8 image endpoints. Through Jentic: under 30 minutes to render the first vehicle.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Car Configurator

Builds the saved configurations whose component images the Vehicle Image API renders.

Pair Configurator with the Image API so each option change updates the on-screen render.

Complementary

Dealer

Routes the customer to a dealer once a vehicle render and configuration are ready.

Use Dealer once Image has produced the previews the customer needs to pick a model.

Alternative

CarsXE

Multi-brand vehicle imagery and VIN data covering many manufacturers, not just Mercedes.

Choose CarsXE when the integration needs cross-brand imagery; use the Mercedes Image API when the customer is configuring or buying a Mercedes.

FAQs

Specific to using Vehicle Image API through Jentic.

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. Through Jentic the apiKey is vaulted and injected at request time so the raw 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?

The spec does not publish numeric limits. 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.

Are the images licensed for commercial use?

The imagery is the original Mercedes-Benz studio photography served via the developer portal. Commercial usage rights are governed by the Mercedes-Benz developer portal terms, not by Jentic.