What's the difference between public-apis on GitHub and a site like publicapis.io?

public-apis on GitHub is a curated markdown list maintained collaboratively via pull requests. It's the source-of-truth catalog used by many downstream sites and search results. publicapis.io is a polished web frontend with search, filtering, and a JSON API, but its catalog is largely derived from the same public sources. The GitHub repo is best for discovery and reference; publicapis.io is better when you need a structured UI or a programmatic endpoint.

Why would I use FreeAPI.watch instead of the GitHub list?

Because the GitHub list doesn't tell you which APIs actually work today. Roughly a third of entries on the most-starred public-apis lists have broken or moved to paid since they were added. FreeAPI.watch verifies each API hourly, tracks 30-day uptime, surfaces a 'graveyard' of APIs that died or went paid, and ranks active APIs by a composite of uptime, speed, and free-tier friction. For verification before integration, it's the more useful tool — but the GitHub list still wins on raw discovery breadth.

Are these three directories competitors?

Not really. They solve overlapping but distinct problems. The GitHub repo is a community discovery list. publicapis.io is a searchable web frontend. FreeAPI.watch is a verification and reliability layer with live monitoring and comparison content. A serious developer building on a free API today might use all three: discover on GitHub, browse on publicapis.io, verify on FreeAPI.watch.

What about generic API monitors like StatusGator or IsDown?

Those are different products. StatusGator and IsDown monitor any service or URL you point them at — they don't curate, don't categorize by free-tier quality, and don't maintain a directory of which APIs are free in the first place. They're complementary if you've already chosen an API and want alerts when it goes down. For deciding which free API to use in the first place, a curated directory is the right starting point.

Free Public API Directories Compared: Which One to Use in 2026

May 17, 2026 · analysis

An honest comparison of public-apis on GitHub, publicapis.io, and FreeAPI.watch. Different tools for different jobs.

There are three meaningful free-API directories in 2026: public-apis on GitHub (350k+ stars, the original), publicapis.io (the polished web frontend), and FreeAPI.watch (this site — adds live monitoring and reliability ranking). They overlap on catalog but differ sharply on what they actually do for you.

I'll be straight: I run FreeAPI.watch. I'll still try to give you an honest read on when each is the right tool, because telling you to use a worse option for your specific need would be the fastest way to lose your trust.

public-apis on GitHub: The Discovery Source

The public-apis GitHub repo is the canonical community-maintained list of free APIs. ~350,000 stars, organized by category, contributed via pull requests by anyone. It's where most downstream directories — including this one — start when building their seed catalog.

Strengths: enormous breadth (hundreds of APIs across 50+ categories), strong domain authority for SEO purposes (Google trusts it implicitly), and community-driven additions mean new APIs get added quickly when developers discover them.

Weaknesses: static markdown. Once an API is added, nothing verifies it stays alive. Free tiers get quietly removed, domains lapse, projects shut down — and the entry stays in the list. The maintenance burden has been visible at times (PRs pile up; entries go stale). For discovery, this is fine. For 'should I actually build on this API right now?', it's misleading.

Use it when: you need to discover what exists in a category. You're brainstorming. You want raw catalog breadth before you filter.

publicapis.io and publicapi.dev: The Searchable Web Frontends

publicapis.io (and the related publicapi.dev) are clean web frontends over a similar catalog. They add search, category filtering, and in publicapis.io's case a JSON API endpoint that returns the same data programmatically.

Strengths: better UX than scrolling a markdown file. Search works. Categories are browsable. The JSON API at publicapis.io/api lets you build on the catalog without scraping markdown.

Weaknesses: the catalog is mostly the same as the GitHub list, which means the same staleness problem. No live status verification. No quality scoring beyond category membership. No graveyard tracking of APIs that died — they're often still listed as if alive. The free-tier description is whatever was written when the entry was added, which is often years ago.

Use them when: you want a quick UI-based browse without leaving the browser, or you need a JSON catalog endpoint and don't care about freshness.

FreeAPI.watch: The Verification Layer

