# Mercedes-Benz Mercedes me > Mercedes-Benz operates a public, self-service API platform at developer.mercedes-benz.com covering > connected-vehicle data (status, lock, fuel, electric, pay-as-you-drive), vehicle commerce content > (car configurator, vehicle images, dealer search), remote diagnostics, and a Kafka-streamed Fleet API > sold through Mercedes-Benz Connectivity Services GmbH. Connected-vehicle APIs run on an OAuth 2.0 > vehicle-owner consent flow with fine-grained per-signal scopes; the content and diagnostics APIs run > on a developer-portal API key. Generated by API Evangelist on 2026-08-26 from this provider profile. Mercedes-Benz does not publish an llms.txt of its own — probed https://developer.mercedes-benz.com/llms.txt (HTTP 200, but the body is the portal's client-rendered SPA shell, not a document) and https://connectivity.mercedes-benz.com/llms.txt (HTTP 404). ## What an agent should know first - Base host for every public API: https://api.mercedes-benz.com - Sandbox is a SEPARATE BASE PATH, not a flag: /configurator_tryout/v1, /dealer_tryout/v1, /image_tryout/v1/vehicles, /remotediagnostic_tryout/v1. Production drops the `_tryout` suffix. - Two auth models. Content and diagnostics APIs take a developer-portal API key as a QUERY PARAMETER (the contract does not name the parameter — that value is only on the portal). Connected-vehicle APIs take an OAuth 2.0 access token from https://id.mercedes-benz.com/as/token.oauth2 with vehicle-owner consent. - There is NO idempotency key, NO pagination, NO request id, NO Retry-After header and NO RFC 9457 problem+json anywhere in this estate. A 429 tells you to back off in English prose in the body. - Only four of the products have a published machine-readable contract. The connected-vehicle family and the Fleet API publish none. ## Published API contracts (Swagger 2.0, provider-published) - [Car Configurator API](openapi/_original/mercedes-me-configurator-api-openapi.yml): markets, classes, bodies, models, product groups, configurations, selectables, alternatives, saved configurations (online codes), and configuration imagery. 24 paths. - [Dealer API](openapi/_original/mercedes-me-dealer-api-openapi.yml): dealer/garage/retailer search by attribute, dealer detail, country reference. 3 paths. - [Vehicle Images API](openapi/_original/mercedes-me-vehicle-images-api-openapi.yml): vehicle and component imagery keyed by FIN/VIN. 8 paths. - [Remote Diagnostic Support API](openapi/_original/mercedes-me-remote-diagnostic-support-api-openapi.yml): asynchronous ECU, DTC, DTC-snapshot and resource readouts keyed by vehicleId. 4 paths. Refined one-per-tag OpenAPI documents live in `openapi/`; Postman and OpenCollection exports live in `collections/`. ## Products WITHOUT a published contract - Vehicle Status API — https://developer.mercedes-benz.com/products/vehicle_status - Vehicle Lock Status API — https://developer.mercedes-benz.com/products/vehicle_lock_status - Fuel Status API — https://developer.mercedes-benz.com/products/fuel_status - Electric Vehicle Status API (v3) — https://developer.mercedes-benz.com/products/electric_vehicle_status_3 - Pay As You Drive 2.0 API — https://developer.mercedes-benz.com/products/pay_as_you_drive_insurance_2 - Mercedes-Benz Fleet API — https://developer.mercedes-benz.com/products/mercedes-benz_fleet_api These are the products with the vehicle-command surface. An agent cannot construct a call to any of them from a contract; it must be driven from the portal by a human first. ## Authentication and authorization - [OAuth scopes](scopes/mercedes-me-scopes.yml) — 38 Mercedes-Benz product scopes read verbatim from the identity provider's own discovery document, including nine EU Data Act (`euda`) vehicle-data categories. - [Authentication profile](authentication/mercedes-me-authentication.yml) - OpenID Connect discovery (saved verbatim): [well-known/mercedes-me-id-openid-configuration.json](well-known/mercedes-me-id-openid-configuration.json) - Authorization endpoint: https://id.mercedes-benz.com/as/authorization.oauth2 - Token endpoint: https://id.mercedes-benz.com/as/token.oauth2 - PKCE S256, pushed authorization requests, mutual-TLS client auth, private_key_jwt and dynamic client registration are all advertised. So are the implicit and password grants — do not use them. ## Runtime semantics - [Conventions, including reversibility](conventions/mercedes-me-conventions.yml) - [Error catalogue](errors/mercedes-me-problem-types.yml) - [Rate limits](rate-limits/mercedes-me-rate-limits.yml) - [Lifecycle and versioning](lifecycle/mercedes-me-lifecycle.yml) — note: each major version is a separate product with a separate scope, so an upgrade requires re-subscription AND re-consent. - [Sandbox](sandbox/mercedes-me-sandbox.yml) - [Data model](data-model/mercedes-me-data-model.yml) - [Standards conformance](conformance/mercedes-me-conformance.yml) - [Plans and pricing](plans/mercedes-me-plans-pricing.yml) - [Agentic access classification](agentic-access/mercedes-me-agentic-access.yml) ## Client libraries - [Package inventory](packages/mercedes-me-packages.yml) — Mercedes-Benz publishes NO API client to any package registry. All twelve MBSDK repositories are archived with no push since 2021. The one maintained first-party artifact is `kafka-integration-samples` (v1.0.0, 2024-07-03), which is sample code for Fleet API Kafka consumers, not a client library. ## Agent surfaces - [MCP tool candidate](mcp/mercedes-me-mcp.yml) — Mercedes-Benz ships NO MCP server. The tool list there is derived from the OpenAPI and is marked `status: candidate`, `deployment.mode: none`. - No A2A agent card is served from any Mercedes-Benz host. - [Agent skills](skills/_index.yml) ## Human entry points - Developer portal: https://developer.mercedes-benz.com/ - API products catalogue: https://developer.mercedes-benz.com/products - Support: https://developer.mercedes-benz.com/support - SDKs: https://developer.mercedes-benz.com/sdks - Postman workspace: https://www.postman.com/mbdevelopers/mercedes-benz/overview - GitHub: https://github.com/mercedes-benz - Mercedes-Benz Connectivity Services: https://connectivity.mercedes-benz.com/ ## Caveat for crawlers developer.mercedes-benz.com is a client-rendered single-page application. It answers HTTP 200 with an identical ~4.3 KB HTML shell for every path, including paths that do not exist — verified by diffing /products/vehicle_status against a fabricated path, which differ only in an og:url meta tag. Do not treat a 200 from that host as evidence a page exists. Its robots.txt disallows /console/, /api/, /config/ and /ciam/.