THE MINIMALIST RESPONSES API
Responses API Explained in 100 Words
Ravindra Dastikop
Understand less. Accomplish more.
Why This Book?
The Responses API is becoming complicated.
Inputs.
Models.
Outputs.
Tools.
Conversations.
Multimodal.
Streaming.
State.
Judgment.
But using the Responses API does not have to begin with complexity.
This book strips the Responses API down to what matters.
10 ideas.
10 words each.
100 words.
Enough to begin.
How to Read This Book
Read one idea.
Stop.
Think about it.
Try it with AI.
Then move to the next.
The purpose is not to know everything about the Responses API.
The purpose is to understand enough to accomplish something with the Responses API.
01 — RESPONSES
Responses provides OpenAI's unified interface for building intelligent applications today.
The Responses API is a central OpenAI API surface for building applications with models.
You send input.
Choose a model.
Give it instructions.
Optionally provide tools.
The model processes the request.
The API returns a response.
A response can involve more than generated text.
It can include messages, reasoning, tool calls, and other output items.
The important shift is simple.
You describe what needs to be accomplished and let the model work through the available capabilities.
02 — INPUT
Input supplies text, images, files, or other information for processing.
Every response begins with input.
Input tells the model what it has to work with.
That might include:
Text.
Images.
Files.
Instructions.
Previous interaction items.
Information returned from tools.
Good input gives the model useful material for accomplishing the task.
The important question is:
What information does the model need to do this work?
03 — MODEL
Models process supplied inputs and generate useful outputs or actions.
The model provides the intelligence behind the response.
It processes the supplied input.
Interprets instructions.
Works with available context.
Reasons when appropriate.
Generates output.
And may decide to use available tools.
The API provides the interface.
The model performs the intelligence work.
04 — OUTPUT
Output contains generated messages, tool calls, and other response items.
A response is not necessarily one block of text.
The Responses API can return different kinds of output items.
These can represent:
Messages.
Reasoning.
Tool calls.
Function calls.
Other response items.
This matters because an AI application may need to do more than display an answer.
It may need to interpret an item.
Execute a tool.
Continue a workflow.
Or present the final result.
05 — TOOLS
Tools extend models with search, files, code, computers, and MCP.
Models can generate information.
Tools let them do more.
Depending on the model and configuration, tools can provide capabilities such as:
Web search.
File search.
Code execution.
Computer interaction.
Function calling.
MCP connections.
Tools allow the model to interact with capabilities beyond language generation alone.
The question becomes:
What capability does the model need to accomplish this task?
06 — CONVERSATION
Conversations maintain related input and output items across multiple interactions.
Useful AI work often takes more than one turn.
You ask.
The model responds.
You add information.
The model continues.
The Responses API supports continuing related interactions rather than treating every request as completely isolated.
That enables:
Follow-up questions.
Corrections.
Refinement.
Additional context.
Continuing work.
Conversation turns individual responses into an evolving interaction.
07 — MULTIMODAL
Multimodal capabilities let models process text and images within requests.
Human information does not exist only as text.
Sometimes the model needs to work with an image.
A document.
Or another supported form of information.
Multimodal capabilities allow applications to provide different forms of input to compatible models.
An application might combine:
Instructions.
Text.
Images.
Files.
And other supported inputs.
The interaction becomes richer than text alone.
08 — STREAMING
Streaming delivers response events progressively while model generation continues asynchronously.
Some responses take time.
Applications do not always need to wait until everything is finished.
Streaming allows response events to arrive while generation continues.
That can include:
Text updates.
Tool-related events.
Completion events.
Other response events.
This can make an application feel more responsive.
Instead of:
Wait → Complete response.
You can have:
Generate → Stream → Receive.
09 — STATE
State preserves relevant interaction information across connected model responses automatically.
Many useful AI tasks continue over several responses.
The system therefore needs a way to preserve relevant interaction information.
State allows later responses to build on earlier work.
That can support:
Follow-up questions.
Refinement.
Continuing reasoning.
Tool workflows.
Longer tasks.
Without state, every request risks becoming an isolated interaction.
With state, responses can become connected work.
10 — JUDGMENT
Human judgment determines which generated outputs and actions deserve acceptance.
The Responses API can make applications powerful.
Models can generate.
Reason.
Use tools.
Retrieve information.
And trigger actions.
But capability does not eliminate responsibility.
Humans and organizations still need to determine:
Is the output accurate?
Is the tool appropriate?
Should this action occur?
Does sensitive information require protection?
Should the result be trusted?
Should the workflow continue?
AI generates and acts within configured capabilities.
Humans remain responsible for deciding what should move forward.
The Entire Book in 100 Words
RESPONSES
Responses provides OpenAI's unified interface for building intelligent applications today.
INPUT
Input supplies text, images, files, or other information for processing.
MODEL
Models process supplied inputs and generate useful outputs or actions.
OUTPUT
Output contains generated messages, tool calls, and other response items.
TOOLS
Tools extend models with search, files, code, computers, and MCP.
CONVERSATION
Conversations maintain related input and output items across multiple interactions.
MULTIMODAL
Multimodal capabilities let models process text and images within requests.
STREAMING
Streaming delivers response events progressively while model generation continues asynchronously.
STATE
State preserves relevant interaction information across connected model responses automatically.
JUDGMENT
Human judgment determines which generated outputs and actions deserve acceptance.
The Minimalist Responses API
You do not need to understand everything about the Responses API before you begin using it.
Remember ten things:
Responses.
Input.
Model.
Output.
Tools.
Conversation.
Multimodal.
Streaming.
State.
Judgment.
Everything else can come later.
Start with the input.
Choose the model.
Understand the output.
Add tools when needed.
Continue through conversation.
Use multimodal inputs when useful.
Stream responses when appropriate.
Maintain state across connected work.
Apply human judgment.
Then accomplish something.
One Final Question
The next time you build with the Responses API, don't begin with:
“Which API parameters should I use?”
Begin with:
“What do I want the model to accomplish?”
Then build the response.
