Install Jentic One Beta

Connect the Mercedes-Benz Developer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mercedes-Benz Developer API, 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-developer-api" | 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-developer-api" | 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 Mercedes-Benz Developer API.

Read live status (fuel, mileage, lock state) for a Mercedes-Benz vehicle by vehicleId

Retrieve the current GPS location of an authorised Mercedes-Benz vehicle

Send a remote command to lock or unlock the doors of a vehicle

Send a remote command to open or close vehicle windows

List markets, models, and configurations through the embedded configurator surface

GET STARTED

Start building with Mercedes-Benz Developer API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Mercedes-Benz Developer API for, with concrete tasks.

★ Owner companion app

Mercedes-Benz vehicle owners and approved partners build companion apps that combine GET /vehicles/{vehicleId}/status, GET /vehicles/{vehicleId}/location, and POST /vehicles/{vehicleId}/doors into one experience. The customer sees fuel level, parked location, and lock state in a single view and can lock the car if they forgot to. Because every endpoint is on one base URL, the integrator manages one apiKey instead of stitching multiple products together.

GET /vehicles/{vehicleId}/status to read fuel and lock state, GET /vehicles/{vehicleId}/location for parked coordinates, then POST /vehicles/{vehicleId}/doors with the lock command if doors are open.

Fleet operations dashboard

Fleet managers running Mercedes-Benz vehicles use the developer API to consolidate live status and location across the fleet. GET /vehicles enumerates the registered vehicleIds, then per-vehicle calls to /status and /location populate a single ops dashboard. Remote door commands give fleet ops the ability to grant or revoke access to drivers without dispatching a key.

GET /vehicles for the fleet, then for each vehicleId call /status and /location and write the results to the dashboard's metrics store.

Sales journey from configure to nearest dealer

A retail integration uses the embedded configurator endpoints (/configurator/markets, /configurator/markets/{marketId}/models) to build a vehicle, then calls /dealers to surface the nearest Mercedes-Benz dealership in the customer's country. The whole sales journey lives on one base URL with one credential, simplifying integration compared to combining the standalone Configurator and Dealer APIs.

GET /configurator/markets/{marketId}/models to list models, walk the configurator path to assemble a build, then GET /dealers with the same country to return the closest dealer.

Agent-driven vehicle command via Jentic

An AI assistant uses Jentic to action a customer request like 'lock my car' or 'how much fuel do I have left'. Jentic exposes the developer API operations by intent so the agent calls /vehicles/{vehicleId}/status or /vehicles/{vehicleId}/doors without managing the apiKey, and returns the result in chat.

Search Jentic for 'lock mercedes-benz doors', load the POST /vehicles/{vehicleId}/doors schema, execute it with the customer's vehicleId and the lock command, and return the success state.

Key Endpoints

11 endpoints — the mercedes-benz developer api is the consolidated entry point for the developer-portal product family.

METHOD

PATH

DESCRIPTION

GET

/vehicles

List the customer's registered Mercedes-Benz vehicles

GET

/vehicles/{vehicleId}/status

Read live vehicle status (fuel, mileage, locks)

GET

/vehicles/{vehicleId}/location

Get the vehicle's current GPS location

POST

/vehicles/{vehicleId}/doors

Send a remote door lock/unlock command

POST

/vehicles/{vehicleId}/windows

Send a remote window control command

GET

/vehicles

List the customer's registered Mercedes-Benz vehicles

GET

/vehicles/{vehicleId}/status

Read live vehicle status (fuel, mileage, locks)

GET

/vehicles/{vehicleId}/location

Get the vehicle's current GPS location

POST

/vehicles/{vehicleId}/doors

Send a remote door lock/unlock command

POST

/vehicles/{vehicleId}/windows

Send a remote window control command

Why Jentic?

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

Setup

