Tendril — AI Lessons for Real Life

Tendril

One Surface for Text, Vision, State, and Tools

Chat Completions taught a generation of developers the messages array. The Responses API is the newer shape: it supports text and image inputs, text outputs, conversation state, built-in tools, and function calling in one API.

import OpenAI from "openai"; const client = new OpenAI(); const response = await client.responses.create({ model: "gpt-5.5", instructions: "Be concise and verify assumptions.", input: "Draft an incident-summary template for a failed deploy.", }); console.log(response.output_text);The simplest Responses call still looks like a normal model request.

Use Chat Completions when	Use Responses when
You maintain a stable legacy chat app	You need built-in tools or multimodal workflows
You cannot migrate everything yet	You need conversation state without rebuilding threads
The endpoint is already working and low risk	You are starting a new OpenAI integration
You only need simple message in, text out	You need structured output, tools, or future agent features

Use Chat Completions when

Use Responses when

You maintain a stable legacy chat app

You need built-in tools or multimodal workflows

You cannot migrate everything yet

You need conversation state without rebuilding threads

The endpoint is already working and low risk

You are starting a new OpenAI integration

You only need simple message in, text out

You need structured output, tools, or future agent features

Wrap model calls behind one local client function.

Move one low-risk flow to Responses.

Add logging for latency, cost, and output quality.

Then migrate flows that need tools, vision, or structured data.

Keep old Chat Completions flows until they have a reason to move.

The big idea: new OpenAI apps should usually start with Responses, while old apps should migrate where the newer surface pays for itself.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-openai-responses-api-creators

What is the main idea of "The Responses API: OpenAI's Modern Developer Surface"?

The Responses API is where OpenAI puts stateful conversations, multimodal inputs, tools, and structured outputs. Learn the shape before you build.
Use AI as the final authority for the whole decision
Avoid checking the answer once it sounds polished
Focus only on speed instead of judgment

Which concept is most central to "The Responses API: OpenAI's Modern Developer Surface"?

Chat Completions
Responses API
stateful responses
tools

Which use of AI fits this topic best?

Let the AI decide what matters without your review
Use the answer before checking whether it fits the situation
Wrap model calls behind one local client function.
Treat the AI output as automatically correct

What should a careful learner remember about "Migration can be incremental"?

Use AI to draft or organize ideas about Responses API, then verify before acting.
Skip the context so the tool can guess faster
Treat the output as private even after sharing it online
Use the answer without checking the source

You want to use AI after this lesson. What is the safest next step?

Act immediately because the AI answer is written clearly
Use AI for drafting and comparison, but verify before publishing or relying on it.
Hide uncertainty so the final answer looks cleaner
Use private or sensitive details before checking permission

How should AI output about Responses API be treated?

As proof that no other source is needed
As a replacement for context, consent, or expert review
As a draft or helper output that still needs human judgment and verification
As something that becomes correct when it sounds confident

Name one way to verify an AI answer about Responses API.

Which action would help you apply "The Responses API: OpenAI's Modern Developer Surface" responsibly?

Use the tool to avoid thinking through the tradeoff
Keep going even if the output conflicts with a trusted source
Treat the AI output as automatically correct
Move one low-risk flow to Responses.

One Surface for Text, Vision, State, and Tools

Use Chat Completions when	Use Responses when
You maintain a stable legacy chat app	You need built-in tools or multimodal workflows
You cannot migrate everything yet	You need conversation state without rebuilding threads
The endpoint is already working and low risk	You are starting a new OpenAI integration
You only need simple message in, text out	You need structured output, tools, or future agent features

Use Chat Completions when

Use Responses when

You maintain a stable legacy chat app

You need built-in tools or multimodal workflows

You cannot migrate everything yet

You need conversation state without rebuilding threads

The endpoint is already working and low risk

You are starting a new OpenAI integration

You only need simple message in, text out

You need structured output, tools, or future agent features

Wrap model calls behind one local client function.

Move one low-risk flow to Responses.

Add logging for latency, cost, and output quality.

Then migrate flows that need tools, vision, or structured data.

Keep old Chat Completions flows until they have a reason to move.

The big idea: new OpenAI apps should usually start with Responses, while old apps should migrate where the newer surface pays for itself.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-openai-responses-api-creators

What is the main idea of "The Responses API: OpenAI's Modern Developer Surface"?

The Responses API is where OpenAI puts stateful conversations, multimodal inputs, tools, and structured outputs. Learn the shape before you build.
Use AI as the final authority for the whole decision
Avoid checking the answer once it sounds polished
Focus only on speed instead of judgment

Which concept is most central to "The Responses API: OpenAI's Modern Developer Surface"?

Chat Completions
Responses API
stateful responses
tools

Which use of AI fits this topic best?

Let the AI decide what matters without your review
Use the answer before checking whether it fits the situation
Wrap model calls behind one local client function.
Treat the AI output as automatically correct

What should a careful learner remember about "Migration can be incremental"?

Use AI to draft or organize ideas about Responses API, then verify before acting.
Skip the context so the tool can guess faster
Treat the output as private even after sharing it online
Use the answer without checking the source

You want to use AI after this lesson. What is the safest next step?

Act immediately because the AI answer is written clearly
Use AI for drafting and comparison, but verify before publishing or relying on it.
Hide uncertainty so the final answer looks cleaner
Use private or sensitive details before checking permission

How should AI output about Responses API be treated?

As proof that no other source is needed
As a replacement for context, consent, or expert review
As a draft or helper output that still needs human judgment and verification
As something that becomes correct when it sounds confident

Name one way to verify an AI answer about Responses API.

Which action would help you apply "The Responses API: OpenAI's Modern Developer Surface" responsibly?

Use the tool to avoid thinking through the tradeoff
Keep going even if the output conflicts with a trusted source
Treat the AI output as automatically correct
Move one low-risk flow to Responses.