Mercedes Benz Vehicle Image
Browse all Mercedes Benz APIs70
AI ReadinessAI-Aware (A-)70/100
Community OpenAPI document · agent-readyMediaImage ProcessingapiKey8 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Fetch official Mercedes-Benz vehicle and component images by FIN/VIN across 8 endpoints with controllable perspective and lighting.
Use for: Get an exterior image of a Mercedes-Benz E-Class by VIN, Render the rim component for a configured Mercedes vehicle, Show the upholstery for a customer's Mercedes-Benz build, Retrieve a night-time view of an S-Class
Not supported: Does not handle vehicle configuration, telematics, dealer search, or order fulfilment - use for retrieving Mercedes-Benz vehicle and component imagery by FIN/VIN only.
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.
Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmercedes-benz.com%2Fmercedes-benz-image" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmercedes-benz.com%2Fmercedes-benz-image" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Embed brand-consistent Mercedes-Benz imagery inside dealer or comparison sites without licensed photo libraries
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 securely stores 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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
V
Vehicle Image
- AI-Aware (A-)70/100
100
Foundational Compliance69
Developer Experience & Jentic Compatibility42
AI-Readiness & Agent Experience94
Agent Usability100
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
69
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
42
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
68%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Mercedes-Benz Vehicle Image API by hand means passing your developer-portal apiKey and hand-coding each FIN/VIN vehicle and component image call against the tryout host. 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/VIN in the URL path (/{finorvin}/vehicle, /{finorvin}/components/...), so a rule can pin your agent to reading imagery for a given vehicle. You choose the operations it may call, and these endpoints only retrieve vehicle and component images, so nothing beyond that is exposed.
Credential isolation
Your Mercedes-Benz apiKey is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'show a Mercedes image by VIN' or 'render Mercedes paint', and Jentic returns the matching endpoint with its FIN/VIN and component path parameters so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
Can I limit what my agent is allowed to do with the Mercedes-Benz Vehicle Image API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API puts the FIN/VIN in the URL path, so you can pin the agent to reading imagery for a specific vehicle and choose exactly which calls it may make, such as GET /{finorvin}/vehicle or the component renders at /{finorvin}/components/paint, /rim, and /upholstery. Since these endpoints only retrieve vehicle and component images, nothing beyond image retrieval is exposed to the agent.
GET STARTED