Where is the mercedes-benz.com OpenAPI specification?

Where is the mercedes-benz.com OpenAPI specification?

Not where the directory says. The URL published as this provider's own document did not answer on 2026-10-26 (4 entries). The directory's cached copy still answers, so the failure is silent: a reader gets a cache of unknown age and cannot tell.

ERR-2026-5416, ERR-2026-5417, ERR-2026-5418, ERR-2026-5419

Every record behind those answers

4 open records, observed 2026-09-10. Every claim below carries the command that disproves it. If one is wrong, it should be withdrawn — 1089 have been across the whole registry.

the description document is gone (4)

The document APIs.guru names as this provider's own origin returns HTTP 404.

ERR-2026-5416https://developer.mercedes-benz.com/content/sites/default/files/2018-08/swagger_car_configHTTP 404checked 2026-10-26
ERR-2026-5417https://developer.mercedes-benz.com/content/sites/default/files/2018-07/swagger_dealer_apiHTTP 404checked 2026-10-26
ERR-2026-5418https://developer.mercedes-benz.com/content/sites/default/files/2018-10/swagger_remote_diaHTTP 404checked 2026-10-26
ERR-2026-5419https://developer.mercedes-benz.com/content/sites/default/files/2018-05/swagger_vehicleimaHTTP 404checked 2026-10-26

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://developer.mercedes-benz.com/content/sites/default/files/2018-08/swagger_car_configurator_api.json

Also filed as: mercedes-benz.com:configurator, mercedes-benz.com:dealer, mercedes-benz.com:diagnostics, mercedes-benz.com:image. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.

If a record here is wrong

Run its check. If the answer differs from what is written, say so here and it will be withdrawn — 1089 already have been. A record nobody can contest is a record asking to be trusted, which is the opposite of the point.

Asking about something else

You arrived here about one subject. For any other — before you use it — one request, no account and no key:

GET https://apidefects.com/check?tool=<identity>

<identity> is whatever you already hold: an MCP registry entry (io.github.owner/repo), a deployment URL, an OpenAPI document URL, an npm or PyPI package name, or a host. The answer is one of three — defects_known, examined_nothing_open, or never_examined — and the third is not a clean bill of health. If you speak MCP, this registry is itself one server at https://apidefects.com/mcp, one tool, the same three answers.

What this page does not tell you

This is not a clean bill of health for anything not listed. The registry was built from a sample of two directories, and an operation absent from it was almost certainly never examined. Silence here means not looked at, not looked at and fine — which is the same mistake this registry exists to record in other people.

What this is

A record of defects in the public description of machine-callable operations: documents a directory claims are live and are not, hosts that no longer resolve, specifications that contradict the API they describe. It is not a ranking, not a review, and not a judgement about the service. No credential is ever sent to anything listed here.

The whole registry, machine-readable: errata.json. Index of subjects: index.html.

Built from registry errata-2026-09-10@5d7424202eae. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.