BYTETOOLS

Status & verification

Two different things get called “uptime” on a site like this one, and they deserve separate answers. The tools have no server that can go down. The 767 APIs we document belong to other people and can break at any time — so this page reports when each one was last confirmed working, and every case where a failed check is expected rather than a fault.

767APIs documented767/767returned 2xx when captured21 Aug 2026most recent check20documented exceptions

The tools

Every tool runs entirely in your browser. There is no upload, no account and no API call behind them, so there is no backend that can be degraded while the page still loads. If a tool page opens, the tool works.

The one dependency is static hosting. If that is unreachable you will not be reading this page, which is precisely why we do not publish a self-reported uptime figure — a status page hosted on the system it reports on cannot tell you it is down.

The API directory

The 767 documented APIs are third-party services. Hosts move, versions get bumped and free tiers get withdrawn, so the curl commands and JSON responses on those pages decay unless someone checks them.

A script replays every documented request against the live endpoint and reports what came back. This page is the result: not a synthetic monitor polling every minute, but a record of when each endpoint was last executed for real.

Last verification sweep

No sweep has been recorded since the last deploy. The per-entry dates below are still the real thing: each one is the day that API's documented request was last executed against the live endpoint and returned the response published on its page.

Verification freshness by category

Every documented API carries the date its example was last confirmed working. The most recent check across the whole directory was 21 Aug 2026, 4 days ago; the oldest is 19 Aug 2026.

CategoryAPIsOldest checkNewest checkExceptions
Developer & Testing APIs8619 Aug 202621 Aug 20261
Finance & Crypto APIs7919 Aug 202621 Aug 20262
Game & Anime APIs6419 Aug 202621 Aug 2026
Government & Open Data APIs6319 Aug 202621 Aug 20261
Science & Space APIs6119 Aug 202621 Aug 20264
Geolocation & IP APIs4519 Aug 202621 Aug 2026
Transport & Vehicle APIs4119 Aug 202621 Aug 20262
Entertainment APIs2919 Aug 202621 Aug 2026
Security & Auth APIs2919 Aug 202621 Aug 2026
Health & Medical APIs2619 Aug 202621 Aug 2026
Video & Streaming APIs2619 Aug 202621 Aug 2026
Utility APIs2319 Aug 202621 Aug 20264
Photography & Design APIs2219 Aug 202621 Aug 20262
Book & Dictionary APIs1919 Aug 202621 Aug 2026
Weather APIs1819 Aug 202621 Aug 2026
Business & Commerce APIs1819 Aug 202621 Aug 20261
Music APIs1519 Aug 202621 Aug 20261
Sports & Fitness APIs1519 Aug 202621 Aug 20262
Environment APIs1519 Aug 202621 Aug 2026
Animal APIs1419 Aug 202621 Aug 2026
News & Open Data APIs1319 Aug 202621 Aug 2026
Social Media APIs1119 Aug 202621 Aug 2026
Food & Drink APIs1019 Aug 202621 Aug 2026
Text Analysis APIs919 Aug 202621 Aug 2026
Machine Learning & AI APIs821 Aug 202621 Aug 2026
Email APIs819 Aug 202621 Aug 2026

Known exceptions (20)

These 20 endpoints fail or redirect under automated checking for reasons that are not the API being broken. Publishing the list is the point: an automated check that quietly excuses failures is indistinguishable from one that never ran. Each is re-checked by hand with curl from time to time.

Bot filter3

The provider's firewall rejects Node's HTTP client but serves curl the identical request. Confirmed by hand with curl, which is the tiebreaker because it is not subject to the same fingerprinting.

  • COLOURlovers

    The firewall fingerprints and rejects Node's undici with a 403, while curl gets HTTP 200 from the identical URL and headers.

  • FBI Wanted

    A Cloudflare-style WAF fingerprints and rejects Node's undici outright. curl and Python both get HTTP 200 from the same URL with the same headers.

  • OPEC Basket Price

    Sends the required Accept-Language header and still 403s under Node; curl with the identical header and URL gets HTTP 200. Same fingerprinting class as the other two.

Documented alias5

The published URL is a shortcut the provider redirects from. Following the redirect is the intended behaviour, so the automated check reports a redirect where nothing is wrong.

  • Al Adhan Prayer Times

    Omitting the date from timingsByCity is documented as "today", so the API redirects to the dated URL. Same class of alias as the NHL '/now' endpoint.

  • Google Favicon Service

    The documented URL keeps working; the redirect target is internal to Google and changes shape, so pinning it would break the example rather than fix it.

  • LoremFlickr

    Redirects to a per-request cache path for the randomly chosen photo, so the target is different on every call by design.

  • NHL Web API

    `/standings/now` is an intentional alias that 302s to the current date. Following the redirect is the documented behaviour.

  • RDAP (Domain Lookup)

    rdap.org is a bootstrap service: it looks up the authoritative registry for the TLD and redirects there. Following the redirect is the protocol.

