Vehicle Image

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

★ Only Publicly Available OpenAPI DocumentMediaImage Processingnone8 EndpointsREST

For Agents

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

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 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

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.

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.

Use Cases

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

★ 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.

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.

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.

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.

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

8 endpoints — jentic publishes the only available openapi specification for vehicle image, keeping it validated and agent-ready.

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

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

Why though Jentic?

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

Credential isolation

Mercedes-Benz Developer API keys are stored in the Jentic vault. Agents call the Vehicle Image API with a scoped Jentic token; the Mercedes API key never enters the agent context.

Intent-based discovery

Agents search Jentic with intents like 'fetch Mercedes vehicle image by VIN' and receive the matching GET /{finorvin}/vehicle or component operation with its parameter schema.

Time to first call

Direct integration with the Mercedes-Benz Developer portal: 1-2 days for app registration, key management, and image caching. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Mercedes-Benz Configurator API

Build vehicle configurations whose FIN or VIN is then passed to the Vehicle Image API

Use when the agent needs to construct or modify a Mercedes-Benz build before fetching matching imagery.

Complementary

Mercedes-Benz Dealer API

Look up dealer inventory and pair listings with Vehicle Image renderings

Use when the agent is building a dealer-facing inventory page that combines stock data with vehicle imagery.

Alternative

Mercedes-Benz Diagnostics API

Different Mercedes-Benz API focused on diagnostic data rather than imagery

Use when the task is reading vehicle diagnostic information instead of rendering vehicle photos.

FAQs

Specific to using Vehicle Image API through Jentic.

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 at https://app.jentic.com/sign-up.

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.