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.
3 endpointsJentic 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.
3 endpointsStep 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" | shStep 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" | 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.