Skip to main content

​
First endpoint quickstart

This flow evaluates Lasso with a standard JSON-RPC call. Creating an external key changes service state; an agent should ask before doing it for a user.

​
1. Check live support

Choose a chain and an explicit strategy. The runtime default is load-balanced, but an explicit URL makes the evaluation reproducible.

​
2. Create and save a key

The response includes a full key and a ready-to-use endpoint. The full key is shown once. Put it in the project’s existing secret store; do not print it into chat, logs, shell history, screenshots, or source control. Load the key from the project’s secret manager. For a one-off interactive shell, read it without echoing it or placing the value in shell history:

​
3. Make a harmless call

The body remains standard JSON-RPC. include_meta=headers adds a request ID and encoded routing metadata without changing the body shape. Anonymous keys can also receive per-request CU and USD headers. See Routing and usage evidence before building automation around a header.

​
4. Install the URL

Lasso replaces the upstream URL; the client remains standard EVM JSON-RPC.
For viem:
Begin with a non-critical stateless read path. Compare results, latency, and routing evidence before expanding traffic or adding historical, write, filter, or subscription workloads. An anonymous key can be linked to a dashboard account without changing its RPC URL:
Give the short-lived claim_url to the user. Linking adds the account management surface; it should not be performed without the user’s approval. For exact key, funding, claim, and session-payment payloads, use /openapi.json and /SKILL.md.