​

Routing evidence

curl -sS -D - "$LASSO_RPC_URL/fastest/base?include_meta=body" \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

x-lasso-request-id: 01J9Z…
x-lasso-access: premium
x-lasso-cu: 2
x-lasso-usd: 0.00001
x-lasso-balance-usd: 19.87421

{
  "jsonrpc": "2.0", "id": 1, "result": "0x3157d37",
  "lasso_meta": {
    "strategy": "fastest", "chain_id": 8453,
    "candidate_providers": ["premium/premium_base_2:http", "premium/premium_base_1:http"],
    "selected_provider": { "id": "premium_base_2", "protocol": "http" },
    "upstream_latency_ms": 9.4, "lasso_overhead_ms": 1.9, "retries": 0
  }
}

​

Where evidence lives

​

Debug a request

1. Capture x-lasso-request-id at your client.
2. Check x-lasso-access and x-lasso-fallback: was it served where you expected, and if not, why?
3. Read lasso_meta: which strategy applied, which providers were candidates, which one served it, and how many retries it took.
4. For an error Lasso originates, read error.data.code and error.data.next_action; they name the fix. Provider errors keep their code and message.
5. Check the key’s recent_errors and the dashboard’s provider health for a pattern across requests.

POST https://lasso.sh/api/v1/feedback
Content-Type: application/json

{"message": "eth_getLogs on base returned -32005 for a 500-block range", "category": "rpc", "request_id": "01J9Z…"}

​

Limits

• Managed providers appear under public aliases such as premium_base_2; Custom profiles show your own provider names.
• candidate_providers lists the order considered, not the attempts. Use selected_provider and retries.
• An HTTP batch’s x-lasso-meta header describes one item. Use include_meta=body to see every item’s evidence.
• Usage views summarize activity for insight; the account balance is the record of money.
• The dashboard’s recent activity is a live stream, not a request log.

​

Next

• Response signals and errors: every header, field and code.
• Routing: what the evidence means.
• Balance and payment fallback: watching spend.

​

Understand latency