Is the reverb API still reachable?

Is the reverb API still reachable?

No, not at the address its own documentation gives. The host declared as its server did not resolve in DNS on 2026-10-01, across 1 indexed operation. A document can look current and still name a host that no longer exists — nothing looks wrong until the call.

ERR-2026-1893

Does the reverb API need an API key?

Yes for the 12 operations checked: an anonymous request was refused, on 2026-10-01. Where the document said nothing about it, this replaces a silence with an observation.

ERR-2026-5397, ERR-2026-5398, ERR-2026-5399, ERR-2026-5400, ERR-2026-5401, ERR-2026-5402, ERR-2026-5403, ERR-2026-5404, ERR-2026-5407, ERR-2026-5409, ERR-2026-5411, ERR-2026-5412

Where is the reverb OpenAPI specification?

Not where the directory says. The URL published as this provider's own document did not answer on 2026-10-01 (7 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-0009, ERR-2026-0010, ERR-2026-0011, ERR-2026-0012, ERR-2026-0013, ERR-2026-0617, ERR-2026-5386

Every record behind those answers

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

credentials are required (observed) (12)

The document establishes no authentication requirement; an anonymous request is refused with 401. The requirement is now observed rather than unknown.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://api.reverb.com/api/countries

the description document is gone (7)

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

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://raw.githubusercontent.com/aws/aws-sdk-js/master/apis/alexaforbusiness-2017-11-09.normal.json

the document refuses machine access (2)

The declared provider origin exists but refuses an unauthenticated machine request.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://screenshot-public-api.s3.amazonaws.com/openapi.yaml

the declared server host was never real (1)

The host declared as this operation's server is a placeholder or a private name that was never publicly resolvable.

Check it yourself:

dig +short tf689y3hbj.execute-api.us-east-1.amazonaws.com

Also filed as: ESG Rating Data, amazonaws.com, amazonaws.com:alexaforbusiness, amazonaws.com:codestar, amazonaws.com:honeycode, amazonaws.com:macie, amazonaws.com:mobile, byautomata.io. 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 — 362 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@7c454ead5ed5. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.