Serving access and pricing
Every request Lasso serves has one serving access:premium, public or
custom. It decides which providers answer, what the request costs, which
strategies apply and which rate limit counts it, and every response tells you
which one served it. Read this page to choose a pool and predict your bill;
read balance and payment fallback for what
happens when money runs out.
The three kinds of serving access
Your URL names the profile, and your account’s payment state decides how it is
served:
Choose
public explicitly for traffic that doesn’t need premium providers:
background jobs or development. Same key, different path
segment:
What a premium request costs
A request’s size in compute units (CU) is its method weight times its strategy factor. Its price is that CU at a published USD rate. A cheap read likeeth_blockNumber weighs less than eth_getLogs, and a trace weighs
more. The strategy factor is the trade you make between latency and cost:
Every method’s weight and price is in
chains and prices, generated from the
live
agent.json. Every response states its
size in x-lasso-cu and its charge in x-lasso-usd, so nothing is a surprise.
A batch is priced per item, a WebSocket request costs the same as over HTTP,
and each subscription notification is priced as an eth_subscription entry.
Money is always in USD: prices, balances, purchases and charges. Included
usage, from free access or a subscription, is counted in CU per month.
Lasso charges only for a response a provider delivered, whether a result or a
JSON-RPC error. A failure inside Lasso with no provider response, and any
request refused before routing, is free.
Current tariff
Subscription prices are on lasso.sh/pricing.
agent.json publishes the live values agents act on.
Subscriptions and free access
Free access belongs to accounts that a person has joined. When you sign in
and create or claim your first account, you sponsor it, and you can sponsor
two more. A provisional account an agent created has no free access until a
person claims it.
Current subscription prices and allowances are on
lasso.sh/pricing and in
agent.json.
Rate limits
Limits apply per account, not per key:- One managed bucket holds every
premiumandpublicrequest from all of the account’s keys: 100 RPS with bursts to 200 while the account has premium access, or 30 RPS with bursts to 60 while payment fallback or free access serves it. publicrequests also draw on a public bucket inside it: 30 RPS with bursts to 60. Public traffic can never take more than 30 of your 100 premium RPS.- Each Custom profile has its own 1,000 RPS bucket while it serves
custom.
RateLimit-Policy and RateLimit headers,
named after the bucket that bound the request: managed, public or the
Custom profile’s slug. "public";q=60;w=2 means 60 requests per two seconds. Over the
limit, Lasso answers 429 rate_limit_exceeded with Retry-After. Need more? Ask
Lasso support for an account override.
Limits
publicservesload-balancedonly. A request for another strategy is served asload-balanced, andlasso_meta.strategyreports what was used. The same holds for any request served by payment fallback or free access.- Public providers’ method coverage and historical depth can be narrower than the premium pool’s.
- Custom traffic has no request price; your providers bill you as usual.
Next
- Balance and payment fallback: where the money comes from and what happens at zero.
- Keys, URLs and profiles: default profiles and scoped keys.
- Chains and prices: the live price table.