canonical: https://jentic.com/apis/mercedes-benz.com/mercedes-benz-configurator

# Mercedes Benz Car Configurator

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.

## For AI agents

Build and store Mercedes-Benz vehicle configurations across 24 endpoints covering markets, models, selectable components, images, and onlineCode identifiers.

## Scope

Does not handle ordering, payment, dealer inventory, or vehicle telematics - use for building and storing Mercedes-Benz vehicle configurations only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **Markets** — Region scoping; 23 of the 24 operations take a marketId path parameter, and GET /markets lists the markets themselves
- **References** — Bodies, classes, models, and product groups available per market
- **Configurations** — Initial configurations, selectable components, and alternatives for a list of component changes
- **Saved configurations** — Store a configuration and get an onlineCode that retrieves it later
- **Images** — Component imagery (paint, rim, trim, upholstery) for active configurations

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Vehicle Image** — Returns full-vehicle and component images for a configured Mercedes-Benz vehicle by VIN or FIN.
- **Dealer** — Locates Mercedes-Benz dealers by country and city to convert a saved build into a quote.
- **CarAPI** — Multi-brand vehicle specification and trim data covering many manufacturers, not just Mercedes-Benz.

## FAQ

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