Mercedes-Benz operates one of the few genuinely public OEM API platforms. Its /developers portal at developer.mercedes-benz.com sells connected-vehicle data as individually-subscribable products — Vehicle Status, Vehicle Lock Status, Fuel Status, Electric Vehicle Status and Pay As You Drive — each gated by its own OAuth 2.0 scope and each requiring the vehicle owner's explicit per-signal consent, granted through the Mercedes-Benz identity provider at id.mercedes-benz.com. Alongside them sit four content and service APIs with published Swagger 2.0 contracts: the Car Configurator, the Dealer API, the Vehicle Images API and Remote Diagnostic Support. Mercedes-Benz Connectivity Services GmbH sells the Fleet API separately, pairing a REST management surface with a managed Apache Kafka push channel that streams nineteen activatable telemetry packages plus five remote-command packages, including remote door lock and unlock. Every API is versioned by URI path and shipped with a *_tryout sandbox base path on the same host.
Mercedes-Benz Mercedes me publishes 17 API contracts indexed on the APIs.io network, including Components API, Configurations API, Dealer search API, and 14 more. Tagged areas include Automotive, Connected Vehicles, Daimler, Fleet Management, and Mercedes me.
The Mercedes-Benz Mercedes me catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 2 Spectral governance rulesets.
Mercedes-Benz Mercedes me’s developer surface includes developer portal, documentation, GitHub presence, authentication, sandbox, and 37 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/mercedes-me/"><img src="https://apis.io/badge/mercedes-me/card.svg" alt="Mercedes-Benz Mercedes me on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Documented Reversibility+6 pts — a reversal operation in the contract, graded up when a window is documented too
Pagination+5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs
5 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Access Clarityscores 31.6 — up to +13.7 composite points
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
The Vehicle Status API delivers real-time vehicle state — doors, windows, deck lid, sunroof, tire pressure, and overall lock state — for a customer-consented Mercedes-Benz vehic...
The Vehicle Lock Status API returns the current door-lock, deck-lid, and position-lock state of a Mercedes-Benz vehicle by VIN. Designed for parking, insurance, and security-mon...
The Fuel Status API exposes a Mercedes-Benz combustion vehicle's current tank level, remaining fuel range in km, and last-update timestamp by VIN. Targeted at fueling, fleet, an...
The Electric Vehicle Status API (currently at v3) provides charge state, state-of-charge percent, remaining electric range in km, charging-active flag, and time-to-full estimate...
The Pay As You Drive 2.0 API supplies precise odometer readings and geographical position for a consented Mercedes-Benz vehicle, designed for usage-based insurance, mileage-base...
The Mercedes-Benz Fleet API integrates vehicle data into fleet management systems without retrofit hardware. It splits into a REST Management API (add vehicles, activate/deactiv...
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
aid: mercedes-me
url: https://raw.githubusercontent.com/api-evangelist/mercedes-me/refs/heads/main/apis.yml
deliveryModel:
model: saas
license_evidence:
not_product:
- mercedes-benz/foss
- mercedes-benz/mercedes-benz-foss-manifesto
open_source: unknown
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: low
source:
- openapi
- pricing
- repository-not-product
generated: '2026-09-25'
method: derived
specificationVersion: '0.23'
apis:
- aid: mercedes-me:mercedes-me-vehicle-status-api
name: Mercedes-Benz Vehicle Status API
tags:
- Automotive
- Connected Vehicles
- Mercedes me
- Mercedes-Benz
- Telematics
- Vehicle Status
tags_raw:
- Automotive
- Connected Vehicle
- Mercedes me
- Mercedes-Benz
- Telematics
- Vehicle Status
humanURL: https://developer.mercedes-benz.com/products/vehicle_status
properties:
- url: https://developer.mercedes-benz.com/products/vehicle_status
type: Documentation
- url: https://developer.mercedes-benz.com/products/vehicle_status/docs
type: Documentation
description: The Vehicle Status API delivers real-time vehicle state — doors, windows, deck lid, sunroof, tire pressure,
and overall lock state — for a customer-consented Mercedes-Benz vehicle by VIN. Returns last-known timestamps and uses
the standard Mercedes-Benz OAuth 2.0 customer-consent flow.
- aid: mercedes-me:mercedes-me-vehicle-lock-status-api
name: Mercedes-Benz Vehicle Lock Status API
tags:
- Automotive
- Connected Vehicles
- Lock Status
- Mercedes me
- Mercedes-Benz
- Telematics
tags_raw:
- Automotive
- Connected Vehicle
- Lock Status
- Mercedes me
- Mercedes-Benz
- Telematics
humanURL: https://developer.mercedes-benz.com/products/vehicle_lock_status
properties:
- url: https://developer.mercedes-benz.com/products/vehicle_lock_status
type: Documentation
- url: https://developer.mercedes-benz.com/products/vehicle_lock_status/docs
type: Documentation
description: The Vehicle Lock Status API returns the current door-lock, deck-lid, and position-lock state of a Mercedes-Benz
vehicle by VIN. Designed for parking, insurance, and security-monitoring use cases that need a minimal lock-only surface
separate from full Vehicle Status.
- aid: mercedes-me:mercedes-me-fuel-status-api
name: Mercedes-Benz Fuel Status API
tags:
- Automotive
- Connected Vehicles
- Fuel
- Mercedes me
- Mercedes-Benz
- Telematics
tags_raw:
- Automotive
- Connected Vehicle
- Fuel
- Mercedes me
- Mercedes-Benz
- Telematics
humanURL: https://developer.mercedes-benz.com/products/fuel_status
properties:
- url: https://developer.mercedes-benz.com/products/fuel_status
type: Documentation
- url: https://developer.mercedes-benz.com/products/fuel_status/docs
type: Documentation
description: The Fuel Status API exposes a Mercedes-Benz combustion vehicle's current tank level, remaining fuel range in
km, and last-update timestamp by VIN. Targeted at fueling, fleet, and concierge integrations.
- aid: mercedes-me:mercedes-me-electric-vehicle-status-api
name: Mercedes-Benz Electric Vehicle Status API
tags:
- Automotive
- Charging
- Connected Vehicles
- Electric Vehicles
- Mercedes me
- Mercedes-Benz
- Telematics
tags_raw:
- Automotive
- Charging
- Connected Vehicle
- Electric Vehicle
- EV
- Mercedes me
- Mercedes-Benz
- Telematics
humanURL: https://developer.mercedes-benz.com/products/electric_vehicle_status_3
properties:
- url: https://developer.mercedes-benz.com/products/electric_vehicle_status_3
type: Documentation
- url: https://developer.mercedes-benz.com/products/electric_vehicle_status_2/docs
type: Documentation
description: The Electric Vehicle Status API (currently at v3) provides charge state, state-of-charge percent, remaining
electric range in km, charging-active flag, and time-to-full estimates for Mercedes-EQ and EV-mode plug-in hybrid vehicles.
v2 also adds remote charge start/stop commands.
- aid: mercedes-me:mercedes-me-pay-as-you-drive-insurance-api
name: Mercedes-Benz Pay As You Drive 2.0 API
tags:
- Automotive
- Connected Vehicles
- Geolocation
- Insurance
- Mercedes me
- Mercedes-Benz
- Odometer
- Telematics
- Usage-Based Insurance
tags_raw:
- Automotive
- Connected Vehicle
- Geolocation
- Insurance
- Mercedes me
- Mercedes-Benz
- Odometer
- Telematics
- Usage-Based Insurance
humanURL: https://developer.mercedes-benz.com/products/pay_as_you_drive_insurance_2
properties:
- url: https://developer.mercedes-benz.com/products/pay_as_you_drive_insurance_2
type: Documentation
- url: https://developer.mercedes-benz.com/products/pay_as_you_drive_insurance_2/docs
type: Documentation
description: The Pay As You Drive 2.0 API supplies precise odometer readings and geographical position for a consented Mercedes-Benz
vehicle, designed for usage-based insurance, mileage-based subscriptions, and PAYD underwriting workflows.
- aid: mercedes-me:mercedes-benz-fleet-api
name: Mercedes-Benz Fleet API
tags:
- Automotive
- Connected Vehicles
- Fleet Management
- Kafka
- Mercedes-Benz
- Streaming
- Telematics
tags_raw:
- Automotive
- Connected Vehicle
- Fleet Management
- Kafka
- Mercedes-Benz
- Streaming
- Telematics
humanURL: https://developer.mercedes-benz.com/products/mercedes-benz_fleet_api
properties:
- url: https://developer.mercedes-benz.com/products/mercedes-benz_fleet_api
type: Documentation
- url: https://connectivity.mercedes-benz.com/products/mercedes-benz-fleet-api
type: Documentation
- url: https://github.com/mercedes-benz/kafka-integration-samples
type: SDKs
name: Kafka Integration Samples
description: The Mercedes-Benz Fleet API integrates vehicle data into fleet management systems without retrofit hardware.
It splits into a REST Management API (add vehicles, activate/deactivate per-vehicle data packages, issue remote commands)
and a Kafka Push API that streams location, mileage, fuel/charge, vehicle health, tires, door/window status, driving behavior,
and anti-theft events. Packages are activated individually at vehicle level.
- aid: mercedes-me:mercedes-me-components-api
name: Mercedes-Benz Mercedes me Components API
description: The Components API from Mercedes-Benz Mercedes me — 7 operation(s) for components.
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/image/v1/vehicles
tags:
- Components
properties:
- type: OpenAPI
url: openapi/mercedes-me-components-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-components-overlay.yaml
- aid: mercedes-me:mercedes-me-configurations-api
name: Mercedes-Benz Mercedes me Configurations API
description: Select equipment and configure a car
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/configurator/v1
tags:
- Configurations
properties:
- type: OpenAPI
url: openapi/mercedes-me-configurations-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-configurations-overlay.yaml
- aid: mercedes-me:mercedes-me-dealer-search-api
name: Mercedes-Benz Mercedes me Dealer search API
description: Resources that provide search functions for dealers (dealer, garage, retailer, etc.) based on given attributes.
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/dealer/v1
tags:
- Dealer search
properties:
- type: OpenAPI
url: openapi/mercedes-me-dealer-search-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-dealer-search-overlay.yaml
- aid: mercedes-me:mercedes-me-diagnostic-trouble-code-dtc-snapshots-api
name: Mercedes-Benz Mercedes me Diagnostic Trouble Code (DTC) Snapshots API
description: Remote Diagnostic Support service for view dtc snapshot List.
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/remotediagnostic/v1
tags:
- Diagnostic Trouble Code (DTC) Snapshots
properties:
- type: OpenAPI
url: openapi/mercedes-me-diagnostic-trouble-code-dtc-snapshots-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-diagnostic-trouble-code-dtc-snapshots-overlay.yaml
- aid: mercedes-me:mercedes-me-diagnostic-trouble-codes-dtc-s-api
name: Mercedes-Benz Mercedes me Diagnostic Trouble Codes (DTC's) API
description: Remote Diagnostic Support service for view dtc List.
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/remotediagnostic/v1
tags:
- Diagnostic Trouble Codes (DTC's)
properties:
- type: OpenAPI
url: openapi/mercedes-me-diagnostic-trouble-codes-dtc-s-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-diagnostic-trouble-codes-dtc-s-overlay.yaml
- aid: mercedes-me:mercedes-me-electronical-control-units-ecu-s-api
name: Mercedes-Benz Mercedes me Electronical Control Units (ECU's) API
description: Remote Diagnostic Support services for view ecu List.
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/remotediagnostic/v1
tags:
- Electronical Control Units (ECU's)
properties:
- type: OpenAPI
url: openapi/mercedes-me-electronical-control-units-ecu-s-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-electronical-control-units-ecu-s-overlay.yaml
- aid: mercedes-me:mercedes-me-images-api
name: Mercedes-Benz Mercedes me Images API
description: Get images for the vehicle configuration and its components
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/configurator/v1
tags:
- Image
tags_raw:
- Images
properties:
- type: OpenAPI
url: openapi/mercedes-me-images-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-images-overlay.yaml
- aid: mercedes-me:mercedes-me-perspectives-api
name: Mercedes-Benz Mercedes me Perspectives API
description: The Perspectives API from Mercedes-Benz Mercedes me — 1 operation(s) for perspectives.
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/image/v1/vehicles
tags:
- Perspectives
properties:
- type: OpenAPI
url: openapi/mercedes-me-perspectives-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-perspectives-overlay.yaml
- aid: mercedes-me:mercedes-me-references-api
name: Mercedes-Benz Mercedes me References API
description: Provide static reference data about cars like markets, bodies, classes, etc.
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/configurator/v1
tags:
- References
properties:
- type: OpenAPI
url: openapi/mercedes-me-references-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-references-overlay.yaml
- aid: mercedes-me:mercedes-me-resources-api
name: Mercedes-Benz Mercedes me Resources API
description: Remote Diagnostic Support service for view all resources.
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/remotediagnostic/v1
tags:
- Resources
properties:
- type: OpenAPI
url: openapi/mercedes-me-resources-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-resources-overlay.yaml
- aid: mercedes-me:mercedes-me-saved-configurations-api
name: Mercedes-Benz Mercedes me Saved configurations API
description: Store and load configurations with an onlinecode
humanURL: https://developer.mercedes-benz.com/products/configurator
baseURL: https://api.mercedes-benz.com/configurator/v1
tags:
- Saved configurations
properties:
- type: OpenAPI
url: openapi/mercedes-me-saved-configurations-api-openapi.yml
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator
- type: Documentation
url: https://developer.mercedes-benz.com/products/configurator/docs
- type: JSONSchema
url: json-schema/mercedes-me-vehicle-configuration-schema.json
- type: JSONLD
url: json-ld/mercedes-me-context.jsonld
- type: Documentation
url: https://developer.mercedes-benz.com/products/dealer
- type: Documentation
url: https://developer.mercedes-benz.com/products/vehicle_images
- type: Documentation
url: https://developer.mercedes-benz.com/products/remote_diagnostic_support
- type: JSONSchema
url: json-schema/mercedes-me-dtc-readout-schema.json
- type: Overlay
url: overlays/mercedes-me-saved-configurations-overlay.yaml
name: Mercedes-Benz Mercedes me
description: 'Mercedes-Benz operates one of the few genuinely public OEM API platforms. Its /developers portal at developer.mercedes-benz.com
sells connected-vehicle data as individually-subscribable products — Vehicle Status, Vehicle Lock Status, Fuel Status, Electric
Vehicle Status and Pay As You Drive — each gated by its own OAuth 2.0 scope and each requiring the vehicle owner''s explicit
per-signal consent, granted through the Mercedes-Benz identity provider at id.mercedes-benz.com. Alongside them sit four
content and service APIs with published Swagger 2.0 contracts: the Car Configurator, the Dealer API, the Vehicle Images
API and Remote Diagnostic Support. Mercedes-Benz Connectivity Services GmbH sells the Fleet API separately, pairing a REST
management surface with a managed Apache Kafka push channel that streams nineteen activatable telemetry packages plus five
remote-command packages, including remote door lock and unlock. Every API is versioned by URI path and shipped with a *_tryout
sandbox base path on the same host.'
maintainers:
- FN: API Evangelist
email: info@apievangelist.com
url: https://apievangelist.com
role: profile-maintainer
note: This profile is maintained by API Evangelist, not by Mercedes-Benz. Mercedes-Benz publishes no maintainer contact
for its API platform; support is a ticket inside the authenticated portal.
created: '2025-05-25'
modified: '2026-08-26'
tags:
- Automotive
- Connected Vehicles
- Daimler
- Fleet Management
- Mercedes me
- Mercedes-Benz
- OEM
- Telematics
- Vehicle Data
tags_raw:
- Automotive
- Connected Car
- Connected Vehicle
- Daimler
- Fleet Management
- Mercedes me
- Mercedes-Benz
- OEM
- Telematics
- Vehicle Data
kind: contract
accessModel:
pricing: freemium
onboarding: self-serve
trial: true
try_now: true
public: false
gated: none
gated_source:
- onboarding
label: Freemium (free trial) · Self-serve signup
confidence: high
source:
- plans
- authentication
- scopes
- rate-limits
- security
generated: '2026-11-06'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/mercedes-me.png
access: 3rd-Party
common:
- type: CapabilityMap
url: capabilities/mercedes-me-capability-edges.yml
name: Mercedes-Benz Mercedes me Business Capability Map
- type: AgenticAccess
url: agentic-access/mercedes-me-agentic-access.yml
- type: VulnerabilityDisclosure
url: security/mercedes-me-vulnerability-disclosure.yml
- type: DomainSecurity
url: security/mercedes-me-domain-security.yml
- type: Portal
url: https://developer.mercedes-benz.com/
name: Mercedes-Benz /developers
- type: Documentation
url: https://developer.mercedes-benz.com/products
name: API Products Catalog
- type: SDKs
url: https://developer.mercedes-benz.com/sdks
name: Mercedes-Benz SDKs
- type: SDKs
url: https://github.com/mercedes-benz/MBSDK-Mobile-Android
name: MBSDK Mobile - Android
- type: SDKs
url: https://github.com/mercedes-benz/MBSDK-Mobile-iOS
name: MBSDK Mobile - iOS
- type: SDKs
url: https://github.com/mercedes-benz/MBSDK-community-support
name: MBSDK Community Support (Archived)
- type: SDKs
url: https://github.com/mercedes-benz/kafka-integration-samples
name: Kafka Integration Samples (Fleet API)
- type: GitHub
url: https://github.com/mercedes-benz
name: Mercedes-Benz Group GitHub
- type: GitHub
url: https://github.com/mercedes-benz/foss
name: Mercedes-Benz FOSS Landing
- type: GitHub
url: https://github.com/mercedes-benz/mercedes-benz-foss-manifesto
name: Mercedes-Benz FOSS Manifesto
- type: Postman
url: https://www.postman.com/mbdevelopers/mercedes-benz/overview
name: Mercedes-Benz Postman Workspace
- type: Connectivity
url: https://connectivity.mercedes-benz.com/
name: Mercedes-Benz Connectivity Services
- type: LinkedIn
url: https://www.linkedin.com/company/mercedes-benz-ag/
name: Mercedes-Benz AG on LinkedIn
- type: Twitter
url: https://twitter.com/MercedesBenz
name: '@MercedesBenz on Twitter'
- type: ConsumerApp
url: https://www.mbusa.com/en/mercedes-benz-app
name: Mercedes me App (US)
- type: Payments
url: https://group.mercedes-benz.com/innovations/digitalisation/connectivity/mercedes-pay.html
name: Mercedes pay (in-car payments)
- type: Payments
url: https://www.mercedes-benz-mobility.com/en/what-we-do/payment-services/
name: Mercedes-Benz Mobility Payment Services
- type: Vocabulary
url: vocabulary/mercedes-me-vocabulary.yml
name: Mercedes me Vocabulary
- type: SpectralRules
url: rules/mercedes-me-rules.yml
name: Mercedes me Spectral Ruleset
- type: Plans
url: plans/mercedes-me-plans-pricing.yml
name: Mercedes me Plans & Pricing
- type: RateLimits
url: rate-limits/mercedes-me-rate-limits.yml
name: Mercedes me Rate Limits
- type: FinOps
url: finops/mercedes-me-finops.yml
name: Mercedes me FinOps Alignment
- type: WellKnown
url: well-known/mercedes-me-well-known.yml
name: Well-Known Document Probe
- type: Authentication
url: authentication/mercedes-me-authentication.yml
name: Authentication Profile
- type: OAuthScopes
url: scopes/mercedes-me-scopes.yml
name: OAuth Scopes (probed from the Mercedes-Benz identity provider)
- type: Security
url: security/mercedes-me-vulnerability-disclosure.yml
name: Vulnerability Disclosure Programme
- type: Conventions
url: conventions/mercedes-me-conventions.yml
name: Runtime Conventions and Reversibility
- type: ErrorCatalog
url: errors/mercedes-me-problem-types.yml
name: Error Catalogue
- type: Lifecycle
url: lifecycle/mercedes-me-lifecycle.yml
name: Versioning and Lifecycle
- type: Conformance
url: conformance/mercedes-me-conformance.yml
name: Standards Conformance
- type: DataModel
url: data-model/mercedes-me-data-model.yml
name: Data Model
- type: Sandbox
url: sandbox/mercedes-me-sandbox.yml
name: Sandbox (tryout base paths)
- type: Packages
url: packages/mercedes-me-packages.yml
name: Client Library Inventory
- type: SDKs
url: packages/mercedes-me-packages.yml
name: First-party SDK inventory (all twelve MBSDK repositories archived since 2021)
- type: AgentSkill
url: skills/_index.yml
name: Agent Skills
- type: LLMsTxt
url: llms/mercedes-me-llms.txt
name: llms.txt (generated by API Evangelist)
- type: MCPCandidate
url: mcp/mercedes-me-mcp.yml
name: MCP Tool Candidate (Mercedes-Benz ships no MCP server)
- type: EventCatalog
url: asyncapi/mercedes-me-fleet-event-catalog.yml
name: Fleet API Kafka Event Surface (no AsyncAPI published)
features:
- type: APIPlatform
name: Self-Service Developer Portal
description: A public, self-service developer portal at developer.mercedes-benz.com lets any developer register an application,
manage API keys/OAuth client credentials, subscribe to API products, and try requests via the integrated console.
- type: Authentication
name: OAuth 2.0 Customer Consent
description: Connected-vehicle APIs (Vehicle Status, Fuel Status, EV Status, Vehicle Lock Status, PAYD) use a Mercedes-Benz-hosted
OAuth 2.0 authorization-code flow where the vehicle owner explicitly grants per-resource consent (e.g. lock state, fuel
level) to a third-party app.
- type: PerResourceConsent
name: Granular Per-Resource Scopes
description: Connected-vehicle APIs split consent into fine-grained scopes — odometer, geo position, lock state, fuel, charge,
tire pressure — so apps only request the minimum data required.
- type: ProductBased
name: Product-Style API Subscriptions
description: Each API is exposed as a "product" with a dedicated docs/specs/details/console tab, allowing independent subscription,
pricing, and lifecycle management.
- type: Streaming
name: Kafka Push API
description: The Fleet API includes a managed Kafka Push API that streams vehicle telemetry events (location, fuel/charge,
health, tires, doors, anti-theft) directly into fleet management systems with OAuth 2.0-authenticated Kafka clients.
- type: SDKs
name: Mobile SDK (MBSDK)
description: Native iOS (Swift) and Android (Kotlin) modules encapsulate customer/car data, authentication, vehicle assignment,
and service activation so partner apps can ship Mercedes me integrations quickly.
- type: VINKeyed
name: VIN/FIN-Indexed Operations
description: All connected-vehicle operations are keyed by VIN/FIN, matching Mercedes-Benz's vehicle-identity model and
enabling consistent telemetry, diagnostics, and command routing across products.
- type: AsyncPolling
name: Async Polling for Diagnostics
description: The Remote Diagnostic Support API uses an asynchronous create-then-poll pattern (readouts) so long-running
ECU/DTC reads don't block client connections.
- type: Sandbox
name: Tryout / Sandbox Environments
description: All public APIs ship with a *_tryout basePath (e.g. /configurator_tryout/v1) for sandbox-only development against
synthetic data before production credentials are issued.
use_cases:
- name: Connected Vehicle App
description: Build a Mercedes me-style companion app showing fuel/charge level, lock status, last known location, and door/window
state for a customer's vehicles.
- name: Usage-Based Insurance
description: Underwrite per-mile or per-trip insurance policies using the Pay As You Drive 2.0 API's odometer and geo position
feeds, with explicit owner consent.
- name: Fleet Management Integration
description: Stream live telemetry for thousands of vehicles into a fleet platform via the Fleet API Kafka Push, using the
Management API to activate per-vehicle data packages on demand.
- name: Remote Roadside Diagnostics
description: Read DTCs and ECU inventories remotely via the Remote Diagnostic Support API so roadside-assistance operators
can triage breakdowns before dispatching a technician.
- name: EV Charging Concierge
description: Combine Electric Vehicle Status with third-party charging-network APIs to recommend chargers based on real
state-of-charge and remaining range.
- name: Dealer Locator and Service Booking
description: Use the Dealer API to build dealer-finder widgets and integrate with the Mercedes me service appointment booking
flow.
- name: Online Configurator Embeds
description: Embed Mercedes-Benz configuration experiences in third-party properties (e.g. classifieds, automotive media,
leasing portals) using the Car Configurator API and Vehicle Images API together.
- name: Telematics-Triggered Aftersales
description: Combine Vehicle Status, Fuel Status, and Remote Diagnostic Support to trigger proactive service, refuel, or
recall notifications.
integrations:
- name: Smartcar
type: 3rd-Party
description: Multi-OEM connected-car API aggregator exposing Mercedes-Benz alongside other brands via a unified surface
(smartcar.com/brand/mercedes-benz).
- name: Apache Kafka
type: Streaming
description: Fleet API Push channel uses Kafka with OAuth-authenticated consumer clients.
- name: OAuth 2.0
type: Authentication
description: Customer-consent flow across all connected-vehicle APIs.
- name: Mercedes pay
type: Payments
description: In-car payment platform that pairs with vehicle identity for fueling, parking, and tolling flows.
solutions:
- name: OEM API Platform
description: Mercedes-Benz operates a full OEM API platform — a model for how an automaker can expose connected vehicle
data, configurator content, dealer data, and diagnostics under one self-service developer portal.
- name: Connected Vehicle Data Productization
description: Each connected-vehicle data axis (lock, fuel, charge, odometer, position, diagnostics) is treated as its own
independently-subscribable product with its own scope, docs, and pricing.
- name: Fleet Telematics-as-a-Service
description: The Fleet API replaces aftermarket telematics dongles with native, OEM-grade telemetry streamed via Kafka,
sold as a managed service.
x-enrichment:
date: '2026-08-26'
status: enriched
artifacts_added: 31
pass: local-v1
Mercedes-Benz Mercedes me API — frequently asked questions
Does Mercedes-Benz Mercedes me have an API?
Yes. APIs.io lists 17 APIs from Mercedes-Benz Mercedes me, including Mercedes-Benz Vehicle Status API, Mercedes-Benz Vehicle Lock Status API and Mercedes-Benz Fuel Status API, and 14 more.
Is there an OpenAPI specification for the Mercedes-Benz Mercedes me API?
Yes. APIs.io indexes 11 OpenAPI specifications for Mercedes-Benz Mercedes me, each linked for download from this page.
How do I authenticate with the Mercedes-Benz Mercedes me API?
Mercedes-Benz Mercedes me documents its authentication (3 schemes). The details are profiled on APIs.io as Mercedes Me Authentication.
How much does the Mercedes-Benz Mercedes me API cost?
APIs.io lists 4 pricing plans for Mercedes-Benz Mercedes me, with each plan's price, limits and inclusions under Pricing on this page.
Is the Mercedes-Benz Mercedes me API ready for AI agents?
Mercedes-Benz Mercedes me has a Kin Score of 50.4 out of 100 (developing) and an Agent Readiness score of 43.0 (agent-ready), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: