Added a "Copy Page" Button for Docs

[_j]

How about a “copy method” button to the API reference, that unravels the multiple levels of nesting to get the parameters? Even example code snippets included. yaml spec as a document is even further convoluted with references.

Over and over, I have to reproduce the contents in a format that is useful.

Discrepancy of image generation results in browser and via API

Reference Documentation for DALL-E 3 Parameters Endpoint: OpenAI Images API still current as of Nov 2024 This table outlines the parameters available and which will require alteration in order to generate images with dall-e-3 Parameters Parameter Type Required Default Description prompt string Yes N/A A text description of the desired image(s). Maximum length is 4000 characters for DALL-E 3. model string No dall-e-2 The model to use for image generation. Set to dall-e-3 to specify t…

Assistants API v2. Maximum number of chunks limit

Since this older topic about Assistants and its file search tool was last active, OpenAI has given more controls that make it more tolerable. chunk size (when adding to a vector store) the maximum number of chunks that will be returned a similarity threshold, below which chunks will not be returned The latter two are part of the tools specification itself, which is set when creating or modifying an assistant, or which can be overridden by tools in a run. The last is also called a “ranker”. …

Upload image to assistant via API

Sending a message is easy when it is just text. The content field is more complex when it is “array”, which is required for images. Here is a new API reference for you, since the current is so useless, neither human nor AI can understand. Assistants Message Content You have two different ways of sending content: content - string - Just the text you send as user message, no additional parts. or content - array - An array (list) of content parts with a defined type, each can be of ty…

File upload and acting on it in an assistant (v2) conversation

The only reason you wouldn’t get back an uploaded file in the list is if you had more than 10000 already uploaded. Or the changing implementation of projects and their effects on endpoints. You’d know if over 10k because of how long your code took. I suspect you can go the opposite direction for scoping: reuse the same openai client for every API interaction do not set parameters on the client instantiation - let it use it’s own grabbing of environment variables. Set all environment variables…