Expand Compute Unit pricing page with new chains and endpoints

[silviu-androne]

Description

Update pricing page with new networks and methods for a better coverage. Used sources:

• topconfig: https://github.com/OMGWINNING/chain-config/blob/master/src/main/resources/configs/chainconfig/topconfig/topconfig.yml
• https://www.notion.so/alchemotion/Node-API-Methods-Support-Audit-Tracker-229069f20066806493cdf9e61138dabc

Related Issues

Changes Made

• Added the methods mentioned on the Node-API-Methods-Support-Audit-Tracker doc
• Added CUs for: Beacon, Aptos, Bitcoin, Celestia, Sui and Tron

Testing

• I have tested these changes locally
• I have run the validation scripts (pnpm run validate)
• I have checked that the documentation builds correctly

[github-actions]

🌿 Documentation Preview

Name	Status	Preview	Updated (UTC)
Alchemy Docs	✅ Ready	🔗 Visit Preview	Nov 3, 2025, 3:36 PM

[Copilot]

Pull Request Overview

This PR expands the Compute Unit pricing documentation by adding pricing information for newly supported blockchain networks and API methods. The changes provide comprehensive coverage of API endpoints across multiple chains to improve developer understanding of costs.

Key Changes

• Added new Ethereum JSON-RPC methods including blob fee APIs and extended trace methods
• Added complete pricing tables for six new blockchain networks: Beacon, Aptos, Bitcoin, Celestia, Sui, and Tron
• Added Arbitrum-specific trace API methods with their respective CU costs

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The throughput CU value '-' is inconsistent with the pattern used in the rest of the table. Consider using an empty cell or a numeric value (0 or N/A) to maintain consistency with other entries that have defined throughput CU values.

Suggested change

	| eth\_submitWork | 20 | - |
	| eth\_submitWork | 20 | |

[Copilot]

The CU and throughput CU values for trace_callMany (80, 3000) differ from the pattern of other trace methods. Verify these values are correct, as trace_call has CU=40 and throughput CU=40, which might suggest trace_callMany should follow a similar proportional pattern.

Suggested change

	| trace\_callMany | 80 | 3000 |
	| trace\_callMany | 40 | 40 |