A useful starting point.
With the fine print.

What’s in the library?

The directory contains 2,112 APIs across 50 categories. Of those, 32 guides were individually checked against official provider documentation on 16 September 2026. The remaining 2,080 are community listings. The Astro redesign and playground were added on 2 October 2026; that does not imply that provider information was reverified on that date.

How the review labels work

Docs reviewed

We read provider documentation and included access notes, a use case, and a request example. This is not continuous endpoint testing, a provider endorsement, or a guarantee of current pricing.

Community listing

Information comes from an external catalog and may be outdated. Authentication, HTTPS and CORS are reported values. We have not checked the pricing.

Tested example

A community listing with an example request that we called once and that responded: with data, or with an authentication error when it needs your key. The date is on the page. Examples that failed are not published. This is a one-time check, not uptime monitoring, and the rest of the listing is still unreviewed.

No key

The listed endpoint is described as not requiring a private credential. Rate limits, usage conditions, and commercial restrictions can still apply.

Free access / free tier

A reviewed provider offers access or an allowance without payment, subject to its stated conditions. This does not mean unlimited use.

Where the data comes from

Community entries use locally saved snapshots of public-apis/public-apis and public-api-lists/public-api-lists. Both catalogs are MIT-licensed. Their licenses are included here: Public APIs license and Public API Lists license.

Duplicate records are consolidated. Community documentation links returning 404 or 410 in the saved check results are excluded. Link checking was partial and most requests were inconclusive; a successful documentation HEAD request does not establish API uptime, access, or terms.

What is eligible for indexing?

Reviewed guides, category pages, collections, and educational articles form the indexable core. Unreviewed detail pages remain browsable with a noindex directive and are excluded from the sitemap. Structured data describes visible content; we do not publish fabricated ratings, rankings, or reviews.

How the request playground handles data

All API execution happens in the visitor’s browser after pressing Send request. Credentials, custom headers, request bodies, and response data stay in current page memory. They are not saved to local storage, session storage, cookies, analytics, or a Find Public APIs backend. Reloading or leaving clears the editor.

The request goes directly to the selected HTTPS endpoint, whose provider may log or retain it. Browser extensions and browser tools can have access to page data. Use limited test credentials and inspect the destination before sending. Browser CORS restrictions apply, and this tool does not use a proxy. Redirects are blocked; automatic cookies are omitted. A failed browser request does not guarantee the provider did not process it.

Code previews use placeholders for entered values by default. You can explicitly reveal and copy those values. Response bodies may contain sensitive provider data; downloading a response creates a file on your device. Search terms can appear in the library URL, so do not put credentials in search.

Independence and updates

Curated order is an editorial starting point, not a popularity ranking. This edition has no paid placements or affiliate rankings and is not affiliated with the listed providers. Always use the linked official documentation as the final authority on access and usage conditions.

The website has no accounts or newsletter signup. Static hosting providers may process standard access logs. Provider websites have their own privacy policies.