Shared free quota8

A free allowance shared across every anonymous caller. A 429 means the day's quota is spent — often by our own repeat checks — not that the API is down. Each entry states the limit.

  • Agify

    Agify, Genderize and Nationalize are one provider (Demografix) sharing a single free allowance of 100 names per day per IP, answering 429 with {"error":"Request limit reached"} once it is spent. Several verifier runs in a day exhaust it on their own. All three pages state the daily limit and carry a 429 entry.

  • Can I Enter (Visa Rules)

    The free tier allows 5 requests per IP per day, so the second verifier run of any day 429s. Quota exhaustion, the same class as the NASA DEMO_KEY entries.

  • Genderize

    Agify, Genderize and Nationalize are one provider (Demografix) sharing a single free allowance of 100 names per day per IP, answering 429 with {"error":"Request limit reached"} once it is spent. Several verifier runs in a day exhaust it on their own. All three pages state the daily limit and carry a 429 entry.

  • NASA APOD

    NASA's DEMO_KEY is shared globally and capped near 30 requests/hour per IP. The verifier alone hits four NASA endpoints, so a 429 means the shared demo quota is spent. Each page tells readers to register their own free key for exactly this reason.

  • NASA DONKI

    NASA's DEMO_KEY is shared globally and capped near 30 requests/hour per IP. The verifier alone hits four NASA endpoints, so a 429 means the shared demo quota is spent. Each page tells readers to register their own free key for exactly this reason.

  • NASA EPIC

    NASA's DEMO_KEY is shared globally and capped near 30 requests/hour per IP. The verifier alone hits four NASA endpoints, so a 429 means the shared demo quota is spent. Each page tells readers to register their own free key for exactly this reason.

  • NASA NeoWs (Asteroids)

    NASA's DEMO_KEY is shared globally and capped near 30 requests/hour per IP. The verifier alone hits four NASA endpoints, so a 429 means the shared demo quota is spent. Each page tells readers to register their own free key for exactly this reason.

  • Nationalize

    Agify, Genderize and Nationalize are one provider (Demografix) sharing a single free allowance of 100 names per day per IP, answering 429 with {"error":"Request limit reached"} once it is spent. Several verifier runs in a day exhaust it on their own. All three pages state the daily limit and carry a 429 entry.

Upstream load shedding3

Intermittent 5xx coming from infrastructure behind the API rather than the API itself. Documented in the entry's own errors section rather than hidden.

  • Cover Art Archive

    Proxies to Internet Archive infrastructure that sheds load. The entry documents this intermittency in its errors section rather than pretending the endpoint is reliable.

  • OECD Data Explorer

    Answers 200 to a standalone request (curl and Node alike) but 500s under the verifier's 4-way concurrency. Load shedding on OECD's side, not a dead endpoint.

  • ParkenDD

    Returns 500 on roughly one request in three (measured 2 of 6 across curl and Node). It scrapes municipal car-park sites, so a 500 tracks an upstream city site being down rather than the API being broken. The entry's errors section documents this.

Provider lockout1

The provider deliberately blocks anonymous access under stated conditions. A failed check during one of those windows is the product working as documented.

  • OpenF1

    Blocks all unauthenticated access while an F1 session is running, past seasons included, and says so in the 401 body. Documented product behaviour, so a verifier run during a race weekend is expected to fail here.

How verification works

  • Every documented request is replayed against the live endpoint — the real URL, method, headers and body shown on the page.
  • A failure is retried once after a pause, because running many hosts concurrently produces resets that look identical to a dead API.
  • Successful responses are captured and published verbatim. Nothing on an API page is hand-written JSON.
  • Redirects are reported: if a documented URL is no longer canonical, the entry is updated rather than left pointing at a moved endpoint.
  • Known exceptions live in one file that both the checker and this page read, so the two can never disagree about what counts as expected.
  • An API that stops working for real is removed, not left listed. That is the failure mode this directory exists to avoid.

Each API is an independent third-party service with its own availability, and is not affiliated with ByteTools. Nothing here is a service-level commitment on their behalf or ours.

Found something broken?

An endpoint that stopped working, a response that no longer matches, a rate limit that changed — tell us and it gets checked. Reports about a specific API are the fastest way to keep this directory honest between sweeps.

support@bytevancer.comOther ways to reach us