The End of CRUD APIs? Designing Intent-Driven Services for AI Agents
Traditional CRUD APIs were designed around resources and operations such as create, read, update, and delete. That model remains effective for browsers, mobile applications, and service-to-service integrations where developers understand the domain and explicitly control the call sequence. AI agents operate differently. An agent receives a goal, selects tools dynamically, evaluates intermediate results, and may revise the execution path. Resource-oriented endpoints expose data structures, but they often hide the business meaning required for reliable autonomous action. As agentic systems become more common, API design is shifting from resource manipulation toward explicit intent.
A CRUD interface might expose /customers, /inventory, /payments, and /shipments. Completing a purchase could require the agent to retrieve a customer, validate an address, reserve stock, authorize payment, create an order, and schedule delivery. Each call introduces another schema, dependency, failure mode, and opportunity for incorrect sequencing. The agent must understand details that traditionally belong inside the service...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