Wiring the Mercedes-Benz Developer API by hand means getting a developer-portal apiKey plus per-customer tokens, attaching them to each call, and coding status, location, and remote-control requests against the vehicles host yourself. Through Jentic you install once, import the Mercedes-Benz Developer API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The Developer API puts the vehicle id in the URL path (/vehicles/{vehicleId}/status), so a rule can pin your agent to one vehicle. You choose the operations it may call, so a rule can grant read-only status and location while leaving out remote-control writes like door or window operations unless you add them.

Credential isolation

Your Mercedes-Benz apiKey and any per-customer 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 'check Mercedes vehicle status' or 'lock the doors', and Jentic returns the matching Developer API operation with its vehicleId schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Mercedes-Benz Developer API through Jentic.

What authentication does the Mercedes-Benz Developer API use?

The spec declares an apiKey scheme. Vehicle-data endpoints additionally require a customer-authorised access flow through the Mercedes-Benz developer portal. Jentic stores the apiKey in its encrypted vault so the agent never handles it directly.

Can I remotely lock the doors with the Mercedes-Benz Developer API?

Yes. POST /vehicles/{vehicleId}/doors sends a remote lock or unlock command for an authorised vehicle, provided the customer has consented and the vehicle is connected.

What are the rate limits for the Mercedes-Benz Developer API?

Numeric limits are not in the spec - they are set per developer-portal contract. Vehicle command endpoints are deliberately rate-limited more strictly than read endpoints to avoid actuator wear.

How do I check a customer's fuel level through Jentic?

Search Jentic for 'mercedes vehicle status', load the GET /vehicles/{vehicleId}/status schema, and execute it with the customer's vehicleId. The response includes fuel, mileage, and lock state in one call.

Does this API replace the standalone Configurator and Dealer APIs?

It exposes a subset of the same functionality under /configurator and /dealers, with one apiKey and one base URL. For deeper configurator features (saved builds, full reference masterdata) the standalone Configurator API still has more endpoints.

Can I open the windows remotely on any Mercedes-Benz vehicle?

POST /vehicles/{vehicleId}/windows is supported, but only on connected Mercedes-Benz vehicles whose owner has authorised the integrating application via the Mercedes-Benz developer portal consent flow.

Can I limit what my agent is allowed to do with the Mercedes-Benz Developer API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and since the vehicle id sits in the URL path you can pin the agent to a single vehicle. You can grant read-only access to GET /vehicles/{vehicleId}/status and GET /vehicles/{vehicleId}/location while withholding the remote-control writes, so the agent cannot POST to /vehicles/{vehicleId}/doors or /vehicles/{vehicleId}/windows unless you add those operations. The apiKey and any per-customer tokens are stored by your instance and injected at execution time, never reaching the agent's prompt or logs.

Mercedes-Benz Developer API

Browse all Mercedes Benz APIs

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyIOTDevice ManagementapiKey11 EndpointsREST

For Agents

Read vehicle status and location, send remote door/window commands, configure cars, and locate dealers across 11 endpoints from one Mercedes-Benz developer entry point.

Use for: Get the fuel level for my Mercedes-Benz, Lock the doors on my E-Class remotely, Find out where my Mercedes-Benz is parked, Retrieve the available models in the Mercedes configurator for Germany

Not supported: Does not handle service bookings, payments, deep diagnostic readouts, or vehicle imagery - use for vehicle status, location, basic remote control, configuration, and dealer search only.

The Mercedes-Benz Developer API is the consolidated entry point for the developer-portal product family. It exposes vehicle status (fuel level, lock state, mileage), vehicle location, remote control commands for doors and windows, an embedded car configurator surface, and the dealer locator under a single base URL. Each operation is keyed to a vehicleId or marketId so an integrator can mix telematics with shopping flows in one client.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

42%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Mercedes-Benz Developer API to your agent

Capabilities

Start building with Mercedes-Benz Developer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mercedes-Benz Developer API

Jentic AI Readiness Score

Mercedes-Benz Developer API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness