What's the difference between the OpenAI Agents SDK and the Responses API?

The Responses API is OpenAI’s single call to a model, one request in and one response out, with no orchestration layered on it; the Agents SDK is a runtime built on top of that call, adding the loop, handoffs, guardrails, and sessions a bare API call doesn’t have. OpenAI’s own SDK docs put it plainly: the SDK “uses the Responses API by default for OpenAI models, but it wraps model calls in a higher-level runtime.”

That wrapping is what matters for grading a run. Call the Responses API directly and you get one thing to look at, the request and the response, with a tool call inside if the model asked for one; you track conversation state yourself, and a handoff between two roles is just a decision your own code makes, invisible to anything watching the API. The Agents SDK cuts the same run into a span per agent, per model call, per tool call, per handoff, and per guardrail, each gradable on its own. Pick the API when you’re writing the loop yourself; pick the SDK when you want that decomposition for free and can live inside its runtime.

sources

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y