FreeAPI.watch is what I built when the staleness problem cost me hours one too many times. The catalog is smaller (77 APIs across 5 categories versus the GitHub list's 200+ across 50+) because every entry has to be hand-curated against current docs and tracked via hourly pings.

What it adds on top of the existing directories: hourly HTTP checks against each API's documented health endpoint, 30-day rollup uptime, latest response-time measurement, a composite ranking score that combines reliability with free-tier friction (no-key scores higher than credit-card-required), a 'graveyard' page tracking APIs that died or went paid with replacement suggestions, side-by-side comparison pages for popular API pairs, and a public JSON API at /api/v1/ for programmatic consumption.

Trade-off: the catalog is deliberately smaller. If your category isn't one of the five we cover (weather, news, finance, geocoding, cryptocurrency), the GitHub list will have more entries than we do. That's a real limitation, not a marketing concession.

Use it when: you're about to integrate a free API and want to know whether it's actually alive, what its real free-tier is in 2026, and what alternatives exist if it's flaky.

Side-by-Side: What Each Directory Actually Provides

Catalog breadth: GitHub list > publicapis.io > FreeAPI.watch (we're the smallest)
Catalog freshness: FreeAPI.watch (hourly) > publicapis.io (varies) > GitHub list (stale)
Live status verification: only FreeAPI.watch
Graveyard/discontinued tracking: only FreeAPI.watch
Free-tier quality scoring: only FreeAPI.watch
JSON API: FreeAPI.watch (/api/v1/) and publicapis.io
SEO/domain authority: GitHub list (massive) > publicapis.io (established) > FreeAPI.watch (new)
Comparison/decision content: only FreeAPI.watch (30 head-to-head pages)
Community PRs: GitHub list > FreeAPI.watch (we accept seed contributions via /contact) > publicapis.io

When to Use Which (Decision Guide)

Use the GitHub public-apis repo when you're at the discovery stage: 'are there any free APIs for [X]?' Browse the category. Get a sense of what exists. Don't trust the metadata is current; treat it as a starting list of names to investigate.

Use publicapis.io when you want a programmatic catalog endpoint or a search UI and don't need verification. Their JSON endpoint is convenient for building a 'directory of directories' app or a personal API explorer.

Use FreeAPI.watch when you're past discovery and about to commit. You've narrowed down to a few candidates and need to know: is this one alive right now? Is the free tier real in 2026? Is there a more reliable alternative? Pull up /[slug] for each candidate, read the live status, check the 30-day uptime, look at the alternatives section. We cover five categories deeply; if yours isn't one of them, fall back to the GitHub list for verification (manual: actually curl the endpoints before integrating).

Use a generic monitor like StatusGator or IsDown after you've chosen your API, when you need alerts on outages of the specific services your production app depends on. These don't replace a directory — they monitor what you already use.

What We Don't Do (And Won't)

FreeAPI.watch is not trying to replace the GitHub list — the discovery problem is solved there, and re-doing it would just fragment community contributions. We're a verification and reliability layer on top of the existing catalog landscape.

We're also not trying to be a generic uptime monitor. If you want to monitor your own internal APIs, your customer's services, or arbitrary URLs, StatusGator, Pingdom, UptimeRobot, and Checkly are all better suited. Their feature sets (multi-region, custom alerting, status pages) are specifically for that use case.

What we do is narrow: take the universe of free public APIs that hackathon hackers, indie developers, and prototype builders are likely to reach for, monitor them seriously, and surface the data in a way that answers 'should I use this one?' faster than reading docs and curl-ing endpoints manually.

The Honest Recommendation

For a developer building today: bookmark the GitHub repo for discovery, bookmark FreeAPI.watch for verification before integration, and skip publicapis.io unless you specifically need its JSON catalog endpoint. The two tools serve sequential parts of the same workflow — discover, then verify.

If you're maintaining a side project that uses free APIs, also subscribe to our changelog RSS (/rss.xml) or check /changelog periodically. APIs die, and being the last to know is expensive.

If your category isn't covered here yet — APIs for transportation, games, government, ML, or anything outside weather/news/finance/geocoding/crypto — the GitHub list remains your best starting point. We may expand into more categories based on demand; suggest one via /contact.