Yes for the 3 operations checked: an anonymous request was refused, on 2026-09-15. Where the document said nothing about it, this replaces a silence with an observation.
ERR-2026-1816, ERR-2026-2049, ERR-2026-2064
3 open records, observed 2026-09-10. Every claim below carries the command that disproves it. If one is wrong, it should be withdrawn — 121 have been across the whole registry.
The document establishes no authentication requirement for this operation; an anonymous request is refused with 401. The requirement is now observed rather than unknown.
ERR-2026-1816 | GET /uv | HTTP 403 | checked 2026-09-15, 2 times |
ERR-2026-2049 | GET /protection | HTTP 403 | checked 2026-09-15, 2 times |
ERR-2026-2064 | GET /forecast | HTTP 403 | checked 2026-09-15, 2 times |
Check it yourself:
curl -sS -o /dev/null -w '%{http_code}\n' https://api.openuv.io/api/v1/uv
Run its check. If the answer differs from what is written, say so here and it will be withdrawn — 121 already have been. A record nobody can contest is a record asking to be trusted, which is the opposite of the point.
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.
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@b7cb54d3a847. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.