The Stack page is the answer to a question the catalog kept raising and could not previously answer: fine, but what about the twelve providers I actually depend on?
Type-ahead your way through the catalog, add those providers, and watch them in one table.
What the table shows
For every provider in your stack:
- Kin Score and band — the composite and where it sits
- Week-over-week movement — what changed since last week
- Movement since you added it — your own baseline, not ours
- Agent readiness — the separate score and band
- API count and published resources
- Access model — pricing, onboarding, whether you can try it now
Plus a rollup: the stack average, and the weakest link.
The weakest link is the number to look at. An integration estate is not as good as its best vendor. If eleven providers are exemplar and one is thin, the thin one is where your on-call gets paged, and it is the one that will not have documented its error semantics.
Movement since you added it
This is the part I think is genuinely new. Week-over-week movement is a catalog-wide fact. Movement since you added a provider is a fact about your relationship with that vendor.
You added a provider in March at 61.2. It is now 58.4. Nothing dramatic happened in any single week, and it has drifted three points since you made the decision — a deprecated spec, a stale changelog, a rate-limit page that stopped being updated. That drift is invisible in a weekly diff and obvious against your own baseline.
The export is the point
Export the whole stack as an APIs.json 0.21 apis.yml — or JSON, or straight to the clipboard.
Every provider in the export carries its rating and agent-readiness blocks, its published resources — OpenAPI, MCP server, agent skills, rules, scopes, security, changelog — and an include pointer back to the provider’s own apis.yml.
That last bit is what makes the file worth having. It is not a snapshot that rots; it is a set of pointers to each provider’s own machine-readable index. Upload one back to restore a stack on another machine. A single provider’s own apis.yml works as an import too, which means a vendor can hand you their file and you can drop it straight into your stack.
No account, and nothing leaves your browser
There is no login. The stack lives in one first-party cookie holding only provider slugs. Nothing is sent to APIs.io.
Clear your cookies and it is gone — which is exactly why the apis.yml download is the durable copy, and why the export was built first rather than an account system. If you want your stack to survive, the answer is a file you own, in an open format, in your repository.
About and Add API moved from the top nav to the footer to make room for it.
Takeaway
A watchlist of the providers you actually depend on, scored, tracked against your own baseline, with the weakest link called out — and exportable as an APIs.json 0.21 apis.yml that points at each provider’s own index. No account, one cookie, and a file you keep.
Build one at apis.io/stack/.