-
Notifications
You must be signed in to change notification settings - Fork 23
Open
Description
Hi,
Three days ago OpenAI released Response API, an orchestration of assistant tools + capabilities of chat completion. A note in release also states that consumers should start building on top of Response API rather than completion to leverage in built tools.
From Open AI News: "However, the Responses API is a superset of Chat Completions with the same great performance, so for new integrations, we recommend starting with the Responses API."
I have started looking into arc to bring responses API and I would like to propose the following:
- Do not invent another interface parallel to ChatCompletor until other model providers also adopt this API as a global specification like /chat/completions.
- Support response API only for Arc Agents built specifically on top OpenAI API for the interim.
- Tactical implementation can have an attribute api in ChatCompletionSettings of type string with default value as
completionsand other supported value asresponses. - All other ChatCompletors except arc-openai-client will reject
responsesrequest. OpenAINativeClientimplementation can tactically handlecompletionsorresponsesrequests.
Metadata
Metadata
Assignees
Labels
No labels