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 scoped per market.

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.

Install Jentic One Beta (Self-Hosted)

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

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 under a configurationId for retrieval on another device

Fetch component-level vehicle imagery for an active configuration to preview paint, rim, and trim choices

GET STARTED

Start building with Car Configurator API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Car Configurator, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Car Configurator, keeping it validated and agent-ready. The Mercedes-Benz Car Configurator API exposes the configuration engine that powers mercedes-benz.com, returning market-scoped masterdata for bodies, classes, models, and lines, building initial valid configurations, applying option changes with rule validation, and persisting saved configurations under shareable IDs. Markets, classes, equipment, and pricing all vary by region, so every operation is parameterised by marketId.

Use Cases

Patterns agents use Car Configurator API for, with concrete tasks.

★ Online dealer build-your-car flow

Dealer sites use the Car Configurator API to recreate the official Mercedes-Benz build experience inside their own UI. /markets, /markets/{marketId}/models, /configurations, and /savedConfigurations together cover masterdata, building, and persistence. Server-side rule validation means the dealer site cannot accidentally save an impossible option combination.

GET /markets/DE/models, build a configuration via /configurations, change paint via the option-change endpoint, then POST /savedConfigurations to obtain a shareable ID.

Comparison and quote tooling

Comparison sites use the Configurator API as a live data source for Mercedes-Benz options, instead of scraping. Market-scoped /markets/{marketId}/classes and /markets/{marketId}/models keep the comparison table accurate as packages and bundles change between model years.

List classes for marketId GB, then for each class enumerate models and persist (modelCode, line, baseEquipment) into the comparison database.

Showroom kiosk and tablet apps

Dealership kiosks let customers configure a vehicle on-site, save the result via /savedConfigurations, and continue on their phone using the returned ID. Component image endpoints supply renders so the kiosk shows the exact build, not a generic shot.

Save the customer's full C-Class configuration to /savedConfigurations, capture the configurationId, and email a deep link that resolves to GET /savedConfigurations/{id}.

Agent-driven build assistant via Jentic

An AI assistant guides a customer through a Mercedes build conversationally. It calls /markets/{marketId}/models, narrows by class, builds via /configurations, and saves the result. Jentic vaults the apiKey and exposes each operation by intent, so the agent never sees the raw key or the OpenAPI spec.

Search Jentic for 'build a mercedes-benz configuration', load the /configurations schema, execute it with the chosen model and options, then save and return the configurationId.

Key Endpoints

24 endpoints — jentic publishes the only available openapi specification for car configurator, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/markets

List supported markets

GET

/markets/{marketId}/models

List models in a market

GET

/markets/{marketId}/classes

List classes in a market

GET

/markets/{marketId}/bodies

List body styles in a market

GET

/markets/{marketId}/models/{modelId}

Get model masterdata

GET

/markets

List supported markets

GET

/markets/{marketId}/models

List models in a market

GET

/markets/{marketId}/classes

List classes in a market

GET

/markets/{marketId}/bodies

List body styles in a market

GET

/markets/{marketId}/models/{modelId}

Get model masterdata

Why though Jentic?

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

Credential isolation

The Mercedes-Benz developer-portal apiKey is stored in Jentic's encrypted vault. Agents receive a scoped reference; the raw key is injected at request time.

Intent-based discovery

Agents search by intent (e.g. 'build a mercedes configuration') 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 for portal sign-up, apiKey wiring, and walking the 24-endpoint surface. Through Jentic: under 1 hour from search to first saved configuration.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Vehicle Image

Returns full-vehicle imagery for a configured Mercedes-Benz once the configurator has produced a model code.

Pair with Vehicle Image when the customer needs hero photography of the configured car.

Complementary

Dealer

Routes a saved configuration to the closest authorised Mercedes-Benz dealer for finalisation.

Use Dealer once a build is saved so the agent can hand the customer to a local retailer.

Alternative

CarAPI

Multi-brand vehicle specification and trim data, broader than Mercedes alone.

Choose CarAPI for cross-brand model data; the Mercedes Configurator is the right tool when the customer is buying a Mercedes.

FAQs

Specific to using Car Configurator API through Jentic.

Why is there no official OpenAPI spec for Car Configurator?

Mercedes-Benz does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Car Configurator via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

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

The Configurator API uses an apiKey from the Mercedes-Benz developer portal in the request header. Jentic vaults the key and injects it at execution time so the agent never sees it directly.

Can I save a customer's configuration with the Car Configurator API?

Yes. POST to /savedConfigurations with the build payload and the response includes the configurationId, which can be reloaded later via GET /savedConfigurations/{id}.

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

The spec does not publish numeric limits. Production limits are set per developer portal contract; the tryout host is intended for evaluation traffic only.

How do I build a Mercedes-Benz vehicle programmatically through Jentic?

Search Jentic for 'build a mercedes-benz configuration', load the /configurations operation schema, and execute it with the chosen marketId, modelId, and options. Jentic returns the validated configuration ready to save.

Does the Configurator API include component imagery?

Yes. The Images tag returns component renders (paint, rim, trim, upholstery) for an active configuration so a build-your-car UI does not need a separate image library for previews.