public-apis/public-apis is a Markdown directory for finding third-party APIs, with authentication, HTTPS and CORS metadata to narrow a shortlist. Use it when choosing data for a prototype or teaching HTTP. Choose another approach for guaranteed availability, provider support or predictable test fixtures. The directory identifies candidates; the selected provider supplies the service, credentials, terms and response behavior your application depends on.
What people use public-apis for
Attilio81 documents a directory index for an MCP server, AndersRod links the repository in a workshop, and the author of issue #303 reports recurring reference use. These examples cover automated discovery, teaching and manual lookup. They describe identifiable uses rather than estimating adoption from stars or promotional inventory totals, which vary across the supplied accounts.
- Attilio81's MCP_PUBLIC_APIS documentation describes an index that an LLM can query by category, authentication, HTTPS, CORS and keyword.
- AndersRod's Rhino Grasshopper workshop includes public-apis as an additional API resource alongside exercises using public data and visualization.
- The author of issue #303 reports referring to the list frequently and offers to add CORS information.
- Contributor eduanmoldeep's broken-link discussion records checking a recovered service and updating its status table. The supplied synthesis also records cleanup PR #1650.
On r/webdev, _fat_santa recommended the list to someone seeking data for a side project. That recommendation fits the discovery use above: start with a subject or an idea, then find services worth investigating. It is a personal account of usefulness, rather than a measurement of provider reliability or a comparative evaluation of the directory. Reddit side-project recommendation
What you can do with public-apis
The directory groups API candidates by subject and exposes authentication, HTTPS and CORS information before you open provider documentation. Begin with the category matching your data need, then eliminate authentication models that conflict with your project. For a classroom exercise, for example, a credential requirement changes the preparation students need before they can make a request. Directory description
Kelvin Kariuki's walkthrough describes authentication values including no authentication, API keys and OAuth. HTTPS and CORS have separate columns: one concerns encrypted transport, while the other concerns browser access across origins. Read the three columns independently. An API-key requirement does not answer the browser-access question, and HTTPS support does not tell you whether the provider permits your intended use. Catalog-column walkthrough
For each shortlisted service, record its documented endpoint, request method, credential requirements, allowance and permitted use. Save an actual response when evaluating the integration, including an error response relevant to the application. If the catalog state matters to the decision, retain its commit identifier alongside that provider record. These are recommended selection steps, not steps completed in our supplied lab attempts.
What happened when we ran it
Our run at commit 8870667 stopped before installation, build or tests on November 11, 2026. The sandbox reported no supported ecosystem for its Python classification and no Dockerfile. Its recorded configuration was 3 CPUs and 8 GB RAM, with no image specified. These figures describe the sandbox attempt, rather than hardware requirements for reading a Markdown directory.
| Recorded stage | Result | What it means |
|---|---|---|
| November 11 sandbox, commit 8870667 | Not run: no supported ecosystem, language Python; no Dockerfile | The harness stopped before installation, build or tests |
| November 17 hands-on safety step | FAILED: none of compose.yaml, compose.yml, docker-compose.yaml or docker-compose.yml exists | The runner's required Compose path was blocked |
| November 17 teardown | ok | The teardown step recorded successful cleanup |
The November 17 safety step failed because the runner required a Compose file and found none of its accepted filenames. Its phrase "unsafe repo" is the runner's rule label. The separate run header says the project was deployed with its own Docker Compose and every port bound to 127.0.0.1. The explicit failed step supplies the recorded execution outcome.
The teardown record says "teardown: ok". Together, the records show a stopped sandbox path, a failed Compose requirement and a successful cleanup record. They support reporting those stages individually rather than describing a working deployment. Ordinary catalog browsing follows a different path: opening the README and its provider links.
Where people get stuck: links, browser access and contribution control
Issue #1590 records broken and recovered services, while issue #303 distinguishes API endpoints from website links when checking CORS. A documentation page returning successfully answers a different question from whether browser JavaScript can read an API response. The issue history also records search and contribution problems, including a growing Markdown list and maintainers lacking settings access.
| Problem in the records | Practical response | Recorded outcome |
|---|---|---|
| Broken and recovered directory links, #1590 | Recheck the provider before changing its row | eduanmoldeep reported checking a recovered service and updating the table; the synthesis records PR #1650 |
| Browser-access uncertainty, #303 | Inspect the actual API response and its headers | A commenter proposed checking Access-Control-Allow-Origin; PR #589 later added the CORS column |
| Difficult Markdown search, #203 | Use category search or inspect a separate index | Participants proposed static hosting, JSON and a client-side search library |
| Contributor backlog and restricted settings access, #1268 | Identify who can review, merge and add maintainers | yannbertrand reported lacking settings access; #3104 later reported clearing an earlier backlog |
In issue #303, a commenter proposes requesting actual API URLs and inspecting Access-Control-Allow-Origin. Other participants discuss the work involved when endpoints require accounts or credentials. The primary thread records PR #589 merging to add the CORS column on January 15, 2018, after the original request and discussion about how to populate it.
In issue #1590, eduanmoldeep reports checking a service after another contributor says it is up again. The status table includes removed, unavailable and working services. For a cleanup contribution, retain the checked URL and date so reviewers can distinguish the reported failure from a subsequent recovery rather than treating either observation as permanent.
The supplied Dropout Developer guide explains browser CORS errors through an illustrative fetch request. It recommends a server-side proxy and says an opaque response cannot provide readable JSON. Its example explains why changing a request to no-cors does not provide the application with the response data it needs. Browser-access guide
Maintenance activity and the access dispute
GitHub records a push on November 15, 2026, and the issue history contains named maintainer reports about restricted access. The push is dated evidence of repository editing. The reports concern authority to change settings, create repositories and add maintainers, which matters to contributors proposing work beyond a catalog-row edit. Repository metadata
On March 17, 2022, matheusfelipeog identified APILayer as the owner and described unsuccessful attempts to obtain help with project improvements. The account also says maintainers' access levels had been lowered. In issue #1268, yannbertrand reported being unable to add maintainers and corrected the assumption that Todd Motto still owned the project. Maintainer-access account
matheusfelipeog reported resolving an earlier backlog of pull requests and issues in about two months. The primary thread shows issue #3104 closing on July 15, 2026, followed by Jamim asking whether the situation had improved. Contributors considering a substantial change should inspect reviews of comparable work and identify the people who can accept it. Issue #3104 and its later discussion
Security, pricing and data rights
GitHub identifies the repository license as MIT; the listed providers set their own service terms. Repository reuse and permission to use an API's data are separate checks. Keep the selected provider's allowance, commercial-use conditions and redistribution rules with the integration record, especially when a prototype becomes an application used by other people. Repository license metadata, provider-terms discussion
The supplied README opens with an APILayer suite promotion and includes an APILayer product table. That is commercial presentation within the repository page. Its descriptions can identify offerings to investigate, but they provide no common purchasing rubric across competing services. Read the advertised products as provider offerings alongside the catalog's discovery role. Supplied upstream README
Search wrappers retrieve the catalog differently
Attilio81's MCP_PUBLIC_APIS documentation describes filtering a directory index by category, authentication, HTTPS, CORS and keyword. The wrapper is a separate project, with its own installation and running instructions. Its documented index-refresh tool downloads the README again and rebuilds the index. Those instructions belong to MCP_PUBLIC_APIS, rather than to ordinary use of public-apis/public-apis. MCP_PUBLIC_APIS documentation
A metadata query can produce a narrower candidate list without becoming a provider ranking. When retaining an automated recommendation, save the source row and catalog revision with the result. This recommendation follows the same selection workflow as manual browsing: it makes the recorded reasons for including a service available to the person evaluating the eventual dependency.
public-apis vs alternatives
Use public-apis/public-apis for category browsing and APIs.guru for machine-readable specifications; the earlier MrKeyoor review points to Postman for request collections. The community-recommended alternative addresses another decision: where to inspect a contribution path after the original repository's access dispute. These choices concern different tasks, so the evidence supports a task-based comparison rather than an overall winner.
| Option | What the evidence supports | Choose it when |
|---|---|---|
| public-apis/public-apis | Category browsing with authentication, HTTPS and CORS metadata | You want a cross-provider shortlist |
| public-apis-dev/public-apis, resolving to marcelscruz/public-apis | An alternative recommended in issue #3484; the supplied GitHub response identifies its destination | You want to inspect another contribution path |
| APIs.guru OpenAPI Directory | OpenAPI definitions with REST access to the collection | Your tooling consumes machine-readable specifications |
| Postman Public API Network | The earlier MrKeyoor review describes published workspaces and runnable API collections | You want to inspect request examples inside an API client |
APIs.guru documents OpenAPI 2.0 and 3.x definitions and REST access to its collection. Its primary documentation recommends the REST API for integrations because repository structure may change. The supplied metadata for the community recommendation identifies marcelscruz/public-apis as the destination of public-apis-dev/public-apis. APIs.guru primary documentation, alternative destination metadata, recommendation discussion, earlier Postman comparison
For deterministic tests, the earlier Hysenlabs review recommends local mocks or recorded fixtures. That approach puts the expected response into the test environment rather than obtaining live data from a remote provider. Choose the directory for discovering external services and fixtures for controlling test inputs. Hysenlabs fixture comparison
What the other reviews get wrong
Hysenlabs' statement that the list does not tell readers whether an API needs a key conflicts with the documented Auth column. Kelvin Kariuki's walkthrough describes no authentication, API keys and OAuth among its values. The correction is to use the recorded authentication field during selection, then read the chosen provider's credential instructions. Authentication-column description
A commit can identify a repeatable catalog state, as the earlier MrKeyoor review advises. Hysenlabs' claim that a missing release prevents a pinned snapshot confuses commits with releases. Historical Hacktoberfest instructions also explicitly describe automated contribution tests, a more specific fact than the review's inference about freshness from omitted README documentation. Commit-pinning advice, automated contribution tests
The earlier MrKeyoor description "clearly alive" compresses editing activity and governance into one judgment. This review instead gives the dated push and attributed access reports. Dewrry1895/public-apis also needs a separate identity: its application download instructions belong to that owner, rather than this directory. Finally, the Auth column contradicts the assumption that public accessibility always means anonymous access. Earlier review, Dewrry1895 project, authentication walkthrough
FAQ
public-apis/public-apis is a community-curated directory, not a shared API service. Reading the README is the starting point for ordinary use. The supplied questions cover that basic workflow as well as pricing, maintenance, ownership and browser access; several originated in GitHub discussions about specific improvements or contribution problems. Each answer below addresses that question directly.
What is public-apis/public-apis?
public-apis/public-apis is a categorized directory of third-party APIs. Its entries include descriptions and authentication, HTTPS and CORS metadata. Directory description
How do I use public-apis/public-apis?
Open the README, choose a category and follow a provider's documentation link. Cloning is optional for reading; record a commit when preserving the catalog state matters. Usage and snapshot guidance
Are the APIs in the list really free?
The directory includes free and freemium services. Each provider sets its own allowances and terms, independently of the repository's MIT license. Directory pricing discussion
Is public-apis still maintained?
GitHub records a push on November 15, 2026. Historical issues separately document maintainer-access disputes. GitHub metadata, maintenance discussion
Who owns the public-apis project?
matheusfelipeog identified APILayer as the owner in the March 17, 2022 account in issue #3104. Ownership account
Should the community fork public-apis?
Participants in issue #3104 proposed a community fork after maintainers reported restricted access. The discussion records that proposal and the difficulty of directing readers to a replacement. Fork discussion
Is the recommendation to use public-apis-dev/public-apis still valid?
Issue #3484 contains the recommendation and a later question about its status after #3104 closed. The supplied GitHub response identifies its destination as marcelscruz/public-apis. Recommendation discussion, destination metadata
Can the directory move to a website with stronger search?
Issue #203 proposes a searchable website and discusses JSON and static hosting. Attilio81's separate MCP project documents another retrieval interface. Website discussion, MCP wrapper
Can the directory show whether APIs support CORS?
Yes. The primary issue thread records PR #589 merging to add a CORS column on January 15, 2018. CORS-column history
What does CORS mean in plain language?
CORS concerns browser JavaScript reading responses across origins. In issue #303, mgrigajtis describes cross-domain AJAX calls with client-side JavaScript. Community explanation
Can CORS support be checked automatically?
A commenter in issue #303 proposes requesting actual API URLs and inspecting Access-Control-Allow-Origin. Website URLs alone are the wrong target for that proposed check. Proposed checking method
Why does an API work in Postman or curl but fail in browser fetch?
Browser JavaScript applies cross-origin response-reading rules. The supplied guide explains opaque responses and proposes a server-side proxy for its illustrative request. Browser CORS guide
What we have not tested yet
The supplied lab records contain stopped attempts rather than a completed provider workload. Endpoint availability, response quality, quotas, authenticated flows and browser behavior across a selected sample were not measured. Actual runtime and operating-system versions require raw toolchain logs. The contradictory November 17 deployment header supplies no completed deployment result beyond the failed safety step and recorded teardown.
The MCP wrapper's parsing accuracy, refresh behavior and handling of stale metadata remain untested here. There is no side-by-side provider sample comparing the original directory with marcelscruz/public-apis. The present resolution of maintainer access, the continuing alternative recommendation, cleanup PR #1650's merge outcome and delivery of the original website proposal are unresolved in the supplied evidence.
The CORS automation discussion supplies a proposed method rather than a completed implementation result. The browser guide supplies instructional examples rather than our provider-specific fix. Automated contribution tests and scheduled endpoint monitoring are separate mechanisms; the evidence supports the former without settling the latter. All four rating dimensions remain unassessed because the supplied records do not support numerical editorial judgments.
The workshop establishes an additional-resource link rather than the origin of every provider used in its exercises. The YouTube transcript lacks a channel identity for reliable attribution, and Bilibili results advertise a Chinese-language edition whose relationship to the original is unresolved. Promotional inventory totals lack a shared dated counting method. No media transcript supplies a project-specific execution result for this review. Directory video, Bilibili results

