A collective list of free APIs
Started in March 2016 and continuously maintained for a decade, this is a stable, mature community resource rather than versioned software. There are no formal releases — the repo functions as a living document updated by community PRs. With only 7 open issues against 47K+ forks, triage is extremely tight. The absence of a release cadence is appropriate for a curated list, not a weakness. The APILayer commercial sponsorship provides structural continuity alongside community contributions.
The README is exemplary for its purpose: a full index of 50+ categories, tabular entries for every API showing name, description, auth type, HTTPS support, and CORS status, plus a Contributing Guide, issue/PR links, and Discord community pointer. There is also a separate programmatic API (github.com/davemachado/public-api) for machine access. Navigation and onboarding friction are essentially zero.
The Python layer handles link validation and list integrity checking — tooling that supports the curation process rather than delivering end-user functionality. No dependency manifest is available, suggesting a lean, low-risk dependency footprint. The validation scripts enforce structural consistency across thousands of entries. CI is implied by the low open-issue count and high contributor volume. No test suite is visible in the README surface, which prevents a perfect score.
Last commit was 2026-05-11 — one day before this appraisal. Commit cadence is near-daily when averaged across months. The hybrid model of paid APILayer staff plus open-source community contributors creates resilient maintenance. Seven open issues at this scale is exceptional and signals active, rapid triage.
434,210 stars places this among the top ~10 most-starred repositories on all of GitHub. 47,547 forks indicate pervasive downstream use. It is the canonical reference for free-API discovery across the developer community, cited in countless tutorials, courses, and toolchains. Community gravity is self-reinforcing.
Overall: 4.6/5
Category: Public API Directory Known alternatives in vault: None — no repo in the current vault occupies this category. Differentiation: This repo is the definitive community-maintained index of free public APIs, spanning 50+ domains with structured metadata (auth, HTTPS, CORS) per entry. Its scale (thousands of APIs), longevity (10 years), and machine-readable companion API have no equivalent in the vault. The vault currently focuses on AI agent infrastructure, personal knowledge management, CLI tooling, and agent engineering — all categories that are consumers of APIs, not cataloguers of them. Gap or crowd: Clear gap. This introduces an entirely new category to the vault. Nothing in the existing 18 repos serves API discovery or acts as a structured reference dataset of external integrations.
Score: 3/5 Harvestable: The dataset itself — structured API entries with category, auth type, HTTPS/CORS flags — is directly harvestable as a knowledge base or lookup table. The 50+ category taxonomy could also inform PAI skill/tool organization. The Python validation scripts offer a pattern for link-health monitoring of any curated list maintained in the vault. Integration path: Two viable paths: (1) Passive reference — an AI agent queries the dataset (via the davemachado public-api companion) to discover candidate APIs when building new skills or tools. (2) Active import — periodically sync a subset of the list (e.g., AI/ML, Development, Security categories) into the vault's knowledge store for offline lookup. The companion REST API makes programmatic access trivial. Overlap with existing: No overlap. No existing vault repo catalogues external APIs or provides API discovery functionality. Adoption cost: Trivial as a reference resource — point an agent at the companion API or the raw README. Moderate if building a synced, queryable local index with staleness detection and category filtering.
This is a reference-class asset rather than an infrastructure component. Its PAI fit score of 3 reflects genuine utility (API discovery accelerates skill-building, reduces research time for integration tasks) tempered by the fact that it is passive data rather than active tooling — it does not run, emit events, or plug into a pipeline without a wrapper. The value proposition for a PAI system is as a lookup layer: when an agent needs to add a capability (e.g., weather data, geocoding, financial quotes), querying this index first surfaces vetted, free options before reaching for paid or custom solutions. The companion API (davemachado/public-api) is the integration surface to prioritize over raw README parsing.