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.
8 endpointsJentic 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.
8 endpointsJentic 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.
8 endpointsStep 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" | shStep 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" | 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.