Mercedes Benz Dealer
Browse all Mercedes Benz APIsAgent-ready OpenAPI document · curated by JenticMaps GeolocationPlaces SearchapiKey3 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Search the official Mercedes-Benz dealer directory by country and retrieve full dealer profiles by ID across 3 endpoints.
Use for: Find all Mercedes-Benz dealers in Italy, List the countries where Mercedes-Benz has authorised dealers, Get the address for a specific Mercedes-Benz dealer ID, Search for the nearest authorised Mercedes dealership
Not supported: Does not handle dealer inventory, appointment scheduling, vehicle pricing, or service bookings - use for looking up authorised Mercedes-Benz dealer locations only.
Jentic publishes the only available OpenAPI specification for Dealer, keeping it validated and agent-ready. The Mercedes-Benz Dealer API exposes the official authorised dealer directory: a country reference list and a dealer search returning addresses and identifiers for each dealership. The data matches the public dealer locator on mercedes-benz.com, suitable for embedding a 'find a Mercedes dealer' experience inside a third-party app or agent flow.
Install Jentic One Beta
Connect the Dealer to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dealer, 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.
1
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-dealer-api" | sh2
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-dealer-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Dealer API.
List the countries where Mercedes-Benz operates an authorised dealer network
Search the Mercedes-Benz dealer directory filtered by country
Retrieve a dealer's full profile, including address and identifiers, by dealerId
Power a 'find your nearest Mercedes-Benz dealer' UI inside a third-party site or app
Verify whether a given dealer ID is recognised in the official Mercedes directory
Use Cases
Patterns agents use Dealer API for, with concrete tasks.
★ Embed a Mercedes-Benz dealer locator
Marketplace and comparison sites embed the official Mercedes-Benz dealer locator instead of scraping mercedes-benz.com. /countries scopes the query, /dealers returns the matching dealerships, and /dealers/{dealerId} fills in the full record. The directory stays in sync with the official locator as dealers open or close.
GET /countries, then GET /dealers?countryCode=DE for German dealers, then GET /dealers/{dealerId} for the first result to obtain the full address.
Hand-off after a saved configuration
After a customer saves a build via the Mercedes Car Configurator, the Dealer API converts a country code into a list of nearby dealers. This closes the loop between online configuration and in-person purchase without leaving the integrating app.
GET /dealers with the customer's countryCode, then surface the top three dealers ranked by distance from the user's coordinates.
Aftersales and breakdown routing
Service apps route an owner to the nearest authorised Mercedes-Benz workshop. /dealers filtered by country returns a candidate list, and /dealers/{dealerId} confirms the address. The directory's authoritativeness reduces the risk of routing a customer to a non-authorised garage.
Filter /dealers by countryCode, sort by distance from the user's location, and return the closest dealer's record from /dealers/{dealerId}.
Agent-driven dealer search via Jentic
An AI assistant uses Jentic to look up an authorised Mercedes-Benz dealer in the user's country. Jentic securely stores the apiKey and exposes /dealers by intent, so the agent calls the operation with a country code and returns a normalised dealer list in chat.
Search Jentic for 'find a mercedes-benz dealer', load the /dealers schema, execute it with countryCode=GB, and return the top dealer's name and address.
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for dealer, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/countries
List supported countries
GET
/dealers
Search authorised Mercedes-Benz dealers
GET
/dealers/{dealerId}
Retrieve a single dealer's full profile
GET
/countries
List supported countries
GET
/dealers
Search authorised Mercedes-Benz dealers
GET
/dealers/{dealerId}
Retrieve a single dealer's full profile
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Mercedes-Benz Dealer API by hand means getting a developer-portal apiKey, attaching it to each call against the dealer_tryout host, and paging through countries and dealers yourself. Through Jentic you install once, import the Dealer API from the API Directory, store the apiKey once, and your agent calls it.
Permission scoping
The Dealer API puts the dealer id in the URL path (/dealers/{dealerId}), so a rule can pin your agent to one dealer record. Every operation here is a read-only GET for looking up countries and authorised dealers, so a rule can grant those lookups without exposing any write.
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 'find a Mercedes dealer' or 'list Mercedes countries', and Jentic returns the matching Dealer API operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Dealer API through Jentic.
Why is there no official OpenAPI spec for Dealer?
Mercedes-Benz does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Dealer 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 Dealer API use?
The Dealer API uses an apiKey from the Mercedes-Benz developer portal in the request header. Jentic stores the apiKey in its encrypted vault and injects it at execution time.
Can I get a full address for a specific Mercedes-Benz dealer?
Yes. GET /dealers/{dealerId} with the dealer's identifier returns the dealership's address and contact identifiers.
What are the rate limits for the Mercedes-Benz Dealer API?
The spec does not publish numeric limits. Production traffic is throttled per developer portal contract; the public tryout host is intended for evaluation only.
How do I find dealers in a specific country through Jentic?
Search Jentic for 'find a mercedes-benz dealer', load the /dealers schema, and execute it with the relevant countryCode parameter. The agent receives the dealer list it can rank or display.
Does the Dealer API include opening hours or service availability?
No. The spec exposes /countries, /dealers, and /dealers/{dealerId} only. Opening hours and live service availability are not in the directory - pair with a dealer's own scheduling system for that.
Can I limit what my agent is allowed to do with the Mercedes-Benz Dealer API?
Yes. Because you self-host Jentic One, your own rules decide which of this API's operations your agent may call, and every operation here is a read-only GET for looking up countries and authorised dealers, so you can grant those lookups without exposing any write. Since the dealer id sits in the URL path at GET /dealers/{dealerId}, a rule can pin the agent to a single dealer record or restrict it to country and search calls such as GET /countries and GET /dealers. You configure these scopes, and the stored apiKey is injected only when a permitted operation runs.
GET STARTED