Skip to main content

​
Trial your own providers behind Lasso

An agent can put your existing provider accounts and nodes behind Lasso, prove it works on your app’s real traffic, and hand you the result, all before anyone signs up. This guide builds a Custom profile from a provisional account, routes the app’s key over it, and verifies failover.

​
1. Create an endpoint

Put rpc_url in the app’s secret store. The profile steps below use the response’s management_token, which makes you the account’s agent.

​
2. Dry-run the profile

List the provider URLs the app already uses. A dry run checks each provider’s chain identity and stores nothing, so it needs no payment:
Each provider comes back verified, verifying (didn’t answer yet) or failed (wrong chain). Fix any failure before you pay. Start with URLs only; add limits only for a cap you know, such as your plan’s log span. Lasso learns the rest from traffic.

​
3. Custom access for the trial

Holding a profile needs Custom access, but a provisional account that has never had it gets five free days the moment it saves its first profile below — no payment needed for this trial. GET /api/v1/accounts/{account_id} shows when they end under subscriptions. If this account already used its free days, or the trial needs longer than five days, buy more with the user’s wallet, within their approved budget:
The 402 exchange is the same as a balance top-up: sign one x402 or MPP challenge and repeat the request with it. The per-day price and day range are in agent.json. Traffic on your own providers has no request price.

​
4. Save it and route the key over it

Repeat the PUT without dry_run. Then point the app at the profile’s URL: replace the /profile/premium segment in rpc_url with /profile/prod-base.

​
5. Verify on real traffic

Confirm x-lasso-access: custom and a selected_provider from your list. Then run the app’s own reads, its largest eth_getLogs range and any historical queries through the profile. Compare latency, errors and head freshness with the direct provider URLs. To see failover, pin each provider once with $LASSO_RPC_URL/provider/primary/base, then watch which provider serves the unpinned URL while one of them is throttled or down.

​
6. Hand it over

Request a claim link and give it to your user privately:
When they claim it, the profile, its Custom access, the key and its URL come with it. If they add it to an account that already has a prod-base profile, the incoming one is renamed and the app’s URL keeps reaching it.

​
Choose behavior for your workload

​
Limits

  • Custom access is per account and covers up to five Custom profiles. When the trial’s days run out, the profile is kept and its URLs serve from Lasso’s premium pool, charged at request prices from the balance and marked x-lasso-fallback: profile, until access is renewed.
  • Two URLs on the same provider account, region or plan can fail together. Test the failure you need to survive.
  • A dry run checks chain identity only. Archive coverage, WebSocket support and method coverage come from testing and from what Lasso learns over time.
  • Your upstream providers still bill you for the traffic they serve.

​
Next