GitHub - mindcloud-inc/universal-api-reference: One consistent API reference for 3,000+ APIs for developers and AI agents. · GitHub
/" data-turbo-transient="true" />
Skip to content
Type / to search
Sign in<br>Sign upAppearance settings
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading. Please reload this page.
mindcloud-inc
universal-api-reference
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star<br>25
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>17 Commits<br>17 Commits
.github/ISSUE_TEMPLATE
.github/ISSUE_TEMPLATE
apis
apis
catalog
catalog
indexes
indexes
CONTRIBUTING.md
CONTRIBUTING.md
LICENSE
LICENSE
README.md
README.md
SECURITY.md
SECURITY.md
catalog.json
catalog.json
llms.txt
llms.txt
View all files
Repository files navigation
Universal API Reference
The API surface of 3,191 apps — 75,488 endpoints — documented in one uniform, greppable format. Every app gets the same treatment: authentication, pagination, filtering, sorting, argument conventions, response formats, and a mapping back to the vendor's native API. One file per endpoint.
git clone https://github.com/mindcloud-inc/universal-api-reference.git
# every app that can issue a refund<br>rg -l "refund" apis
# how a specific API paginates, straight from the spec<br>rg "pagination" apis/s/stripe/universal-api/README.md -A 3
Why this exists
APIs are filthy things. If there is one true REST standard, precious few companies have ever fully followed it. Every vendor invents its own pagination, its own filtering syntax, its own creative interpretation of HTTP status codes. This repo documents all of them the same way, so you don't have to be a specialist in a system to consume its API:
Request & response formats and datatypes
Pagination
Filtering & sorting
HTTP methods & status codes
Native-API mapping (endpoint, quirks, source docs)
Averaged out, that's ~23.7 documented endpoints per app — most integration platforms cover 7–8.
What's in this repo
apis///universal-api/ — the Universal API README, auth, pagination, filtering, sorting, argument conventions, examples, and one file per action.
apis///native-api/ — the vendor-native API README and one file per native operation.
catalog.json — machine-readable catalog of all 3,191 apps, with per-letter shards under catalog/.
indexes/ — app indexes by category, API specification, and native-docs link.
llms.txt — index of this repo for LLM ingestion.
indexes/api-specifications.md — generated Universal API OpenAPI files and provider-published Native API specifications.
indexes/native-api-docs.md — the vendors' own API documentation, one link per app.
Example: one endpoint file
Stripe: Cancel Payment Intent
Cancels an existing payment intent in Stripe.
PUT https://connect.mindcloud.co/v1/universal/stripe/latest/actions/cancel-payment-intent
Native API mapping: POST payment_intents/:intent/cancel — vendor documentation.
Where these docs come from
This is not scraped documentation. It's a nightly mirror of the machine-readable spec that drives MindCloud's integration gateway — the product of years of building and validating app integrations, and the same spec its production systems execute API calls against at a run rate of ~1.85 billion per year. When a doc is wrong, real workflows break, and the spec gets fixed. Changes land here as daily commits, so you can watch it evolve in the history.
Full disclosure: MindCloud sells a Universal API and MCP that can call every endpoint in this repo through one interface.
Ways to use it
Native API reference — integrating directly with an app? Each endpoint file documents the native endpoint, arguments, pagination, and quirks, with links to source docs. No account, no SDK, no gateway required.
Agent context — point your agent or RAG pipeline at llms.txt and catalog.json, or vendor the folders for the apps you care about.
Grep across every API at once — find every app with a refund endpoint, every API that paginates by cursor, every endpoint that touches invoice.
Unified API / MCP — if you'd rather call all 3,191 apps through one REST signature and auth model, that's the hosted thing.
Browse
By letter:<br>A (185) · B (146) · C (285) · D (170) · E (131) · F (136) · G (117) · H (89) · I (94) · J (25) · K (47) · L (123) · M (166) · N (86) · O (94) · P (251) · Q (33) · R (149) · S (360) · T (174) · U (59) · V (74) · W (97) · X (12) · Y (22) · Z (66)
By category:<br>Communication (181) · Productivity (372) · IT Operations (390) · Sales & CRM (170) · Commerce (289) · Marketing (394) · Content & Files (71) · Support (180) · Human Resources (77) · Business...