Mercedes Benz Car Configurator

Name: Car Configurator API
Brand: Car Configurator
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontapiKey24 EndpointsREST

For Agents

Build, validate, and persist Mercedes-Benz vehicle configurations across 24 endpoints covering markets, models, options, and saved configuration IDs.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 lines available in a specific Mercedes-Benz market

Retrieve an initial valid configuration for a chosen model and apply option changes with rule validation

Save a customer-built configuration to a shareable configurationId for later retrieval

GET STARTED

Start building with Car Configurator API

Explore with Jentic

View OpenAPI Document

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 official Mercedes-Benz build experience inside their own UI. The API returns market-scoped masterdata, generates an initial valid configuration for a chosen model, validates each option change against engineering rules, and stores the final result under a configurationId the dealer can retrieve later or hand to the customer. A working flow can be wired up in a few days because rule validation is handled server-side.

Fetch all models for marketId DE, select the E-Class sedan, retrieve its initial configuration, change the paint to obsidian black, and POST the final configuration to /savedConfigurations to obtain a shareable ID.

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 GB, then for each class enumerate models and persist the model code, line, and base price 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. The /savedConfigurations endpoints generate stable IDs that survive across devices, so a configuration started on a kiosk can be opened on the customer's phone. Image components return high-resolution renders so the kiosk can show the exact build.

Save a fully configured C-Class to /savedConfigurations, capture the returned configurationId, then GET /savedConfigurations/{id} 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 /configurations to assemble a valid build, and saves it. 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 /configurations operation schema, execute it with the customer's chosen model and options, and return the saved configurationId.

Key Endpoints

24 endpoints — the mercedes-benz car configurator api exposes the same configuration engine that powers the official mercedes-benz.

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?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Mercedes-Benz developer portal apiKey is stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped reference; the raw key is injected at request time and never enters the agent context.

Intent-based discovery

Agents search by intent (e.g. 'build a mercedes configuration', 'save a vehicle build') and Jentic returns the matching Configurator operation with its input schema, so the agent calls the right endpoint without reading the spec.

Time to first call

Direct integration: 2-4 days to register on the developer portal, wire up the apiKey, and walk the 24-endpoint surface. Through Jentic: under 1 hour from search to first saved configuration.

FAQs

Specific to using Car Configurator API through Jentic.

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

The Configurator API uses an API key passed as a request header. Through Jentic the apiKey is stored in the encrypted vault 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 does not publish a fixed limit in the spec. The tryout host is intended for evaluation traffic, and production access is gated through the Mercedes-Benz developer portal where limits are set per contract.

How do I save a customer's vehicle configuration through Jentic?

Search Jentic for 'save a mercedes configuration', load the /savedConfigurations operation schema, and execute it with the configuration payload. Jentic returns the configurationId from the response so it can be reloaded later via GET /savedConfigurations/{id}.

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 this the same engine that powers mercedes-benz.com?

The API exposes the same configuration logic and reference masterdata used by the official Mercedes-Benz configurator, including market-specific availability rules and option validation.