Quickstart

Start Lasso RPC Core

Follow Installation to start the v0.5.0 container or run from source. The included public profile is ready to try without provider keys.

Make your first requests

Request the latest Ethereum block number:

curl --fail-with-body --silent --show-error http://localhost:4000/rpc/ethereum \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

A successful response contains a hexadecimal block number; the value changes:

{"jsonrpc":"2.0","id":1,"result":"0x18ba3fb"}

The health endpoint checks the application. This RPC request also exercises an upstream provider. Public providers have their own availability and rate limits. For WebSocket subscriptions, use the dashboard tester or run wscat with Node.js and npm:

npx --yes wscat -c ws://localhost:4000/ws/rpc/ethereum

At its > prompt, send:

{"jsonrpc":"2.0","method":"eth_subscribe","params":["newHeads"],"id":1}

Expect a subscription ID followed by eth_subscription notifications as blocks arrive. Press Ctrl+C to disconnect. To inspect routing decisions, add ?include_meta=headers to an HTTP request URL and -i to curl. See the API reference for metadata fields and error responses.

Choose a route

Use /rpc/fastest/ethereum, /rpc/load-balanced/ethereum, or /rpc/latency-weighted/ethereum for explicit strategies. Use /rpc/profile/my-app/ethereum for a configured profile named my-app. WebSocket routes use the /ws/rpc/ prefix. Provider health, method support, and configured limits constrain selection. Routing cannot create upstream capacity or guarantee a provider supports every parameter combination. See Configuration, HTTP endpoints, and Docker deployment.

Get Started

Core Concepts

Configuration

Deployment

Observability

Advanced

Start Lasso RPC Core

Make your first requests

Choose a route

​Start Lasso RPC Core

​Make your first requests

​Choose a route

Start Lasso RPC Core

Make your first requests

Choose a route