Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -373,15 +373,15 @@ Similar to the [NFT API](/docs/reference/compute-unit-costs#nft-api), the Wallet

# Webhooks and Subscription APIs

[Webhooks](/docs/reference/notify-api-quickstart) and [WebSocket Subscriptions](/docs/websocket-subscriptions) on Alchemy are priced based on **bandwidth:** the amount of data delivered as part of the subscription.
[Webhooks](/docs/reference/notify-api-quickstart) and [WebSocket Subscriptions](/docs/websocket-subscriptions) on Alchemy are priced based on **bandwidth** (the amount of data delivered) by default, except for Base Flashblocks subscriptions, which are priced **per event**.

Each subscription type is priced identically per byte:
| Subscription | Pricing |
| ------------------------- | -------------- |
| newFlashblockTransactions | 40 CU / event |
| newFlashblocks | 60 CU / event |
| All other subscriptions | 0.04 CU / byte |

| Bandwidth | CU |
| --------- | --- |
| 1 byte | .04 |

On average, a typical webhook or WebSocket subscription event is about 1000 bytes, so it would consume 40 compute units. Note that this can vary significantly based on the specific event delivered [Subscription API Quickstart](/docs/reference/subscription-api)
On average, a typical byte-priced webhook or WebSocket subscription event is about 1000 bytes, so it would consume 40 compute units. Note that this can vary significantly based on the specific event delivered. See the [Subscription API Quickstart](/docs/reference/subscription-api) for details.

# Polygon PoS: Specific Methods

Expand Down
Loading