Is the Conversations API (with conversation state) separately chargeable?

API
, ,
1

Hi everyone,

I’ve been exploring the new Conversations API mentioned in the OpenAI docs on Conversation State.

From what I understand, it allows maintaining conversation threads and state natively — which looks really helpful compared to manually managing messages[] in the Responses API.

However, I couldn’t find any explicit details about pricing.

  • Is the Conversations API itself chargeable separately?

  • Also, does storing and retrieving conversation state incur any additional cost?

  • All previous input tokens for responses in the chain are billed as input tokens in the API?

If anyone from the OpenAI team or other developers has already tested or reviewed billing behavior for this API, I’d really appreciate your insights.

Thanks in advance!

2

Welcome to the community.

The Conversations API is not billed in any way atm, as far as I know (and as long as it is not abused).

It can store and edit conversations, and its contents are passed as inputs (then billed normally as input tokens) to your desired model.

There is a new endpoint in which you can preview how many input tokens will be used in a request here. You can pass your conversation id to it.

2 Likes