Most API tooling and discourse is built around an API producer mindset, but the real value lies in consuming APIs effectively. The author argues that thinking like an API consumer — understanding how APIs fit together across providers — is a rare and undervalued skill. Using MCP servers from Notion or Figma as examples, the point is made that producer-defined interfaces only go so far; true power comes when consumers define exactly what resources, functions, and context they need across multiple APIs. The rise of agentic workflows is shifting power away from individual API producers and toward a consumer-centric perspective that breaks down boundaries between services.
Sort: