Skip to main content

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. Every response names it in x-lasso-access. Use this page to choose a pool and predict your bill.

The three kinds of serving access

Your URL names the profile, and your account’s payment state decides how it is served: Name public for traffic that doesn’t need premium providers, such as background jobs or development. Same key, different profile 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 like eth_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. Every response states its size in x-lasso-cu and its charge in x-lasso-usd. 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. Lasso charges only successful results. Every final JSON-RPC error is free, including execution reverts and provider rate-limit errors after failover, and so is any request refused before routing. Money is always in USD: prices, balances, purchases and charges. Included usage, from free access or a subscription, is counted in CU per month.

Current tariff

Subscription prices are on lasso.sh/pricing, and agent.json publishes the live values agents act on.

Subscriptions and free access

Free access belongs to accounts a person has joined. Your first account is sponsored when you create or claim it, and you can sponsor two more. A provisional account an agent created gets free access once a person claims it.

Rate limits

Limits apply per account, not per key:
  • One managed bucket holds every premium and public request 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.
  • public requests 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 bucket while it serves custom: 1,000 RPS with bursts to 2,000. For a higher limit, email support@lasso.sh.
Every response carries the IETF 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 with Retry-After. For higher limits, ask Lasso support for an account override.

Limits

  • public, payment fallback and free access serve load-balanced only; lasso_meta.strategy reports the strategy used.
  • Public providers can cover fewer methods and less history than the premium pool.
  • Custom traffic has no request price; your providers bill you as usual.

Next