An API is a product. Why versioning, validation and error semantics matter more than the style choice.
Category · Backend & Data
An interface is a product contract.
An API is the technical interface through which systems talk to each other. REST, GraphQL, gRPC, WebSocket — depending on the use case. For almost every product API, REST with JSON is the most pragmatic choice.
More important than picking a style is how you handle the contract: versioning, validation, clear error semantics, documentation, monitoring. An API is a product that other teams consume.
APIs and AI.
LLM providers expose their models via APIs (Anthropic Messages API, OpenAI API). Agents use APIs as tools — every API call is a possible agent action. Which means: the quality of an AI integration depends on the quality of the surrounding APIs.
