Over 461K Stars: The Ultimate Open‑Source Catalog of 1,400+ Free APIs Covering Most Development Scenarios

Project Overview

The public‑apis repository is a community‑maintained open‑source “free API encyclopedia” that aggregates publicly available APIs with free usage or free tier limits. It is jointly maintained by community contributors and the APILayer team, and has accumulated more than 461 K stars on GitHub.

Core Metadata

Each API entry lists three essential attributes:

Auth : Indicates whether the API requires a key (No / apiKey / OAuth).

HTTPS : Shows whether the endpoint supports encrypted requests, a prerequisite for production use.

CORS : States whether the API can be called directly from a browser, helping developers avoid cross‑origin errors.

Scale and Visual Search

The catalog contains over 1,400 endpoints spread across 45 categories. A companion visual search site ( publicapis.dev) provides a searchable UI that eliminates the need to read the long README manually.

Category Coverage

High‑frequency categories include:

🐱 Animals : cat/dog images, pet databases, animal trivia.

🎨 Art & Design : illustration libraries, color palettes, font resources.

💰 Finance : stock quotes, currency exchange, cryptocurrency prices.

🌤 Weather : real‑time weather, air quality, forecasts.

🍔 Food : recipes, cocktail formulas, food data.

📰 News : global headlines, RSS aggregators.

🎮 Games : game databases, player stats, achievement info.

👽 Anime : series info, character data, subtitles.

✈️ Transportation : flight status, traffic, charging stations, subway data.

🧠 Machine Learning : AI models, image recognition, NLP text processing.

📖 Books : ISBN lookup, open libraries, poetry collections.

🧪 Test Data : mock users, mock articles, todo lists.

🤪 Fun & Entertainment : jokes, motivational quotes, quirky anecdotes.

Practical Scenarios

Typical high‑frequency use cases are illustrated as an ordered list:

Weather widget – Weatherstack or OpenWeatherMap (requires an apiKey).

Humorous quote mini‑app – icanhazdadjoke, Advice Slip (no key required).

Front‑end mock data – JSONPlaceholder + RandomUser (generates users, posts, todos).

Currency converter – exchangerate.host (some endpoints are key‑free).

Cat‑image gallery – TheCatAPI (large collection of animal pictures).

Personal homepage assets – NASA’s “Astronomy Picture of the Day” + Pexels free image library.

Code Example (Python)

import requests
API_KEY = "your_api_key"
city = "Beijing"
url = f"https://api.openweathermap.org/data/2.5/weather?q={city}&appid={API_KEY}&units=metric"
resp = requests.get(url)
print(resp.json())

Note: The OpenWeatherMap endpoint requires registration for an apiKey and is subject to free‑tier rate limits.

Known Limitations

Rate‑limit constraints : Most free APIs impose per‑minute or daily request caps; sufficient for demos but may require paid plans for high‑traffic production.

Stability variance : Some endpoints are maintained by individual contributors and can become unavailable when abandoned. The community periodically removes dead entries, but real‑time guarantees are absent.

Data quality ceiling : Free APIs often have lower accuracy or completeness compared to commercial alternatives; they are best suited for prototyping, not core business logic.

CORS pitfalls : Interfaces marked CORS: No will trigger browser cross‑origin errors and must be accessed via a backend proxy or server‑side script.

HTTPS requirement : Production projects should avoid HTTP‑only endpoints to prevent man‑in‑the‑middle attacks.

Practical Tips

Check the free quota of apiKey ‑based APIs before launch to avoid unexpected throttling.

Cache responses from unstable APIs to reduce repeated calls.

Use the repository’s Discord community for faster issue resolution than opening a GitHub issue.

Contribute fixes or new entries via pull requests; the project maintains high community activity.

Role‑Based Recommendations

Front‑end developers / personal demos : Prefer APIs with Auth: No, HTTPS: Yes, and CORS: Yes to enable direct browser fetches without a backend.

Back‑end, crawlers, side‑projects : Authentication is less critical; focus on data quality and stability. APILayer series, CoinGecko, OpenStreetMap, etc., are suitable, but implement rate‑limit handling and caching.

Students / graduation projects : Choose no‑auth APIs to skip registration and accelerate prototype development.

Independent developers / side‑businesses : Prioritize APILayer ecosystem APIs, which offer generous free tiers and better documentation; avoid relying on free public APIs for core business features.

Conclusion

In the AI‑driven era, public‑apis serves as a ready‑made “building‑block” library. By reusing these free endpoints and combining them with AI‑generated glue code, developers can assemble functional products over a weekend without reinventing the wheel.