Support for OpenAI Responses API

[andresssantos]

Hi Spring AI team,

First of all, thanks for the amazing work you’ve done on Spring AI so far.

While integrating with OpenAI I noticed that Spring AI currently doesn't provides support for the newly‑released “Responses API” (docs: https://platform.openai.com/docs/api-reference/responses).

OpenAI positions the Responses API as:

• a more “agentic” primitive that natively supports tool usage (web search, file search, computer use, etc.),
• built‑in state handling (previous_response_id),

Because of these advantages, OpenAI encourages new users to prefer Responses over Chat Completions (docs: https://platform.openai.com/docs/guides/responses-vs-chat-completions).

Question / feature request

• Is there a plan or roadmap item for adding first‑class Spring AI support for the OpenAI Responses API?
• Is there any early design guidance you could provide (new ResponsesClient, extension of existing ChatClient, etc.)?

I think being able to swap between Chat Completions and Responses through the same Spring AI abstraction would align with the project’s goal of “easy component swapping with minimal code changes.”

Thank you for your time.

[markpollack]

Sure would be nice indeed!

Put it in the 1.0.x milestone for later triage and prioritization.

[tzolov]

The Responses API appears to be a stateful, standalone application (OpenAI's latest agentic attempt) rather than a traditional chat model.
It doesn't fit the existing ChatModel abstractions and isn't easily integrated as another chat-model provider.
IMO, It represents a new agentic category entirely.

[andresssantos]

Hi @tzolov,

What are your thoughts on how we might approach this in Spring AI? I understand that the Responses API is specific to OpenAI and wouldn’t apply to other providers. I also don’t closely follow the other providers, so I’m not sure if they offer anything similar to this new agentic category.

Thanks!

[winterbe]

I'm really looking forward to Spring AI Support for the OpenAI Response API. While OpenAI is stating that the existing Chat Completion API will not be deprecated any time soon, it all looks like the new Response API will be the defacto standard in the near future. OpenAI already suggests for new projects to use the Response instead of Chat Completions API. Response API is already the default in all of the OpenAI documents.

And for most some new features are already exclusive to the Response API such as:

• Remote MCP tools
• Builtin Tools (e.g. Websearch in Response API can be activated for via flag while in Chat Completions API have to be used via separate model)

Spring AI is a great library, thanks for all your hard work! Really looking forward for your future plans on that particular topic! ✊

[eypclk]

Hi,

Thank you for your great work on Spring AI! I'm following the discussion around OpenAI Responses API support with interest. The agentic capabilities of the Responses API (e.g., web search, state management) could bring significant value to Spring AI users. A new abstraction—like a ResponsesClient—might align better with the project's architecture.

I'd be interested to hear if there’s any roadmap or update planned for this.

Thanks again, and keep up the great work!