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.

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" | 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-dealer" | 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 Dealer API.

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

GET STARTED

Start building with Dealer API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Dealer API for, with concrete tasks.

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

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.

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.

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.

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 — the mercedes-benz dealer api provides a structured directory of authorised mercedes-benz dealerships and the countries they operate in.

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

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.

Intent-based discovery

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.

FAQs

Specific to using Dealer API through Jentic.

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.

Mercedes Benz Dealer

Browse all Mercedes Benz APIs

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Community OpenAPI document · agent-readyMaps 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 Germany, List the countries Mercedes-Benz operates dealers in, Get the address for Mercedes-Benz dealer ID 12345, Search for the nearest authorised Mercedes dealer to the user

Not supported: Does not handle dealer inventory, appointment scheduling, vehicle pricing, or service bookings - use for looking up authorised Mercedes-Benz dealer locations only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

71%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Dealer to your agent

Capabilities

Start building with Dealer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mercedes Benz Dealer

Jentic AI Readiness Score

Dealer

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness