Install Jentic One Beta

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.

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-remote-diagnostic-support" | 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-remote-diagnostic-support" | 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 One

View OpenAPI Document

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 the DTC snapshot endpoint returns the 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.

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 — the mercedes-benz remote diagnostic support api lets authorised third parties pull on-board diagnostic data from a customer's mercedes-benz vehicle remotely, on the customer's consent.

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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Mercedes-Benz Remote Diagnostic Support by hand means running the OAuth 2.0 client-credentials and per-customer token flow, refreshing tokens against the remotediagnostic_tryout host, and posting the DTC and ECU readout requests yourself. Through Jentic you install once, import Remote Diagnostic Support from the API Directory, store the OAuth credentials once, and your agent calls it.

Permission scoping

Remote Diagnostic Support puts the vehicle id in the URL path (/vehicles/{vehicleId}/ecuReadouts), so a rule can pin your agent to one vehicle: it can read that vehicle's fault codes and ECU snapshots and nothing else. You choose the operations it may call, so a rule can grant DTC and ECU readouts while leaving out resource readouts you do not want included.

Credential isolation

Your Mercedes-Benz OAuth credentials and access tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'read Mercedes fault codes' or 'get a DTC snapshot', and Jentic returns the matching Remote Diagnostic Support operation with its vehicleId and ecuId schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Remote Diagnostic Support API through Jentic.

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 securely stores 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 customer 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.

Can I capture the conditions when a fault occurred?

Yes. POST /vehicles/{vehicleId}/ecuId/{ecuId}/dtcId/{dtcId}/dtcSnapshotReadouts returns the DTC snapshot recorded by the specified ECU at the moment the fault was logged, which a workshop can use to reproduce the issue.

Can I limit what my agent is allowed to do with the Remote Diagnostic Support API?

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use, and this API puts the vehicle id in the URL path (/vehicles/{vehicleId}/ecuReadouts), so a rule can pin the agent to a single vehicle and let it read only that car's fault codes and ECU snapshots. You also choose which operations it may call, so you can grant DTC and ECU readouts while leaving out the resource readouts you do not want included. Your Mercedes-Benz OAuth credentials are injected at execution time and never enter the agent's prompt or logs.

Mercedes Benz Remote Diagnostic Support

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

Browse all Mercedes Benz APIs

Community OpenAPI document · agent-readyIOTDevice Managementoauth24 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Use for: Read all active fault codes from a Mercedes-Benz vehicle by VIN, Get a DTC snapshot for a specific ECU on a customer's car, Retrieve ECU readouts for a Mercedes-Benz vehicle remotely, Check whether a Mercedes-Benz vehicle has any open trouble codes

Not supported: Does not handle vehicle control, location, fuel, configuration, or imagery - use for reading DTCs, ECU readouts, and DTC snapshots from a Mercedes-Benz vehicle only.

The Mercedes-Benz Remote Diagnostic Support API lets authorised third parties pull on-board diagnostic data from a customer's Mercedes-Benz vehicle remotely, 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). It is built for partners such as roadside assistance providers and authorised workshops who need fault data before sending a technician.

Jentic One on Github View OpenAPI Document

Connect the Remote Diagnostic Support to your agent

Capabilities

Start building with Remote Diagnostic Support API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mercedes Benz Remote Diagnostic Support