Quickstart
Create an endpoint, call it, and put it in your app. It takes one HTTP request and no signup, so an agent can do every step. Prefer a browser? Sign in at lasso.sh, create an endpoint, and skip to step 3; it serves on public providers under your free monthly allowance until you add balance or subscribe to Pro.1. Create an endpoint
rpc_url as LASSO_RPC_URL, and keep management_token private: it lets you
add keys, build Custom profiles and hand the account to a person later.
If the response is 202 with serving_ready: false, wait Retry-After
seconds, then send the RPC call below to the saved rpc_url. Retry RPC if
it is still pending, honoring Retry-After; the key already exists.
2. Call it
Append a chain torpc_url, and optionally a strategy before it:
lasso_meta names the provider that served the call and where the time went.
Every response also carries x-lasso-usd, what the call cost, and
x-lasso-balance-usd, what’s left.
For free Ethereum RPC, save the returned key as LASSO_RPC_KEY and derive
the public path from rpc_url. The premium path uses the starting balance;
public providers have no request charge.
3. Put it in your app
--rpc-url), Hardhat and indexers take the same URL; use
${LASSO_WS_URL}/base for subscriptions. Install Lasso has
an example for each.
4. Pick a strategy per call site
The strategy is a URL segment, so each call site can choose its own:
To route over Lasso’s public providers at no charge, replace
/profile/premium
with /profile/public. Routing explains each strategy and
keys and profiles each pool.
5. Fund it
The starting balance covers a few thousandeth_blockNumber calls. To add more, credit the
account with USDC from the wallet your user approved:
402 with a standard x402 or MPP challenge. Sign it with a stock
client and repeat the request. Top up has
a complete example, and people can add balance or subscribe to Pro in the
dashboard.
Limits
- Creating endpoints without credentials is limited to 10 per hour per client IP.
- No Lasso credential can spend money; every payment needs a wallet signature.
Next
- Set up production RPC with an agent: keys per environment, one balance, and a handoff to your team.
- Bring your own providers: route over the provider accounts and nodes you already pay for.
- Serving access and pricing: what each request costs.