Merged
Conversation
🔗 Preview Mode
|
🔍 Link CheckStatus: ❌ Failed Summary
Broken links (63) — click to expandErrors per inputErrors in ./content/wallets/pages/bundler-api/bundler-faqs.mdx
Errors in ./content/changelog/2026-03-26.md
Errors in ./content/tutorials/alchemy-university/smart-contract-basics/multi-sig-contracts.mdx
Errors in ./content/changelog/2026-04-09.md
Errors in ./content/api-reference/op-mainnet/op-mainnet-api-faq/op-mainnet-api-faq.mdx
Errors in ./content/api-reference/starknet/starknet-api-faq.mdx
Errors in ./content/api-reference/hyperevm/hyperevm-api-overview.mdx
Errors in ./content/api-reference/arbitrum/arbitrum-api-faq/arbitrum-api-faq.mdx
Errors in ./content/api-reference/pricing-resources/resources/error-reference.mdx
Errors in ./content/api-reference/katana/katana-api-overview.mdx
|
Moved warning callout after table
dslovinsky
approved these changes
Apr 15, 2026
SahilAujla
approved these changes
Apr 15, 2026
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
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
Adds measured billing and usage guidance to the core WebSocket guidance docs so builders see bandwidth-based subscription pricing and the right guardrails before they choose a broad stream.
What Changed
Why
The docs already recommend using WebSockets for subscriptions only, but they did not clearly connect broad subscription scope to bandwidth-based billing or point users to spend caps and alerts where they make the transport choice.
Validation
pnpm run lint:eslint content/api-reference/websockets/subscription-api.mdx content/api-reference/websockets/subscription-api-endpoints/subscription-api-endpoints.mdx content/api-reference/websockets/best-practices-for-using-websockets-in-web3.mdx content/tutorials/getting-started/developer-best-practices/best-practices-when-using-alchemy.mdx