canonical: https://jentic.com/apis/mercedes-benz.com/mercedes-benz-dealer # Mercedes Benz Dealer The Mercedes-Benz Dealer API provides a structured directory of authorised Mercedes-Benz dealerships and the countries they operate in. It returns dealer locations with addresses, contact details, and identifiers, plus a country reference list to scope queries. The dataset is the same dealer information surfaced on mercedes-benz.com's dealer locator, suitable for embedding a 'find a Mercedes dealer' experience inside a third-party app. ## For AI agents Search the official Mercedes-Benz dealer directory by country and retrieve full dealer profiles by ID across 3 endpoints. ## Scope Does not handle dealer inventory, appointment scheduling, vehicle pricing, or service bookings - use for looking up authorised Mercedes-Benz dealer locations only. ## Capabilities - List the countries where Mercedes-Benz operates an authorised dealer network - Search the dealer directory filtered by country and other parameters - 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 Mercedes dealer ID is recognised in the official directory ## Use cases ### Embed a Mercedes-Benz dealer locator Marketplace, comparison, and booking sites use the Dealer API to embed an authorised Mercedes-Benz dealer locator without scraping mercedes-benz.com. The /countries endpoint scopes the query to a region, /dealers returns the matching dealerships, and `/dealers/{dealerId}` fills in the full record. Because the data is the same as the official locator, listings stay current as dealers open or close. Example prompt: GET /countries to list available regions, then GET /dealers?countryCode=DE to retrieve all German dealers, and finally GET `/dealers/{dealerId}` for the first result to obtain the full address. ### Hand-off after a saved car configuration After a customer saves a build via the Mercedes Car Configurator, the Dealer API converts a country code and saved configuration into a list of nearby dealers who can finalise the order. This closes the loop between online build and in-person purchase without leaving the integrating app. Example prompt: Given the customer's countryCode, call /dealers to fetch the dealer list, then surface the top three nearest dealers to the user with their addresses. ### Aftersales and service routing Service and breakdown apps use the Dealer API to route a vehicle owner to the nearest authorised Mercedes-Benz workshop. /dealers returns dealerships filtered by country, and `/dealers/{dealerId}` returns the address used to navigate the customer in. The directory's authoritativeness reduces the risk of routing a customer to a non-authorised garage. Example prompt: Filter /dealers by countryCode for the user's location, sort the response by distance from the user's coordinates, and return the closest dealer's full 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 without managing the developer-portal apiKey directly. Jentic exposes /dealers by intent, so the agent calls the operation with a country code and receives a normalised dealer list it can present in chat. Example prompt: 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 | 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 | ## Key resources - **Countries** — Reference list of countries with Mercedes-Benz dealer coverage - **Dealers** — Authorised Mercedes-Benz dealerships with addresses and identifiers ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 71 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/mercedes-benz.com/mercedes-benz-dealer/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Mercedes-Benz Dealer lookup by hand means passing your developer-portal apiKey and hand-coding the country and dealer calls against the tryout host. 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 reading dealer locations and countries. You choose the operations it may call, and these endpoints are read-only dealer lookup, so nothing beyond that is exposed. - **Credential handling:** Your Mercedes-Benz apiKey is stored once, encrypted, by your own Jentic One instance and injected when /dealers or /countries is called. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find a Mercedes dealer' or 'list Mercedes countries', and Jentic returns the matching operation with its parameters so the agent calls /dealers without browsing the reference docs. ## Related APIs - **Car Configurator** — Builds and saves Mercedes-Benz vehicle configurations that the Dealer API can route to a local dealership. - **Vehicle Image** — Provides high-resolution Mercedes-Benz vehicle imagery for dealer listing pages. - **Auto Dealer Data** — Multi-brand US dealer inventory and dealership data; broader than Mercedes alone. ## FAQ ### What authentication does the Mercedes-Benz Dealer API use? The Dealer API uses an apiKey from the Mercedes-Benz developer portal, sent as a request header. Through Jentic the key is stored encrypted and injected at execution time so the raw value never enters the agent context. ### Can I get a full address for a specific Mercedes-Benz dealer? Yes. Call GET `/dealers/{dealerId}` with the dealer's identifier and the response includes the dealership's address and contact identifiers. ### What are the rate limits for the Mercedes-Benz Dealer API? The spec does not publish hard limits. Production traffic is rate-limited per developer portal contract; the public tryout host is intended for evaluation volumes only. ### How do I find dealers in a specific country through Jentic? Search Jentic for 'find a mercedes-benz dealer', load the /dealers operation schema, and execute it with the relevant countryCode parameter. Jentic returns the dealer list the agent can rank by distance. ### Does the Dealer API include opening hours or service availability? The spec exposes /countries, /dealers, and `/dealers/{dealerId}` only. It does not include opening hours or live service availability - for in-person bookings combine this API with a dealer's own scheduling system. ### Is this the same data as the mercedes-benz.com dealer locator? Yes. The Dealer API surfaces the official authorised dealer directory used by the public locator, so any dealer returned is recognised by Mercedes-Benz. ### Can I limit what my agent is allowed to do with the Mercedes-Benz Dealer API? Yes. Because you run Jentic One yourself, your own rules decide which of the Dealer API's operations your agent may call, so you can allow only GET /countries, GET /dealers, and GET `/dealers/{dealerId}.` These are all read-only lookups that return dealer locations and the supported-country list, so an agent scoped to them cannot write, book, or change anything. You also control where the Mercedes-Benz apiKey is used, keeping it out of the agent's prompt and context while it queries the directory.