Surface Order - which integration surface to build next, and in what order

Decide which integration surfaces your platform builds for outside developers and AI agents - REST, webhooks, SDKs, GraphQL, gRPC, SQL, bulk data, a CLI, MCP, embedded components, a Terraform provider - and in what order, by reversal cost and audience rather than novelty. Free in your browser: the lead posture ranked from your buyer, the spec and telemetry groundwork, demand signals weighed (a blocked deal over telemetry over community asks), every surface in play sequenced into waves your team can carry behind the contract it derives from, MCP last on agent signals, and your own draft order checked for MCP-first, sprawl and derived-before-contract - plus a gate sheet and a build-order CSV. A metered run writes the sequencing plan, or one handoff card per surface with the review cadence. Built on the SkillSafe skill @samber/api-integration-surface-strategy, from samber/developer-platform-skills (MIT), by Samuel Berthe.