Skip to content

docs(pricing): first generated Compute Unit Costs update (drift audit)#1425

Draft
SahilAujla wants to merge 1 commit into
dx-3112-cu-costs-markersfrom
dx-3112-cu-costs-first-generation
Draft

docs(pricing): first generated Compute Unit Costs update (drift audit)#1425
SahilAujla wants to merge 1 commit into
dx-3112-cu-costs-markersfrom
dx-3112-cu-costs-first-generation

Conversation

@SahilAujla

@SahilAujla SahilAujla commented Jul 4, 2026

Copy link
Copy Markdown
Collaborator

Description

Stacked on #1424 (the marker PR) — merge that first; this PR's diff then shows exactly what the automation changes.

This is the first generated output of UpdateComputeUnitCostsFromDaikonWorkflow (OMGWINNING/dashboard#8087), produced by running the workflow's generator locally against the latest chain-config topconfig (1100 methods). It serves as the drift audit from the ticket's acceptance criteria: every diff against the hand-maintained tables is a pre-existing inaccuracy or omission that the daily automation will keep fixed. Once the workflow is deployed and scheduled, PRs identical to this one arrive automatically on bot/daikon-cu-costs-update.

Drift audit summary

Coverage: 658 → 1038 table rows. 382 billed methods were missing from the page entirely, 53 rows had wrong values, 1 row is removed.

12 new sections auto-created (inferred titles — please review naming/placement; renaming headers or moving blocks is safe, the marker carries the key):

  • TON (61 methods), Avalanche P-Chain (26), Tendermint (24), Polkadot (2), Optimism-specific (4), HyperEVM (5), Arc (1)
  • Bitcoin Indexer REST (35, Esplora-style indexer group), Celestia gRPC (40, celestia.*/cosmos.* services), Sui gRPC (22), Solana Yellowstone gRPC unary (7)
  • all API (2 internal-looking methods create_file/upload_metadata, cu=0) — needs a human decision on naming/placement

Notable value corrections (topconfig is the billing source of truth):

  • eth_sendRawTransaction Throughput CU 250 → 50, eth_sendRawTransactionSync 250 → 125
  • starknet_blockNumber/starknet_blockHashAndNumber CU 20 → 10
  • getNFTsForContract Throughput CU 50 → 100
  • Solana getSupply/getProgramAccounts/getInflationReward gained real throughput values (800/117/300)
  • Prices API rows gained Throughput CU 20; Portfolio rows gained their (oddly low) explicit values of 1
  • Trace/Arbtrace/Gas-Manager rows that showed Throughput CU equal to CU are now blank per the rule "only show when explicitly set AND differing" (rateLimitComputeUnits defaults to computeUnits, so equal values carry no information)

Removals (both verified intentional):

  • suix_getLatestBridge — marked METHOD_PRERELEASE in topconfig; the page only lists public methods
  • Portfolio's /transactions/history/by-address is a rename to transactions/history/by-address (path normalization), not a removal

Formatting normalization: uniform \_ escaping (the Wallet section was inconsistent), deterministic row sort (CU ascending, then name), NFT/signer/prices/portfolio rows keep their public display names via the workflow's display-name map.

Flagged, not on the page: /tx (custom method shared by Celestia consensus + Bitcoin) resolves to no product tag — the workflow Slack-alerts this; it needs a manual override decision.

Found in the process: likely topconfig typo aarbtrace_rawTransaction (double "a") — appears as a new Arbtrace row here; should be fixed in Daikon.

Test Plan

  • Output produced by the exact generator code in OMGWINNING/dashboard#8087 (232 unit tests passing there)
  • prettier --check passes
  • Regeneration over this output is idempotent (second run produces zero diff)
  • All content outside cu:auto markers verified byte-identical to the marker PR
  • Human review of auto-created section titles/placement (especially all API)

LINEAR TASK: https://linear.app/alchemyapi/issue/DX-3112/automate-the-compute-unit-costs-pricing-page-from-daikon-topconfig

Output of UpdateComputeUnitCostsFromDaikonWorkflow's generator run against
latest chain-config topconfig (1100 methods). This is the drift audit PR:
every diff against the hand-maintained tables is a pre-existing inaccuracy
or omission the automation fixes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jul 4, 2026

Copy link
Copy Markdown

🔗 Preview Mode

Name Status Preview Updated (UTC)
Alchemy Docs ✅ Ready 🔗 Visit Preview Jul 4, 2026, 3:40 AM

@SahilAujla

Copy link
Copy Markdown
Collaborator Author

@codex review

@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: c807093cad

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

| getTransaction | 40 | |
| getTransactionsForAddress | 100 | |
| getSupply | 160 | 800 |
| alchemy\_requestFeePayer\_prefundRent | 1250 | 100 |

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 Keep prefund billing variants off method tables

This row turns an override key into a public Solana JSON-RPC method even though the page already documents the real API as alchemy_requestFeePayer with prefundRent = true; repo-wide search only finds alchemy_requestFeePayer_prefundRent in this generated table and the OpenRPC ignore list, not in the public wallet docs. Users copying the method name from the pricing table would call a billing variant instead of the supported method, so render this as a note/override on alchemy_requestFeePayer instead of a row.

Useful? React with 👍 / 👎.

Comment on lines +1105 to +1106
| create\_file | 0 | 50 |
| upload\_metadata | 0 | 50 |

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 Filter catch-all internal methods from public pricing

The generated all product is a Daikon catch-all, not a customer-facing API family: a repo-wide search for these method names only finds them in this new table, with no corresponding API docs or specs. Publishing them under a generic all API heading exposes internal billing keys as methods users cannot discover or call, so the generator should filter this product or map it to a reviewed public section before landing.

Useful? React with 👍 / 👎.

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