AI Agents API Explained: What Indie SaaS Founders Actually Need to Build
OpenAI's current agent stack has three paths. Choose the runtime that matches the workflow instead of starting with the most sophisticated option.
OpenAI's current agent stack has three paths. Choose the runtime that matches the workflow instead of starting with the most sophisticated option.
The useful API decision is about control: who owns orchestration, state, tools, approvals, and execution. OpenAI's current docs separate the Agents API, Agents SDK, and Responses API along those lines.
The word “agent” can make a small software project sound much more complicated than it needs to be.
The more useful question is not “which agent API is hottest?” It is “which part of the workflow should the model control, and which part should my application control?”
OpenAI's current agent documentation separates three approaches: the Agents API, the Agents SDK, and the Responses API. The Agents API is for workflows where more of the agent runtime is managed for you. The Agents SDK is designed for applications that want to own the agent loop, tools, storage, and approvals. The Responses API gives the application more direct control over model responses and tool use.
That distinction matters for an indie SaaS because infrastructure complexity compounds quickly.
Write one real customer workflow before writing an agent prompt.
For example:
A support ticket arrives → retrieve account details → classify the issue → draft a response → ask an operator for approval → send the response.
That is already an agent-shaped workflow, but not every step should be probabilistic.
The model can classify the issue and draft language.
Your application should retrieve the account.
Your application should decide whether the operator has permission to access the account.
Your application should decide whether sending the message requires approval.
The agent is one component inside the workflow.
The Responses API is a useful foundation when your application wants to stay close to the model request.
OpenAI's current documentation shows tools can be attached to a response, including hosted capabilities and application-defined function calls. The application can also guide tool selection.
That makes the API suitable for focused features such as support copilots, research helpers, document analysis, sales research, and structured workflow helpers.
A typical pattern is:
user request → model → tool request → server validation → tool result → model response
The important part is the middle.
The model can ask to call a tool. It should not get to bypass the server.
The Agents SDK becomes useful when the workflow has structure that you expect to reuse.
Imagine a lead-research SaaS with:
research agent → website retrieval → CRM lookup → enrichment → scoring → approval → CRM update
Now you may need reusable agents, tools, handoffs, sessions, tracing, and evaluation.
The SDK is designed for applications that want to keep those runtime responsibilities inside their own infrastructure.
That is a meaningful architectural choice. You are trading some implementation work for direct control.
A managed agent runtime makes sense when the provider-managed execution model removes operational work that you would otherwise have to build.
Ask a practical question:
What do I no longer need to operate?
If the answer is “very little,” adding a managed agent layer may not improve your product.
If the answer is “long-running execution, persistence, orchestration, and infrastructure around those jobs,” then the trade-off is easier to justify.
Before giving an agent production access, define:
Data boundary: what can it read?
Action boundary: what can it change?
State boundary: what belongs in temporary context versus durable storage?
Failure boundary: what happens when the model, tool, or external API fails?
These rules should live in software.
A prompt saying “do not change billing” is not an authorization system.
A practical first version can be:
one model + three to five narrow tools + validation + logs + an approval gate for risky actions.
That is enough to produce a useful workflow without creating a miniature platform team.
Use deterministic code for deterministic decisions.
Use model reasoning where ambiguity actually exists.
For example, a model can decide that a ticket sounds like a refund request. The billing service should determine whether a refund is actually permitted.
Do not measure success by token count or number of agent steps.
Measure:
An eight-step agent that produces the correct outcome may be better than a two-step agent that creates work for the customer.
OpenAI's current developer materials now treat tools, state, runtimes, observability, guardrails, and evaluation as core parts of agent development. The Agents cookbook includes examples around SRE workflows, Slack bots, memory, sandboxed agents, and spending controls.
That is the important shift.
The product is no longer “a prompt connected to an API.”
It is a controlled software workflow surrounding a model.
Use the Responses API when your application can comfortably own the loop.
Use the Agents SDK when you need reusable agent behavior, orchestration, sessions, handoffs, or deeper runtime control.
Use a managed agent runtime when it removes substantial operational work for the kind of job you actually have.
Do not choose based on the word “agent” in the product name.
Choose based on who should own the workflow.
For an indie founder, the best agent architecture is usually the smallest one that solves a real repeated problem.
Keep business rules deterministic.
Keep tools narrow.
Keep permissions server-side.
Keep state deliberate.
Add orchestration only when the workflow needs it.
The API is a component. The customer outcome is the product.
Community
0 comments
React to this article
Trending now
Written by
Kirtesh Admute
Founder
Kirtesh Admute is the founder of IndieFounder, a platform for founders, builders, and people curious about technology. He writes about AI, startups, software, product building, and the lessons that come from building in public.
See an issue with this story?
Continue reading
