docs(pricing): update compute unit costs from Daikon [Bot] - #1585
Conversation
🔗 Preview Mode
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6cf34b4ab2
ℹ️ 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".
| @@ -1209,18 +1209,12 @@ On average, a typical byte-priced webhook or WebSocket subscription event is abo | |||
| | Method | CU | | |||
| | ---------------------------------------------------------- | -- | | |||
| | sui.rpc.v2.LedgerService/GetServiceInfo | 10 | | |||
There was a problem hiding this comment.
The six deleted RPCs remain publicly supported: content/api-reference/sui-grpc/subscriptions.mdx:7-101 documents the three subscription calls, and content/api-reference/sui-grpc/objects-and-ledger.mdx:221-322 documents the three List* calls. Removing them from this table leaves these active methods without either a CU value or a Sui-specific bandwidth rate, so users cannot calculate their billing or throughput usage. Restore their pricing in Daikon or document the replacement streaming-pricing rule before removing these rows.
Useful? React with 👍 / 👎.
| | Method | CU | | ||
| | ------ | -- | |
There was a problem hiding this comment.
content/api-reference/aptos-grpc/transaction-stream.mdx:7-40 still exposes aptos.indexer.v1.RawData/GetTransactions, and the Aptos quickstart invokes it, but this edit replaces its sole pricing row with an empty table. Because no Aptos-specific alternative billing rule is documented, customers using the only public Aptos gRPC method can no longer determine its cost. Restore the Daikon entry or add the applicable streaming rate.
Useful? React with 👍 / 👎.
…RPC streaming Complements the isStreaming filter added to the Daikon dashboard workflow in OMGWINNING/dashboard#8555. That change stops streaming methods (sui-grpc x6, aptos-grpc x1, and yellowstone-grpc's existing filter) from being emitted into the cu:auto per-method tables, so we can now hand-write bandwidth-priced sections for them without being overwritten on the next daily Daikon run. Sui: adds a new '# Sui: gRPC Streaming Methods' section above the existing sui-grpc cu:auto table, mirroring the Solana Yellowstone pattern ($75/TB, pro-rated, [Contact us] CTA). Renames '# Sui: gRPC Methods' to '# Sui: gRPC Unary Methods' for parity with 'Solana: Yellowstone gRPC Unary Methods' and to disambiguate the two sections. Aptos: replaces the empty '# aptos-grpc API' cu:auto section with a manual '# Aptos: gRPC Streaming Methods' section using the same bandwidth format. All current aptos-grpc methods (aptos.indexer.v1.RawData/GetTransactions) are server-streaming per the isStreaming: true flag in topconfig.yml, so the cu:auto marker was empty after the workflow filter shipped. If future unary aptos-grpc methods are added to topconfig, this section can grow a companion cu:auto block then. Refs DOCS-185 Requested-by: @dslovinsky
|
Pushed 3396556 with the two manual bandwidth-priced sections you asked for @dslovinsky:
Both use the same $75/TB + Contact-us format as Note: I removed the PR #1518 can be closed as superseded once this merges. |
2 participants
🤖 Automated update of the Compute Unit Costs pricing page
This PR regenerates the per-method CU tables from Daikon topconfig (the pricing source of truth). Only content inside
cu:automarkers is touched; prose, headers, and footnotes are hand-written and preserved. See this comprehensive guide.2 sections regenerated:
sui-grpc— 3SubscriptionService/Subscribe*and 3LedgerService/List*streaming methods removed by the newisStreaming: truefilter added in OMGWINNING/dashboard#8555.aptos-grpc—aptos.indexer.v1.RawData/GetTransactionsremoved by the same filter (only method in the group, table is now empty).Manual companion sections (added on top of the Daikon regen)
Per follow-up in the Slack thread, added two hand-written bandwidth-priced sections that mirror
# Solana: Yellowstone gRPCfor the streaming methods the workflow filter now drops:# Sui: gRPC Streaming Methods— new section above the existing sui-grpccu:autotable, covering the 6 streaming methods (SubscribeCheckpoints,SubscribeTransactions,SubscribeEvents,ListCheckpoints,ListTransactions,ListEvents) at $75/TB, pro-rated, with a Contact-us CTA.# Sui: gRPC Unary Methods— renamed from# Sui: gRPC Methodsfor parity with# Solana: Yellowstone gRPC Unary Methodsand to disambiguate the two Sui sections.# Aptos: gRPC Streaming Methods— replaces the now-empty# aptos-grpc APIsection with the same bandwidth format foraptos.indexer.v1.RawData/GetTransactions.This supersedes PR #1518, which staged the same Sui rename + streaming section against a pre-filter Daikon regen and was blocked by the daily Daikon overwrite. That blocker is gone now, so #1518 can be closed as superseded once this PR merges.
Linear
DOCS-185 — https://linear.app/alchemyapi/issue/DOCS-185/split-sui-grpc-streaming-methods-into-a-separate-bandwidth-priced
Requested by
@dslovinsky (via Slack thread)
Something look wrong on the Daikon-regenerated tables? If you are an Alchemy employee please open a PR with changes in Daikon. If you are a member of the public please reach out to our team.