API-mega-list: A Directory of 11,860 API Listings, and What That Number Conceals
This GitHub repo is a powerhouse collection of APIs you can start using immediately to build everything from simple automations to full-scale applications. One of the most valuable API lists on GitHub—period. 💪
At a glance
- What is it?
- cporter202/API-mega-list is a JavaScript repository that organises thousands of third-party API listings into 24 categories. It is a discovery index, not a client library, and the README's claim that each API is production-ready cannot be verified from the repository.
- Who is it for?
- Adopt API-mega-list as a starting point for finding a data source, not as a dependency. It suits developers who need to locate a scraping or automation endpoint and are willing to verify the vendor's own terms, pricing and rate limits before writing code.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 26 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- cporter202/API-mega-list8,392 ★ · +782
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| cporter202/API-mega-list | 7.6k | 8.4k |
782 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The problem is discovery, not integration
Finding a working API for a narrow task is slower than it should be. Search engines return vendor marketing pages, and general awesome-lists go stale because nobody owns the entries. API-mega-list attacks that problem by concentrating listings into one repository with a fixed category structure. The README describes it as a collection you can "start using immediately to build everything from simple automations to full-scale applications". The intended reader is a developer who already knows what data they want and needs a shortlist of endpoints that supply it: social posts, property listings, job ads, price data. The repository does not wrap those endpoints in code. It points at them. That distinction matters, because everything the README claims about production readiness is a claim about the third-party services, not about anything in this repository.
How the repository is laid out on disk
The structure is directory-per-category, with the count baked into the folder name. The README links to paths such as ./agents-apis-623/, ./automation-apis-5653/, ./lead-generation-apis-4431/ and ./social-media-apis-2786/. The number in the path is the advertised size of that category, which means a category that grows requires either a rename or a mismatch between the folder name and its contents. The README also links a 00-featured-apis/ directory under Featured APIs, and its sponsored banner promotes APIMesa. A separate SPONSORED_PARTNERS.md file sits at the top level of the repository. That file is the one to read before treating any ordering in the list as neutral. The primary language is JavaScript, but the language label likely reflects tooling or scripts used to assemble the listings rather than a library consumers import.
The listings are Apify endpoints with affiliate parameters
The visible table rows follow a consistent shape: a name, a price hint, and a link. The Agents table shows entries like "Youtube Transcript Scraper - $0.5 per 1k" pointing at apify.com, and "Tweets / X - Scraper" pointing at apify.com/mikolabs/x-scraper. Every one of those URLs carries the query parameter fpr=p2hrc6. That pattern indicates referral tracking on outbound links, which is consistent with the README's own framing of 200 sponsored partner listings alongside 11,860 core directory APIs. None of this is hidden, but it does mean the directory has a commercial interest in which links you click. Treat the ordering within a category as editorial and paid placement mixed together, not as a ranking.
What the README claims that the material does not support
Two claims deserve scepticism. The first is "Each API is production-ready - simply integrate it into your application and start building." Nothing in the repository can establish that. Production readiness depends on the vendor's uptime, rate limits, authentication model and terms of service, none of which are visible in a listing row. The second is the headline "The most comprehensive collection of APIs on GitHub". That is a marketing assertion. The category counts also overlap heavily: Automation at 5,653, Lead Generation at 4,431 and Developer Tools at 4,065 cannot be disjoint sets if a single scraping endpoint plausibly belongs to all three. The 11,860 figure is therefore a count of listings, not of distinct services. Read it as catalogue size, not coverage.
There is no installation step, and that is the point
There is no package to install. Consumption happens through the repository itself: open the category directory, read the table, follow the link, then sign up with the vendor and read their documentation. The only configuration surface visible in the README is the referral parameter appended to outbound URLs, which you would strip or keep depending on whether you want to credit the maintainer. The README gives a Last Updated date of 2026-07-23, although the repository's last push is dated 2026-10-20. If you fork the repository, you inherit the maintenance burden of keeping the catalogue current.
The licensing gap is the largest unresolved risk
The repository's licence is listed as unknown. That is a real constraint, not a formality: without a stated licence, the default position under most copyright regimes is that no reuse rights are granted, which affects anyone who wants to mirror the catalogue, republish the tables, or fold the listings into a commercial product. The individual APIs listed carry their own terms, which are entirely separate and generally require an account. If your use case depends on redistributing the list itself, resolve the licence question before you build on it. This is not legal advice.
Public-apis and awesome-lists take the opposite approach
The obvious comparison is the public-apis project and the broader awesome-list ecosystem. Those directories are community-curated through pull requests, and their inclusion criteria usually require an API to be free or have a free tier, with entries reviewed before merge. API-mega-list inverts that: it accepts paid endpoints, shows prices in the listing text ("$0.5 per 1k"), and mixes sponsored placements into the same tables as unpaid entries. The trade-off is coverage against neutrality. A community list gives you fewer entries and a clearer signal about why each one is there. This repository gives you far more entries and no per-row signal about whether a listing is there because it is good or because it is paid. If you want a small set of vetted free APIs, the community model serves you better. If you want to know whether an endpoint exists at all for a niche data source, breadth wins.
Who should use this, and what to check first
Use it when you are scoping a data problem and need to know what vendors exist in a category such as real estate, jobs or social media. Do not use it as a dependency in a build pipeline, and do not treat the listing text as a specification. Before you write integration code against any entry, check three things in the repository itself: whether a licence has been added since this review, what SPONSORED_PARTNERS.md says about how placements are marked, and whether the category folder name still matches the count the README advertises. Then check the vendor's own pricing and terms, because the price shown in a listing row is a starting figure, not a contract. The repository is a map. The territory is entirely on someone else's servers.
Editorial conclusion
Adopt API-mega-list as a starting point for finding a data source, not as a dependency. It suits developers who need to locate a scraping or automation endpoint and are willing to verify the vendor's own terms, pricing and rate limits before writing code. It is the wrong tool if you need a maintained client library, a guaranteed uptime figure, or a licence you can trace: the repository states no licence, and most listed endpoints sit behind third-party accounts. Verify the licence file, the sponsored placement policy in SPONSORED_PARTNERS.md, and the specific listing you intend to call before you commit.
Frequently asked questions
How is the API Mega List organised?
Into one directory per category, each named with its own entry count, such as agents-apis-623 or ai-apis-1555, plus a featured folder for sponsored partners. The readme table of contents, the per-category headings and the directory names all carry the same counts, so the repository duplicates the numbers three ways.
Are the APIs in the API Mega List free?
Not uniformly. Several entries are marketplace listings described with unit prices, such as a YouTube transcript scraper at half a dollar per thousand, and many links carry a referral parameter. The readme states each API is production-ready, which is a claim about the vendor's offering rather than a test of the endpoint.
How many categories and APIs are in the API Mega List?
The statistics table states 24 categories, 11,860 core directory APIs and 200 sponsored partner listings, last updated 23 July 2026. The category table lists 23 core categories whose counts sum to roughly 30,000, which does not reconcile with the stated API total.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/cporter202-api-mega-list)Star history chart for your README
[](https://hysenlabs.com/projects/cporter202-api-mega-list)Was this useful?