Each API is modeled once as a pack — a faithful, hand-built model of that service’s objects, lifecycle, errors, and webhooks. Point your app at a pack and it behaves like the real thing. The control surface (force outcomes, seed, events, clock, values you control) is identical no matter which one you pick — learn it once, use it everywhere. Looking for the API your app uses? Search the 500 most-integrated APIs below.

​
What a pack page gives you

Each pack page is a focused reference for that one API — so you can wire it up without reading the whole docs: its resources & lifecycle, the vendor’s real errors & magic values, its webhooks (and the branches you can force), and the values you control. New to ProdBreak? Start with the Quickstart — it’s the same three steps for every pack.
Don’t see yours, or want it sooner? If your app calls it over HTTP, it can have a pack — modeling a new API is new behavioral work, not new infrastructure. Search above and hit request a pack.