A hands-on walkthrough of creating API applications across six major providers — Notion, Slack, LinkedIn, GitHub, Cloudflare, and Google — reveals that while OpenAPI standardized how to describe APIs, there is no standard for how to become a consumer of one. Each provider uses different vocabulary, gating mechanisms, scope models, and credential types. The divergence was tolerable when developers managed a handful of APIs, but becomes a serious problem as API counts scale and AI agents need to navigate these portals programmatically. Slack's JSON/YAML app manifest is highlighted as the only agent-friendly artifact among the six. The post argues for a cross-provider application manifest standard that captures credential types, scope vocabularies, resource selection models, verification states, and TTL/rotation policies.

9m read timeFrom apievangelist.com
Post cover image
Table of contents
Six providers, six different worldsWhy no standard ever emergedThe cost was bearable when we managed ten APIsAgents make this acute

Sort: