Public APIs: the collective list of free APIs
Public APIs is a MIT-licensed community list of free APIs across dozens of categories, with 494,667 GitHub stars and 55,209 forks, making it a long-running reference.
TL;DR: Public APIs is a collective list of free APIs, and after ten years it is still the fastest way to find a free endpoint for a side project. It is MIT licensed, holds 494,667 stars and 55,209 forks, and it gained roughly 324 stars in today’s trending window. The categories cover weather, finance, geography, machine learning, entertainment and dozens more, and the repository’s homepage points to the APILayer service that maintains it.
What it is
The description is four words: “A collective list of free APIs”. That is the entire pitch, and it is the right one.
The repository was created in March 2016, which makes it one of the longest-running curated lists in the open source ecosystem. It has survived multiple waves of API marketplaces, several API directories that came and went, and the shift away from free developer tiers that happened across the industry.
The topic list is api, apis, dataset, development and free. The dataset tag is the one that understates it. Most people treat this as a reference list, but the raw material is structured enough to use as a dataset, which is how you would approach it if you wanted to answer a question about the API economy rather than find one endpoint.
Why the fork count is enormous
55,209 forks is unusual for a list of links. Most people do not fork a README of links.
The likely explanation is that people fork it to keep a personal copy, prune it, or turn it into their own list with a different structure. Some fork it to migrate to a private tracker or a spreadsheet. A sizeable share probably fork it as a test repository, since it is a well-known and completely safe target for practicing git workflows.
Whatever the reason, the fork number is a good proxy for how much people rely on it. This is not a list people bookmark once and forget. It is a list people fork.
What you will find in it
The structure is a set of category files, each holding a list of API entries with the name, a short description, and a link. The categories that get used most often in practice tend to be the boring ones.
| Category type | Typical use |
|---|---|
| Weather and environment | Current conditions and forecasts for a location |
| Finance and currency | Exchange rates, market data, crypto prices |
| Geolocation and maps | Coordinates, geocoding, places, directions |
| Machine learning | Image and text recognition, translation, embeddings |
| Entertainment and media | Comics, movies, music, books, quotes |
| Communication and messaging | SMS, email, chat, translation |
Two things to keep in mind when you pull from it. Most of these are free tiers, not free products, and the free tiers change without notice. And a listed API is not a guarantee that the endpoint still responds. Check the API itself before you design around it.
How to try it
Clone it and read the categories directly:
git clone https://github.com/public-apis/public-apis.git
cd public-apis
ls
The default branch is master rather than main, which is a small sign of the repository’s age.
If you want to query it as data rather than read it, the category files are plain text and easy to parse:
# List every API named in the weather category
grep -E '^- API:' src/categories/weather.md
The homepage listed in the repository metadata is an APILayer referral link, so the project is maintained alongside a commercial API gateway. That does not affect the list itself, which is MIT licensed and community contributed, but it is worth knowing when you read the README.
When to use it
Use it when you need a free endpoint for a prototype and you do not want to spend an afternoon searching for one. It is the fastest path from “I need geocoding” to a working request.
Skip it when you are building something with a real SLA. Free tiers with no commitment are exactly the endpoints that change their terms. For production, treat this list as a starting point for research, then pick a provider with an actual contract behind it.
Source and Accuracy Notes
- Project page: https://github.com/public-apis/public-apis
- Source repository: public-apis/public-apis (verified via GitHub API
html_url) - License: MIT (verified via GitHub API
license.spdx_id) - Stars at time of writing: 494667
- Homepage listed in repository metadata: https://APILayer.com/?utm_source=Github&utm_medium=Referral&utm_campaign=Public-apis-repo
- Repository created: 2016-03-20, default branch
master
Related Posts
dev-tools
Automotive Skills Suite for AI Engineering
Evaluate Automotive Skills Suite for APQP, ASPICE, HARA, safety-plan, and DIA workflows with setup notes, governance risks, and SME review guidance.
5/28/2026
dev-tools
awesome-agentic-ai-zh Roadmap Guide
Explore awesome-agentic-ai-zh as a Chinese agentic AI learning roadmap, with setup notes, track selection, study workflow, and evaluation guidance.
5/28/2026
dev-tools
Baguette iOS Simulator Automation Guide
Set up Baguette for iOS Simulator automation, web dashboards, device farms, gesture input, streaming, and camera testing with Xcode caveats.
5/28/2026