MeterCall L4 · BUILD

Build products on L4.

The layer every new crypto app will sit on. Your agent, your dashboard, your bot — all on one endpoint, 30+ chains, zero RPC juggling.

Get an API key Open playground

Quickstart

Five steps. The first four take under a minute. Number five is on you.

STEP 1
Get an API key

Sign up, grab a key at /keys.

STEP 2
Make your first call

One curl, one chain, one balance.

STEP 3
Try cross-chain

Same address, every chain at once.

STEP 4
Deploy

Static HTML or a full backend — your call.

STEP 5
Earn

Publish as a module — we revenue-share on popular ones.

// step 2 — first call (Node)
const l4 = new MeterCallL4({ key: process.env.MC_KEY });
const bal = await l4.balance("ethereum", "0xd8dA…6045");

// step 3 — cross-chain, same address
const all = await l4.crossBalance("0xd8dA…6045");
// → [{ chain:"ethereum", amount:1246.3, usd_value:... }, { chain:"arbitrum", ... }, ...]

Starter templates

Fork any of these. Each is a single HTML file or a 50-line script — ready to customize.

Multi-chain balance dashboard

One address → balances on every chain, USD-rolled, auto-refreshing. Static HTML.

Cross-chain gas optimizer

"Where's the cheapest place to move $X?" — fetches gas across EVM chains in one call.

NFT sniper bot

Polls floor price on every marketplace on every chain. Webhook on threshold.

DCA bot across chains

Executes recurring buys on the cheapest chain of the moment. Pay per call.

Yield aggregator

Top 500 pools by APY via /v1/l4/protocols/top. Sortable, filterable, fast.

Chain-agnostic ENS tool

One name → resolved on every supported chain. Single /v1/l4/ens call.

What's in it for you

Every reason you'd build on L4 instead of wiring 30 RPCs yourself.

$
Revenue share

Publish a module. When others use it, we split the meter.

0
Zero infra

No nodes, no RPC providers, no Kubernetes. Just calls.

30+
Chains out of box

Every major chain. Add one tomorrow — we handle it.

R
No RPC management

We do failover, retries, rate limits across providers.

K
One key

Not 30 API keys to juggle. Not 30 invoices. One.

Your usage

Calls (30d)
Chains touched
Avg latency
Spend (30d)

Sign in to see live numbers — /login.

Keep going

copied to clipboard