Skip to main content
Usage is metered in credits. Every priced call, every second a push socket is held open, and every byte delivered on a channel draws from your plan’s monthly credit allowance. A call costs the same whichever transport it arrives on. Socket.IO, HTTP, and batch all address a route by the same path, so they are billed identically.

Request Costs

Requests are charged per call, at one of four rates. Free calls are still recorded, and they are still blocked once an account is out of credits.

SVM (Solana) Endpoints

Subscribing and tracking are free calls. The cost of a price subscription is the bytes its priceUpdate events deliver; the cost of a tracked wallet is the standing charge below.

EVM Endpoints

Registering and removing an auto-snipe watch are free. The watch itself is billed per minute as standing work, and its signals are billed on the bytes they deliver.

TVM Endpoints


Transaction Logs


Connection Costs

Holding a push socket open costs 1 credit per connected minute, charged once per connection no matter how many channels it subscribes to. Two sockets open at the same time cost twice as much, because that is two connections alive.

Channel Costs

Delivered events are charged on bytes, at 1 credit per 3.5 MB (about 286 credits per GB). Time is not charged again here - that is the connection meter’s job - so a socket subscribed to several channels is not billed for its duration more than once.

Standing Work

Some features cost while they exist, not when they are called. These are billed by how long each item is registered, the way instance-hours are billed. Fifty tracked wallets held for one minute costs 100 credits, not 2. These charges continue until the wallet is untracked or the watch is removed or expires, and they are not attributed to any one API key - revoking a key does not stop them.
Standing work accrues whether or not you call the API. A tracked wallet left registered for a month costs 86,400 credits.

Running Out of Credits

When an account passes its monthly allowance plus its overage grace, priced routes are rejected with CREDIT_LIMIT_EXCEEDED and HTTP 402. Free routes such as unsubscribe, untrack, and auto-snipe remove keep working, so you can always wind standing work down. Retrying does not help. The block clears when the calendar month rolls over in UTC, or when the plan changes. See Error Handling for the response shape.