docs(streaming): update concurrent stream cap from 10 to 1 per key#199
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Policy changed 2026-04-27: every paid tier defaults to 1 concurrent stream with newer-wins displacement. Fleet limits require a maxStreams override via Unkey metadata (contact sales). Updated streaming/overview.mdx, pricing.mdx, and api-reference/websocket.mdx. single-connection.mdx already reflected the correct policy. Co-Authored-By: Paperclip <noreply@paperclip.ing>
Mlaz-code
force-pushed
the
docs/streaming-stream-cap-1-per-key
branch
from
2986275 to
998a0b3
Compare
Mlaz-code
added a commit
that referenced
this pull request
May 7, 2026
) Policy changed 2026-04-27: every paid tier defaults to 1 concurrent stream with newer-wins displacement. Fleet limits require a maxStreams override via Unkey metadata (contact sales). Updated streaming/overview.mdx, pricing.mdx, and api-reference/websocket.mdx. single-connection.mdx already reflected the correct policy. Co-authored-by: root <root@api-dev.hs.chocopancake.com> Co-authored-by: Paperclip <noreply@paperclip.ing>
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Brings three pages in line with the policy change that landed on the API on 2026-04-27: every paid tier now defaults to 1 concurrent stream, with newer-wins displacement (a second connection from the same key sends close
4001 displaced by newer sessionto the older one). Fleet limits require amaxStreamsoverride in Unkey metadata via Enterprise.The recently-merged single-connection guide (#198) already reflected the new policy. This PR fixes the other three pages that still claimed "10 streams":
content/en/streaming/overview.mdxcontent/en/pricing.mdxcontent/en/api-reference/websocket.mdxOrigin
Authored by a parked Paperclip agent on
paperclip/SHA-217412 hours ago, never PR'd. Cherry-picked onto a fresh branch offorigin/main. The dirtypublic/openapi.jsonregen in that worktree was deliberately excluded — it's stale generator drift unrelated to this feature.Test plan
grep -ri "10 stream" content/)🤖 Generated with Claude Code