Remote Diagnostic Support

Name: Remote Diagnostic Support API
Brand: Remote Diagnostic Support
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementoauth24 EndpointsREST

For Agents

Pull DTCs, ECU readouts, and DTC snapshots from a Mercedes-Benz vehicle by VIN/FIN across 4 POST endpoints designed for remote workshop diagnosis.

Connect the Remote Diagnostic Support to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Remote Diagnostic Support, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Remote Diagnostic Support API.

Read all active Diagnostic Trouble Codes from a Mercedes-Benz vehicle by vehicleId

Retrieve a DTC snapshot for a specific ECU and DTC combination to diagnose a fault

Pull readouts from a vehicle's electronic control units for deeper analysis

Fetch resource readouts to inspect raw diagnostic resources from the vehicle

GET STARTED

Start building with Remote Diagnostic Support API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Remote Diagnostic Support, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Remote Diagnostic Support, keeping it validated and agent-ready. The Mercedes-Benz Remote Diagnostic Support API lets authorised third parties pull on-board diagnostic data from a Mercedes-Benz vehicle on the customer's consent. It returns active Diagnostic Trouble Codes (DTCs), DTC snapshots from individual ECUs, ECU readouts, and resource readouts, all scoped per vehicleId (VIN/FIN). The API is designed for partners such as roadside assistance providers and authorised workshops who need fault data before sending a technician.

Use Cases

Patterns agents use Remote Diagnostic Support API for, with concrete tasks.

★ Roadside assistance pre-arrival triage

Roadside assistance providers (ADAC, ATU, RAC) read a stranded driver's vehicle DTCs before dispatching a technician. POST /vehicles/{vehicleId}/dtcReadouts returns the active fault codes, which the dispatcher uses to send the right specialist with the right parts. This shortens fix time and avoids second visits.

POST /vehicles/{vehicleId}/dtcReadouts with the customer's VIN and summarise the top fault for the dispatcher.

Independent workshop remote diagnosis

Authorised independent workshops pull ECU readouts and DTC snapshots remotely before the customer arrives. POST /vehicles/{vehicleId}/ecuReadouts captures ECU state and POST /vehicles/{vehicleId}/ecuId/{ecuId}/dtcId/{dtcId}/dtcSnapshotReadouts returns the snapshot conditions when a fault was logged, so parts and labour can be prepared ahead of time.

POST /vehicles/{vehicleId}/ecuReadouts to capture ECU state, then for each fault POST /vehicles/{vehicleId}/ecuId/{ecuId}/dtcId/{dtcId}/dtcSnapshotReadouts to retrieve the snapshot.

Fleet health monitoring

Fleet operators with Mercedes-Benz vehicles run scheduled DTC readouts to catch faults before they cause downtime. The vehicleId scoping lets the operator iterate VINs and consolidate fault data, prioritising vehicles with critical DTCs for service.

For each vehicleId in the fleet, POST /vehicles/{vehicleId}/dtcReadouts and aggregate active DTCs, flagging critical fault codes for service scheduling.

Agent-driven fault triage via Jentic

An AI assistant triages a customer's car remotely: the customer provides a VIN, the agent calls /vehicles/{vehicleId}/dtcReadouts and recommends an action. Jentic handles the OAuth credential and exposes diagnostic operations by intent, so the agent does not need to manage tokens directly.

Search Jentic for 'read mercedes fault codes', load the /dtcReadouts schema, execute it with the customer's vehicleId, and return the active DTCs with severity.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for remote diagnostic support, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/vehicles/{vehicleId}/dtcReadouts

Read active DTCs from a vehicle

POST

/vehicles/{vehicleId}/ecuReadouts

Pull readouts from the vehicle's ECUs

POST

/vehicles/{vehicleId}/ecuId/{ecuId}/dtcId/{dtcId}/dtcSnapshotReadouts

Retrieve a DTC snapshot for an ECU+DTC pair

POST

/vehicles/{vehicleId}/resourceReadouts

Read raw resource data from a vehicle

POST

/vehicles/{vehicleId}/dtcReadouts

Read active DTCs from a vehicle

POST

/vehicles/{vehicleId}/ecuReadouts

Pull readouts from the vehicle's ECUs

POST

/vehicles/{vehicleId}/ecuId/{ecuId}/dtcId/{dtcId}/dtcSnapshotReadouts

Retrieve a DTC snapshot for an ECU+DTC pair

POST

/vehicles/{vehicleId}/resourceReadouts

Read raw resource data from a vehicle

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

OAuth 2.0 client credentials and per-customer access tokens are stored in Jentic's vault. The agent sees only a scoped reference; raw tokens are injected when the diagnostic call executes.

Intent-based discovery

Agents search by intent (e.g. 'read mercedes fault codes') and Jentic returns the matching POST operation with its vehicleId/ecuId parameter schema.

Time to first call

Direct integration: 5-10 days to onboard, implement OAuth, and wire the diagnostic flows. Through Jentic: under 1 hour from search to first diagnostic call once OAuth credentials are vaulted.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Remote Diagnostic Support

An equivalent diagnostics spec entry under a different api_slug; same operations and base URL.

Either spec entry works; pick whichever path is referenced by the integrating tooling.

Alternative

Smartcar

Multi-brand connected-car API covering many manufacturers but with shallower DTC support.

Choose Smartcar when the integration must cover multiple brands; choose this API when Mercedes-only depth on ECU/DTC matters.

Complementary

Tesla Fleet API

Fleet operators with mixed marques use Tesla Fleet alongside Mercedes diagnostics for cross-brand fleet health.

Use Tesla Fleet for Tesla vehicles in the same fleet; use this API for Mercedes vehicles.

FAQs

Specific to using Remote Diagnostic Support API through Jentic.

Why is there no official OpenAPI spec for Remote Diagnostic Support?

Mercedes-Benz does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Remote Diagnostic Support via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Remote Diagnostic Support API use?

The API uses OAuth 2.0 with explicit customer consent — the Mercedes-Benz vehicle owner must authorise the third-party application before a partner can pull diagnostic data. Jentic vaults the OAuth client credentials and exchanges access tokens at execution time.

Can I read DTCs from a vehicle without the owner's consent?

No. Every diagnostic call is keyed to a vehicleId and requires an OAuth flow that the vehicle owner has authorised. The API is designed for legitimate partners operating with the customer's permission.

What are the rate limits for the Remote Diagnostic Support API?

Numeric limits are not in the spec. Production rate limits are negotiated per Mercedes-Benz developer portal contract; the tryout host is throttled for evaluation volumes.

How do I read fault codes for a customer's vehicle through Jentic?

Search Jentic for 'read mercedes fault codes', load the POST /vehicles/{vehicleId}/dtcReadouts schema, and execute it with the customer's VIN. Jentic handles the OAuth exchange and returns the active DTCs.

Why are diagnostic operations modelled as POST instead of GET?

DTC and ECU readouts cause the vehicle to perform an active diagnostic operation, so they are POSTs rather than idempotent GETs to reflect the side effect on the car.