xAI has introduced a new capability allowing users to attach files to chat conversations. This feature, available through the Responses API, enables intelligent document search within the attached files. When files are included, the system automatically activates document search, converting the request into an agentic workflow.
Files can be attached using either a public URL or an uploaded file ID. The Responses API is the recommended method for interacting with xAI models, offering new capabilities not present in the legacy Chat Completions API.
Key Points
- Users can attach files to chat messages using a public URL or an uploaded file ID.
- Attaching files enables intelligent document search capabilities, creating an agentic workflow.
- The Responses API is the recommended way to interact with xAI models and supports this new file attachment feature.
- The Chat Completions API is a legacy endpoint, and new features, such as file attachment, are delivered via the Responses API.
- For multi-turn conversations, the Responses API allows continuation using a
previous_response_id, unlike the Chat Completions API which requires resending the entire history.
Context
According to xAI documentation, the Responses API is designed to replace the legacy Chat Completions API. The Responses API provides a different response format and streamlines multi-turn conversations by allowing users to continue a conversation without resending the full history. The Chat Completions API is noted as a deprecated endpoint, with new capabilities being prioritized for the Responses API.
Why It Matters
This update from xAI enhances the utility of its models by allowing direct interaction with user-provided documents, which can improve the accuracy and relevance of responses. The shift to the Responses API also indicates a strategic move towards more efficient and capable conversational AI.
What To Do
- Review the xAI documentation for the Responses API to understand its structure and capabilities.
- Test attaching files to chat messages using both public URLs and uploaded file IDs.
- Compare the Responses API with the legacy Chat Completions API to understand the differences in response format and conversation management.
- Note the migration guide for moving from the Chat Completions API to the Responses API if currently using the legacy endpoint.