Skip to content

[docs-agent] Split Sui gRPC streaming methods into a bandwidth-priced section - #1518

Open
alchemy-bot wants to merge 2 commits into
mainfrom
docs/sui-grpc-streaming-cu-section
Open

[docs-agent] Split Sui gRPC streaming methods into a bandwidth-priced section#1518
alchemy-bot wants to merge 2 commits into
mainfrom
docs/sui-grpc-streaming-cu-section

Conversation

@alchemy-bot

Copy link
Copy Markdown
Contributor

Summary

Clarifies Sui gRPC billing on the Compute Unit Costs page:

  1. Adds a new # Sui: gRPC Streaming Methods section modeled on the existing # Solana: Yellowstone gRPC section — bandwidth pricing at $75 / 1 TB, pro-rated, [Contact us] CTA. Placed immediately after # Sui: Standard Methods for parity with how Solana Yellowstone gRPC sits alongside # Solana: Standard JSON-RPC Methods.
  2. The intro sentence calls out the six streaming methods the requester listed inline: SubscriptionService/{SubscribeCheckpoints, SubscribeTransactions, SubscribeEvents} and LedgerService/{ListCheckpoints, ListTransactions, ListEvents}.
  3. Removes sui.rpc.v2.SubscriptionService/SubscribeCheckpoints from the per-method {/* cu:auto product="sui-grpc" */} table since it is bandwidth-priced, not per-call. This is the only one of the six methods currently present in that cu:auto table.

Daikon note

The sui-grpc per-method table is Daikon-managed via cu:auto markers (PR #1424 / #1425 pattern). The manual removal of SubscribeCheckpoints from that block will be reverted on the next daily 12 PM EST Daikon run unless the method is also reclassified in topconfig.yml upstream (OMGWINNING/chain-config) so Daikon stops emitting it under the sui-grpc product. Flagged so a follow-up chain-config PR can pin the change.

The other five methods listed in the new section are not currently in the sui-grpc cu:auto table, so no removal is needed for them today.

Linear

DOCS-185 — https://linear.app/alchemyapi/issue/DOCS-185/split-sui-grpc-streaming-methods-into-a-separate-bandwidth-priced

Requested by

@oskarciupider-alchemy (via Slack thread)

… section

Add a new "Sui: gRPC Streaming Methods" section modeled on the existing "Solana: Yellowstone gRPC" bandwidth section ($75 / 1 TB, pro-rated). Streaming methods (SubscriptionService/{SubscribeCheckpoints,SubscribeTransactions,SubscribeEvents} and LedgerService/{ListCheckpoints,ListTransactions,ListEvents}) are called out inline in the intro sentence.

Also drop sui.rpc.v2.SubscriptionService/SubscribeCheckpoints from the per-method cu:auto "Sui: gRPC Methods" table since it is bandwidth-priced, not per-call. NOTE: that table is Daikon-managed via cu:auto markers and the row will be re-added on the next daily Daikon run unless the method is also reclassified in topconfig.yml upstream (OMGWINNING/chain-config).

Refs DOCS-185

Requested-by: @oskarciupider-alchemy
@alchemy-bot
alchemy-bot requested a review from a team as a code owner August 11, 2026 15:12
@github-actions

github-actions Bot commented Aug 11, 2026

Copy link
Copy Markdown

🔗 Preview Mode

Name Status Preview Updated (UTC)
Alchemy Docs ✅ Ready 🔗 Visit Preview Aug 11, 2026, 3:26 PM

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ca951cb6fd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".


# Sui: gRPC Streaming Methods

Sui gRPC [streaming methods](/docs/reference/sui-grpc-overview) (`SubscriptionService/SubscribeCheckpoints`, `SubscribeTransactions`, `SubscribeEvents`, and `LedgerService/ListCheckpoints`, `ListTransactions`, `ListEvents`) deliver real-time blockchain data via server-streaming RPCs. Pricing is based on **bandwidth:** the amount of data delivered as part of the stream.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Document the newly priced Sui gRPC streams

This sentence starts advertising and pricing five Sui gRPC methods that the linked Alchemy Sui gRPC overview/API reference does not expose (SubscribeTransactions, SubscribeEvents, ListCheckpoints, ListTransactions, and ListEvents); I checked the Sui gRPC docs in this repo and rg shows those names only in this new pricing line. When customers follow the pricing page to implement one of these bandwidth-priced streams, they have no Alchemy request/response docs or examples, so please either add the corresponding API reference pages/overview entries or limit this pricing section to methods that are actually documented.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Codex's observation is factually correct — the five newly-priced Sui gRPC streaming methods (SubscribeTransactions, SubscribeEvents, ListCheckpoints, ListTransactions, ListEvents) do not have per-method API reference pages under the Sui gRPC section today. SubscribeCheckpoints is the only Sui streaming method with any docs presence, and it was in the cu:auto product="sui-grpc" table strictly because Daikon's topconfig.yml grouped it there for per-method CU tracking (removed in this PR since it's actually bandwidth-priced).

Not applying the fix here because:

  1. Scope: this PR was tightly scoped to the pricing-page clarification the requester (@oskarciupider-alchemy) asked for. Adding five new per-method API reference pages is a substantially different scope.
  2. Daikon-managed surface: Sui gRPC per-method pages live under the cu:auto product="sui-grpc" scope; adding real reference pages requires coordinated changes in OMGWINNING/chain-config (topconfig.yml + chainconfig/) before the docs side can stabilize. That's a separate cross-repo workstream, not a small docs edit.
  3. Precedent: Alchemy's Solana Yellowstone gRPC pricing section on the same page also disclaims bandwidth pricing for the geyser.Geyser/Subscribe stream without linking to a dedicated per-method API reference page — the pricing disclosure and the API reference surface have historically been decoupled here.

The underlying gap (bandwidth-priced streaming methods lack dedicated API reference pages) is worth tracking, but as a follow-up ticket rather than blocking this pricing clarification. Leaving the thread open so a human reviewer can decide whether to spin one off.

…on Compute Unit Costs

Move "Solana: Yellowstone gRPC Unary Methods" from the bottom of the page up to sit right after "Solana: Yellowstone gRPC" and before "Solana: WebSocket Subscriptions", so both Yellowstone sections are adjacent.

Move "Sui: gRPC Methods" from the bottom of the page up to sit right after "Sui: gRPC Streaming Methods" and before "Tron: Standard HTTP Methods", so the three Sui sections (Standard Methods, gRPC Streaming Methods, gRPC Methods) are adjacent.

Pure reorder: content and cu:auto markers are unchanged.

Refs DOCS-185

Requested-by: @oskarciupider-alchemy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant