Mercedes Benz Car Configurator
Browse all Mercedes Benz APIsCommunity OpenAPI document · agent-readyE CommerceStorefrontapiKey24 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Build and store Mercedes-Benz vehicle configurations across 24 endpoints covering markets, models, selectable components, images, and onlineCode identifiers.
Use for: I want to build a Mercedes-Benz E-Class configuration for the German market, List all available models in the UK Mercedes-Benz configurator, Retrieve the selectable packages and lines for a Mercedes-Benz configuration, Save the customer's chosen configuration so they can return to it later
Not supported: Does not handle ordering, payment, dealer inventory, or vehicle telematics - use for building and storing Mercedes-Benz vehicle configurations only.
The Mercedes-Benz Car Configurator API returns market-specific reference data for bodies, classes, models, and product groups, retrieves the initial configuration for a chosen model, resolves a list of component changes into the resulting configuration with its added, removed, and updated components and prices, and stores a finished configuration under an onlineCode that can be reloaded later. Markets, vehicle classes, available equipment, and prices all vary by region, so 23 of the 24 operations are scoped to a marketId such as de_DE or en_GB; the exception is GET /markets, which enumerates the markets themselves.
Install Jentic One Beta
Connect the Car Configurator to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Car Configurator, 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-configurator" | 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-configurator" | 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 Car Configurator API.
List the bodies, classes, models, and product groups available in a specific Mercedes-Benz market
Retrieve the initial configuration for a chosen model, then resolve a list of component changes into the resulting configuration
Store a finished configuration under an onlineCode that can be shared and reloaded later
Fetch component-level vehicle imagery (paint, rim, trim, upholstery) for any active configuration
Read model and component prices, including net price, taxes, and the configuration total, before quoting a customer
Look up a stored configuration by its onlineCode and reload it into a configurator session
Use Cases
Patterns agents use Car Configurator API for, with concrete tasks.
★ Online dealer build-your-car flow
Dealer websites and marketplace integrations use the Car Configurator API to reproduce the Mercedes-Benz build experience inside their own UI. The API returns market-scoped reference data, returns the initial configuration for a chosen model, resolves a component change list into the added, removed, and updated components that result, and stores the final configuration under an onlineCode the dealer can retrieve later or hand to the customer.
Fetch all models for marketId de_DE, select an E-Class model, GET /markets/{marketId}/models/{modelId}/configurations/initial, request alternatives for a paint change with a componentList such as '+I-950_L-890,-I-953_L-696', then POST the modelId and configurationId to /markets/{marketId}/onlinecode to obtain a shareable onlineCode.
Comparison and quote tools
Aggregator and comparison sites use the Configurator API to pull live, market-correct option lists and equipment data for Mercedes-Benz vehicles, instead of scraping the public site. This keeps comparison tables accurate as packages and bundles change between model years. The market-scoped endpoints (/markets/{marketId}/models, /markets/{marketId}/classes) provide everything needed to populate a quote builder.
List all classes available in marketId en_GB, then for each class enumerate models and persist the modelId, baumuster, and priceInformation into a comparison database.
Showroom kiosk and tablet apps
In-dealership kiosks and salesperson tablet apps embed the Configurator API to let customers configure a vehicle on-site, save the result, and email a link to themselves. POST /markets/{marketId}/onlinecode returns an onlineCode such as 'M6882554' that identifies the stored configuration, so a configuration started on a kiosk can be opened on the customer's phone. The image endpoints return component images in the highest available resolution, so the kiosk can show the exact build.
POST the modelId and configurationId of a fully configured C-Class to /markets/{marketId}/onlinecode, capture the returned onlineCode, then GET /markets/{marketId}/onlinecode/{onlineCode} to confirm the build is retrievable from another device.
Agent-driven vehicle build assistant via Jentic
An AI agent can use Jentic to guide a customer through a Mercedes-Benz build conversationally: agent asks for market and budget, calls /markets/{marketId}/models, narrows by class, calls /markets/{marketId}/models/{modelId}/configurations/initial for a starting build, and stores the result. Jentic handles the apiKey credential and exposes each operation by intent, so the agent never sees the raw key and never has to read the OpenAPI spec.
Search Jentic for 'build a mercedes-benz configuration', load the /markets/{marketId}/models/{modelId}/configurations/initial operation schema, execute it with the customer's chosen market and model, then store the build and return its onlineCode.
Key Endpoints
24 endpoints — the mercedes-benz car configurator api returns market-specific reference data for bodies, classes, models, and product groups, retrieves the initial configuration for a chosen model, resolves a list of component changes into the resulting configuration with its added, removed, and updated components and prices, and stores a finished configuration under an onlinecode that can be reloaded later.
METHOD
PATH
DESCRIPTION
GET
/markets
List supported Mercedes-Benz markets
GET
/markets/{marketId}/models
List models available in a market
GET
/markets/{marketId}/models/{modelId}
Get model masterdata
GET
/markets/{marketId}/classes
List vehicle classes per market
GET
/markets/{marketId}/bodies
List body styles per market
GET
/markets
List supported Mercedes-Benz markets
GET
/markets/{marketId}/models
List models available in a market
GET
/markets/{marketId}/models/{modelId}
Get model masterdata
GET
/markets/{marketId}/classes
List vehicle classes per market
GET
/markets/{marketId}/bodies
List body styles per market
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Mercedes-Benz Car Configurator by hand means passing your developer-portal `x-api-key` on every request and hand-coding each market, model, class, and body call to build a configuration and store it. Through Jentic you install once, import the Car Configurator from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Car Configurator puts the market and model ids in the URL path (/markets/{marketId}/models/{modelId}), so a rule can pin your agent to one market and read its models, classes, and bodies. You choose the operations it may call, and these endpoints read reference data, build configurations, and store them, so nothing beyond that is exposed.
Credential isolation
Your Mercedes-Benz `x-api-key` 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 'build a Mercedes configuration' or 'save a vehicle build', and Jentic returns the matching Configurator operation with its input schema 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 Car Configurator API through Jentic.
What authentication does the Mercedes-Benz Car Configurator API use?
The Configurator API authenticates with a secret API key sent in the `x-api-key` request header. Mercedes-Benz documents it as 'Insert your secret API key as `x-api-key` value in the header', and keys are managed in the Mercedes-Benz developer portal console. Through Jentic the key is stored encrypted by your own self-hosted Jentic One instance and injected at execution time, so the agent never sees the raw credential.
Can I retrieve all models available in a specific market with the Car Configurator API?
Yes. Call GET /markets/{marketId}/models to enumerate every model offered in that market, then GET /markets/{marketId}/models/{modelId} for masterdata on a specific model.
What are the rate limits for the Mercedes-Benz Car Configurator API?
Mercedes-Benz publishes no numeric rate limit for this API. Every operation in the spec defines a 429 response described as 'Quota limit is exceeded', so a quota is enforced, but no figure is documented. API keys and their entitlements are managed in the Mercedes-Benz developer portal console.
How do I save a customer's vehicle configuration through Jentic?
Search Jentic for 'save a mercedes configuration', load the POST /markets/{marketId}/onlinecode operation schema, and execute it with the modelId and configurationId. The response returns an onlineCode, for example 'M6882554', which reloads the build later via GET /markets/{marketId}/onlinecode/{onlineCode}.
Does the Configurator API include vehicle images?
Yes. The Images tag exposes endpoints that return component renders (paint, rim, trim, upholstery) for an active configuration, so a build-your-car UI does not need a separate image service for component previews.
Is there a Mercedes-Benz Car Configurator MCP server?
You do not need an MCP server to give your agent the Car Configurator. Jentic connects it directly from the API Directory: import the Car Configurator, store your `x-api-key` once, and your agent can read market reference data, build configurations, and store them under an onlineCode, with no extra tool definitions loaded into its context.
Can I limit what my agent is allowed to do with the Car Configurator API?
Yes. Because you self-host Jentic One, your own rules decide which Car Configurator operations and credentials the agent may use. Since the market and model ids sit in the URL path, such as /markets/{marketId}/models/{modelId}, you can pin the agent to a single market and let it read only that market's models, classes, and bodies. You choose which operations it may call, so if you allow only the configuration and saved-configuration endpoints, nothing beyond reading reference data, building a configuration, and storing it is exposed.
GET STARTED