Car Configurator

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

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontnone24 EndpointsREST

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

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

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.

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.

Use Cases

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

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

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.

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.

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.

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

24 endpoints — 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.

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

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

Why though Jentic?

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

Credential isolation

The sandbox tryout endpoint requires no credentials. For production Mercedes-Benz developer-portal credentials, Jentic stores the OAuth client encrypted in the MAXsystem vault and injects tokens at request time so they never appear in agent context.

Intent-based discovery

Agents search Jentic for intents like 'configure mercedes vehicle' or 'list mercedes models in a market' and receive the matching market/model/configuration endpoint with input schema, ready to execute.

Time to first call

Direct integration: 1-2 days to wire up the market/class/model browse, configuration apply, and saved-build flows. Through Jentic: under 30 minutes — the agent loads only the operations needed for the current build.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Smartcar

Connected-car telemetry across many brands rather than vehicle configuration

Use Smartcar to read odometer, location, or lock state on an already-owned vehicle; use Mercedes Car Configurator to spec a new vehicle for purchase.

Alternative

Autodata

Multi-brand technical vehicle data rather than configurator builds

Choose Autodata for repair and technical specifications across brands; choose Mercedes Car Configurator when the workflow is configuring a new Mercedes vehicle for sale.

Complementary

Mercedes-Benz Image API

Rendered imagery for Mercedes vehicles paired with configurator output

Use the Image API to fetch a high-quality render of a configured vehicle once the Car Configurator API has produced the configuration ID.

FAQs

Specific to using Car Configurator API through Jentic.

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.