Delivering a Modern API Integration Page with Arazzo

About this paper

I am going to open this paper with a sentence that sounds heretical and is actually the most boring, obvious thing I have said in years: you should not be building integrations anymore. You should be describing them. Strip an integration down and you find two APIs and a wire between them — call an operation on the first, catch the response, carry the useful parts into an operation on the second. That is the entire job, and we have spent two decades dressing it up as custom code, connector apps, certified marketplace listings, and no-code automations locked inside somebody else’s runtime.

What changed is that both ends of the wire already describe themselves. Nearly every API worth integrating with publishes an OpenAPI definition; the only thing ever missing was a portable, machine-readable way to describe the sequence between them, and that is exactly what Arazzo — the workflow member of the OpenAPI family — was built to hold. This paper reframes your integrations page from a gallery of partner logos into a directory of forkable, runnable Arazzo workflows; walks the full anatomy of an Arazzo-backed integration; rebuilds the most popular listings from a major marketplace as verified workflows against real definitions on both ends; is honest about the parts that are still hard (authentication across two providers, rate limits, pagination, async completion, partial failure); and makes the economic case that a customer who owns a portable integration beats one who rents a connector. It closes on the agentic turn — where MCP is the wire and Arazzo is the conductor — and a provider self-assessment you can run in an afternoon.

What's inside

1. The integration was always two ends and a wire
2. From connectors to described behavior — the sixteen-year trap
3. What Arazzo is, and what it is not
4. From a gallery to a directory — the integrations page reimagined
5. The anatomy of an Arazzo-backed integration
6. A worked example — rebuilding a marketplace as workflows
7. The honest hard parts — auth, rate limits, pagination, async, failure
8. What the marketplace becomes — the economics of described integrations
9. Anti-patterns I'll be watching for
10. Where this is going — MCP is the wire, Arazzo is the conductor
11. Provider self-assessment

What you get for $25.00