nknj

6 ms·

1.
by nknj 1y ago
we expect responses and realtime to be our 2 core api primitives long term — responses for turn by turn interactions and realtime for models requiring low latency bidirectional streams to/from the apps/models.
2.
by nknj 1y ago
sorry about the error in the docs. we're removing that call out. `"vector_store_ids": ["<vector_store_id1>", "<vector_store_id2>"]` is exactly right. only 2 vector stores are supported at the m
3.
by nknj 1y ago
you can use local mcp servers with the agents sdk: https://openai.github.io/openai-agents-python/mcp/ responses api is a hosted thing and so it made most sense for it to directly connect to other hosted services (
4.
by nknj 1y ago
one additional difference between chat and responses is the number model turns a single api call can make. chat completions is a single turn api primitive -- which means it can talk to the model just once. responses is capable of making mul
5.
by nknj 1y ago
I hear you and really appreciate the patience here. We're almost ready to share a migration guide. Today, we closed the gap between Assistants and Responses by launching Code Interpreter and support for multiple vector stores in File S
6.
by nknj 2y ago
there's no rush to do this - in the coming weeks, we will add support for: - assistant-like and thread-like objects to the responses api - async responses - code interpreter in responses once we do this, we'll share a migration gu
7.
by nknj 2y ago
Proud to have Stainless as a partner at OpenAI. All our SDKs are generated by them. Alex, Robert, Philip and team are extremely thoughtful about SDK design and push us to improve our API + other products while they're at it. Stainless
8.
by nknj 9y ago
https://projecteuler.net/
9.
Heroku Buildpack Yo Angular(github.com)
1 points by nknj 12y ago|0 comments