A collective list of free APIs
| Rating | Summary | |
|---|---|---|
| Quality | decent (13/24) | Actively updated reference resource with exceptional adoption, but carries no releases, no test infrastructure, and no executable software — scoring reflects what it actually is rather than what it isn't. |
| PAI Relevance | watch (0.38) | Not an executable or installable tool; fills a limited gap as a structured API catalog when PAI agents need to identify integration-ready external APIs, but the Research skill already covers on-demand discovery. |
The prior landscape rough-placement scored this as poor (4.6/24) / note — the formal appraisal revises both upward once probe-level evidence is applied. The WATCH verdict is formula-driven (standalone 13 ≥ 12); the low composite (0.38) accurately signals low PAI integration value.
13/24 — maintained / under-documented / early-or-minimal
Failed:
.github/ directory for assets but contains no CI badge and no explicit reference to .github/workflows/Passed:
Failed:
Passed:
Failed:
Passed:
| Dimension | Score | Assessment |
|---|---|---|
| Harvest Value | 0 | The repo is a curated text list with no architectural pattern, algorithm, or system design that could be studied and applied to any PAI subsystem. Nothing novel to harvest. |
| Integration Readiness | 0 | Python validation scripts only; no installable package, no CLI, no bun add path. The companion JSON API (davemachado/public-api) is a separate repo not appraised here. This repo itself produces no machine-consumable output. |
| Overlap Risk | 0 | No existing PAI skill or tool covers a structured, pre-curated API directory. The Research skill does web investigation but does not maintain a browsable API catalog — this is functionally distinct. |
| Gap Fill | 1 | PAI agents currently have no structured reference for discovering available free APIs by domain when building new integrations. This fills that gap as a passive reference, even if imperfect given its non-executable nature. |
Composite: 0.38
When prototyping any feature that needs external data (images, geolocation, museum records, color palettes): Before signing up for a paid API, search public-apis' markdown tables filtered by the relevant category — the auth/HTTPS/CORS columns immediately surface which options work without a key or server proxy. This compresses API discovery from an hour of scattered Googling to a two-minute table scan.
Monitor for a machine-readable export: The repo is currently markdown-only, which limits automated use. Watch the Issues tab and forks for any stabilized JSON/YAML export of the dataset (several forks attempt this). If a maintained structured version emerges, it becomes worth building a lightweight "find free API for capability X" lookup — but that investment is premature until the format is stable and actively maintained alongside the main repo.
Bookmark for re-evaluation in 6 months: The repo's value as a discovery reference is high but its PAI fit is low because it requires human browsing rather than programmatic consumption. Revisit if the maintainers add rate-limit, uptime, or pricing-tier metadata to each entry — that would shift it from a human-readable list into a dataset worth querying during feature planning.
Category: Education & Reference
In this category: first entry — no prior repos formally assigned to education-reference. Note: codecrafters-io--build-your-own-x and practical-tutorials--project-based-learning appear in uncategorized landscape subsections and would logically share this category on formal appraisal.
Standing: Unchallenged as the canonical API discovery reference; at 437k stars it occupies a category of one in terms of adoption scale.
Density: 8/10 — Available: full repo metadata (stars, forks, issues, dates, license, topics, language), README first 8KB including index and sample entries, topic tags. Missing: dependency manifest, CI workflow config, full README beyond 8KB, CONTRIBUTING.md content, test file structure.
The rough landscape pre-score (4.6/24 / note) underweighted health and adoption signals. Once probe-level scoring is applied, the repo resolves to decent — a healthy, actively-maintained reference artifact with exceptional social proof but limited engineering infrastructure appropriate to its nature as a curated list. The WATCH verdict is appropriate: this is worth a PAI agent being aware of as a lookup resource, but it warrants no integration effort.