One endpoint for all your RPC
A single provider URL fails whenever that provider does: an outage, a rate limit, a slow region or a method it doesn’t serve becomes your app’s error. Lasso replaces it with one standard JSON-RPC endpoint that routes every request across a pool of providers. It measures each provider’s latency and health per kind of request, orders them by the strategy you pick, and fails over before your app sees the error. Every response says what served it and what it cost. Your app keeps speaking JSON-RPC; only the URL changes. An agent can create a working endpoint with one HTTP request and no signup:How a request flows
- Profile: Lasso’s
premiumpool, itspublicpool, or a Custom profile over your own nodes and provider accounts. One key reaches all of them. - Strategy, per call site:
load-balanced,balanced-fast,fastestorpriority. - Chain: any EVM chain Lasso serves, or any your own providers serve.
When Lasso fits
What your app keeps
Lasso routes requests; your app keeps the parts that depend on its own state:- Transactions. Lasso resends identical signed bytes to up to three providers when one fails. Signing, nonces, replacement and finality stay with your app. See transactions.
- Log scans. Use
eth_getLogsor subscriptions; HTTP filter IDs live on one provider, so Lasso doesn’t serve them. - Provider limits. Historical depth and
eth_getLogsrange caps follow the providers in the pool.
How you pay
Premium requests are priced in USD by method and strategy, drawn first from included usage, then from the account’s balance. An account that has paid keeps serving on public providers for 30 days if its balance runs out. An account a person has joined gets a free monthly allowance on public providers. See serving access and pricing.Two ways in, one account
A person can claim what an agent built without changing a single URL. See
accounts, people and agents.
Next
- Quickstart: a working endpoint in one request.
- Set up production RPC with an agent: keys per environment, one balance, a handoff.
- Routing: how selection and failover work.
- Chains and prices: every chain Lasso serves.
- Lasso RPC Core: run the routing engine yourself.