← Connor O’DeaInfrastructure
2026 · In build

APIDistributed

An API marketplace built for agents, not portals.

Cloudflare WorkersTypeScriptMCPD1
Private repository

Problem

API marketplaces were built for a human browsing a catalog, signing up, and copying a key. Agents need to discover, authenticate, and transact programmatically, and every existing marketplace makes that the hard path.

Approach

  1. 01

    Make the marketplace MCP-native, so an agent can enumerate and call APIs through a protocol it already speaks.

  2. 02

    Run the whole surface at the edge, because an agent chaining several calls pays every millisecond of latency more than once.

  3. 03

    Keep provider onboarding to an OpenAPI spec, so listing an API is a configuration step rather than an integration project.

What it taught me

Edge runtimes change what you can assume. A surprising amount of standard Node middleware simply does not exist there, and the constraint pushed the design toward something simpler than what I would have built on a server.

Architecture

Edge
Cloudflare Workers, global by default
Data
D1 for catalog, KV for hot routing
Protocol
MCP server exposing the catalog as tools
Billing
Per-call metering at the edge
NextCutroom