[pull] master from cube-js:master - #668
Merged
Merged
Conversation
…gent (#11566) * docs: document the deployment-scoped Chat API endpoint for the Auto agent The public Chat API can be addressed by deployment (`/api/v1/public/:account/deployments/:deploymentId/chat/...`) as well as by agent; the deployment form resolves to the deployment's Auto agent. Document both shapes for stream-chat-state and abort, and point at the deployment's API credentials page as the place to copy the URL from. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cr35TwoTbUhJr9onzbymXs * docs: correct Chat API auth support for the deployment-scoped endpoint The deployment form is served only through the Cube token exchange — that exchange is what resolves the Auto agent, so an API key (which carries no agent) is rejected with 403. Replace the claim that both forms take the same authentication with a support matrix and the concrete failure mode. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cr35TwoTbUhJr9onzbymXs * docs: qualify Chat API deployment-form auth and cover it in the OpenAPI spec Follow-up on review of the deployment-scoped Chat API docs: - State that the deployment form works only once Cube token auth is enabled (Settings -> Configuration), since that switch is off by default and the URL Cube surfaces in API credentials fails until it is flipped. - Qualify the abort endpoint's auth section the same way, so it no longer contradicts the support matrix two sections above. - Add the deployment-scoped server to the interactive API reference (api-reference/chat.yaml), which previously covered only the agent form. - Drop "the agent's deployment" in the Cube token section, which read oddly for the deployment form where no agent is in the request. - Label the matrix's first header column. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cr35TwoTbUhJr9onzbymXs * docs: match the OpenAPI deploymentId default to its own example The variable's description points at /d/9 while the default was '1', so the pre-filled playground value disagreed with the example beside it and with the deployment id used in chat-api.mdx. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cr35TwoTbUhJr9onzbymXs --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )