Skip to content

Subscriptions API Compute Unit Cost Update #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dericksozo merged 1 commit into from
Nov 27, 2025
Merged

Subscriptions API Compute Unit Cost Update #124

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions compute-units.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Compute Units (CUs) are how we measure API usage in Sim. CUs reflect the actual
| Transactions (EVM & SVM) | Fixed | 1 compute unit per request | — |
| Token Info | Fixed | 2 compute units per request, even though `chain_ids` is required | — |
| Token Holders | Fixed | 2 compute units per request | — |
| Subscriptions | Event-based | 1 compute unit per event sent to your webhook. Note that a single webhook payload can contain multiple events. | All supported EVM chains (varies by subscription type) when chain_ids is omitted |
| Subscriptions | Event-based | 2 compute units per event sent to your webhook. Note that a single webhook payload can contain multiple events. | All supported EVM chains (varies by subscription type) when chain_ids is omitted |

## How CUs work

Expand Down Expand Up @@ -57,7 +57,7 @@ Chain count is computed after we expand any tags you pass. To keep CU predictabl
Token Info is fixed-cost per request, even though `chain_ids` is required. CU does not scale with the number of chains.
</Card>
<Card title="Subscriptions: event-based cost">
Each event sent to your webhook consumes 1 CU. A single webhook payload may contain multiple events, resulting in multiple CUs per webhook delivery.
Each event sent to your webhook consumes 2 CUs. A single webhook payload may contain multiple events, resulting in multiple CUs per webhook delivery.
</Card>

</Columns>
Expand Down
2 changes: 1 addition & 1 deletion evm/subscriptions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ You can set up and manage your subscriptions in two ways:

## Compute Unit Cost

The Subscriptions API costs **1 CU per event** sent to your webhook. Note that a single webhook call may include multiple events. For example, multiple balance changes or transactions.
The Subscriptions API costs **2 CUs per event** sent to your webhook. Note that a single webhook call may include multiple events. For example, multiple balance changes or transactions.

If you omit `chain_ids` when creating a webhook your subscription watches all supported EVM chains for matching events. You are only charged per event received regardless of how many chains are monitored.

Expand Down