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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmercedes-benz.com%2Fmercedes-benz-configurator-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmercedes-benz.com%2Fmercedes-benz-configurator-api" | 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 One

View OpenAPI Document

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 securely stores 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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Mercedes-Benz Car Configurator by hand means registering on the developer portal, threading its apiKey into every request against the configurator_tryout host, and coding the market and model path lookups yourself. Through Jentic you install once, import the Car Configurator from the API Directory, store the apiKey once, and your agent calls it.

Permission scoping

The Car Configurator puts the market in the URL path (/markets/{marketId}/models/{modelId}), so a rule can pin your agent to one market and the models under it. You choose the operations it may call, and every endpoint here is a read-only GET for building and validating configurations, so a rule can grant model and body lookups without exposing anything that writes.

Credential isolation

Your Mercedes-Benz apiKey is stored once, encrypted, by your own Jentic One instance and injected at request time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'build a Mercedes configuration' or 'list models for a market', and Jentic returns the matching Car Configurator operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 with Jentic One, the self-hosted execution layer.

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 securely stores 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.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which Configurator operations and credentials your agent may use. Every endpoint here is a read-only GET for building and validating configurations, so you can grant lookups like GET /markets/{marketId}/models and GET /markets/{marketId}/models/{modelId} without exposing anything that writes. Since the market sits in the URL path, a rule can also pin the agent to a single marketId and the models under it.

Mercedes Benz Car Configurator

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

Browse all Mercedes Benz APIs

Agent-ready OpenAPI document · curated by JenticE CommerceStorefrontapiKey24 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Build, validate, and persist Mercedes-Benz vehicle configurations across 24 endpoints scoped per market.

Use for: I want to build a Mercedes-Benz GLC configuration for the Spanish market, List every model offered in the Italian Mercedes configurator, Save a customer's chosen Mercedes build to a shareable ID, Retrieve the initial configuration for a specific Mercedes class

Not supported: Does not handle ordering, payment, dealer inventory, or vehicle telematics - use for building, validating, and saving Mercedes-Benz vehicle configurations only.

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.

Jentic One on Github View OpenAPI Document