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

# Mercedes Benz Car Configurator

The Mercedes-Benz Car Configurator API exposes the same configuration logic that powers the Mercedes-Benz online configurator - vehicle masterdata, market and model browsing, initial and updated configurations, and saved-configuration retrieval - across 24 endpoints. Configurations are scoped by market and class so a client can fetch the right body styles, models, and option packages for a given country, then walk a customer through option selection or restore a previously saved build. The API is well suited to dealer tools, third-party automotive aggregators, and brand-experience apps that need authoritative Mercedes vehicle data.

## For AI agents

Browse Mercedes-Benz vehicle masterdata by market, class, and model, build and modify configurations, and retrieve saved builds. Returns the structured options and pricing logic powering the public configurator.

## Scope

Does not handle vehicle telematics, dealer inventory, or financing - use for Mercedes-Benz vehicle masterdata, configuration, and saved-build flows only.

## Capabilities

- List supported markets and retrieve the model lineup available in each market
- Browse Mercedes-Benz body styles, classes, and models with full structured masterdata
- Create an initial configuration for a model and retrieve its default option set
- Apply changes to an existing configuration and receive the validated updated state
- Save a configuration so it can be restored or shared via a stable identifier
- Retrieve images for a configured vehicle to render in a downstream UI

## Use cases

### Dealer Configurator Tool

Mercedes-Benz dealers and dealer-network apps embed the configurator API to walk a customer through option selection on a tablet during a showroom visit. The market, class, and model endpoints give the app the right lineup for the customer's country, and configuration endpoints validate option compatibility so the dealer never quotes an invalid build.

Example prompt: List markets, scope to market=DE, list models, create an initial configuration for the chosen model, apply the customer's selected options, and return the updated configuration with validated pricing logic.

### Automotive Aggregator Listings

Automotive aggregators and comparison sites use the Mercedes Car Configurator API to keep model and option data in sync with the official source. The API's market-scoped browse endpoints provide structured masterdata that aggregators can normalise across brands instead of scraping configurator pages.

Example prompt: For each supported market, fetch `/markets/{marketId}/models`, normalise the response into the aggregator's schema, and update the listings table with new or changed models.

### Saved Build Sharing

Brand-experience apps let prospective buyers configure a vehicle on mobile, save the build, and resume on desktop or share with a salesperson. The configurator's save endpoints generate a stable configuration identifier that can be restored on any client, which preserves the exact option set across devices.

Example prompt: Save the customer's current configuration to obtain a configurationId, send the ID by email or SMS, and on follow-up call `/markets/{marketId}/models/{modelId}/configurations/{configurationId}` to restore the saved build.

### AI Agent Vehicle Quote

An AI assistant on a Mercedes-Benz brand site can parse a natural-language request - 'show me a C-Class with the AMG line and panoramic roof in Germany' - into a structured configuration. Through Jentic, the agent loads the masterdata and configuration endpoints as discoverable tools and walks the build steps without writing custom HTTP code.

Example prompt: Search Jentic for 'configure mercedes vehicle', list models in market=DE, create an initial configuration for the matched model, apply 'AMG line' and 'panoramic roof' options, and return the resulting configuration.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/markets` | List supported markets |
| GET | `/markets/{marketId}/models` | List models available in a market |
| GET | `/markets/{marketId}/classes` | List vehicle classes in a market |
| GET | `/markets/{marketId}/bodies` | List body styles in a market |
| GET | `/markets/{marketId}/models/{modelId}/configurations/initial` | Get the initial default configuration for a model |
| GET | `/markets/{marketId}/models/{modelId}/configurations/{configurationId}` | Retrieve a specific configuration |

## Key resources

- **Markets** — Supported markets and the model lineup available in each.
- **Bodies** — Vehicle body styles offered per market.
- **Classes** — Mercedes-Benz vehicle classes (C-Class, E-Class, S-Class, etc.) per market.
- **Models** — Specific models within a class with their masterdata.
- **Configurations** — Initial and modified configurations including option packages and validated state.
- **Saved configurations** — Restore and share builds by stable identifier.
- **Images** — Rendered imagery for a configured vehicle.

## Why Jentic

- **Setup:** Wiring the Mercedes-Benz Car Configurator by hand means walking the market, model, class, and body hierarchy and hand-coding each configuration call against the tryout host. Through Jentic you install once, import the Car Configurator from the API Directory, store any production credential once, and your agent calls it.
- **Permission scoping:** The Car Configurator puts the market, model, and configuration ids in the URL path (`/markets/{marketId}/models/{modelId}/configurations/{configurationId}`), so a rule can pin your agent to one market and read its models and configurations. You choose the operations it may call, and these endpoints read masterdata and saved builds, so nothing beyond configuration flows is exposed.
- **Credential handling:** Any production Mercedes-Benz credential is stored once, encrypted, by your own Jentic One instance and injected at execution time; the sandbox tryout host needs none. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'configure a Mercedes vehicle' or 'list Mercedes models in a market', and Jentic returns the matching market, model, or configuration endpoint with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Smartcar** — Connected-car telemetry across many brands rather than vehicle configuration
- **Autodata** — Multi-brand technical vehicle data rather than configurator builds
- **Mercedes-Benz Image API** — Rendered imagery for Mercedes vehicles paired with configurator output

## FAQ

### What authentication does the Mercedes-Benz Car Configurator API use?

The OpenAPI spec declares no security scheme on this tryout base URL - the public sandbox is open. Production Mercedes-Benz developer endpoints require an OAuth client credential issued by the Mercedes-Benz developer portal; through Jentic any such credential is held in the encrypted vault and injected at request time.

### Can I save a vehicle configuration and restore it later with the Mercedes-Benz Car Configurator API?

Yes. The Saved configurations resource issues a stable configurationId, and `/markets/{marketId}/models/{modelId}/configurations/{configurationId}` restores the exact build, which supports cross-device resume and configuration sharing flows.

### What are the rate limits for the Mercedes-Benz Car Configurator API?

The OpenAPI spec does not declare numeric rate limits. The hosted tryout endpoint is intended for development; production usage requires the Mercedes-Benz developer portal where quotas depend on the contracted plan.

### How do I build a Mercedes-Benz configuration through Jentic?

Run `pip install jentic`, search for `configure mercedes vehicle`, load `/markets/{marketId}/models/{modelId}/configurations/initial`, and execute with the chosen market and model IDs. Jentic returns the default configuration, and you can chain follow-up calls to apply options.

### Does the Mercedes-Benz Car Configurator API expose pricing?

The configurator returns the structured option and package data needed to drive a build flow, but list pricing is governed per market and may not appear in this sandbox spec. Pricing visibility depends on which market endpoint and which contract you operate under in the developer portal.

### Can I limit what my agent is allowed to do with the Mercedes-Benz Car Configurator API?

Yes. Because you run Jentic One yourself, your own rules decide which Car Configurator operations and credentials the agent may use. The market, model, and configuration IDs sit in the URL path (`/markets/{marketId}/models/{modelId}/configurations/{configurationId}`), so you can pin the agent to a single market and let it read only that market's models and configurations. You choose the operations it may call, and since these endpoints only read masterdata and saved builds, nothing beyond configuration flows is exposed.