MeterCall

Why teams leave Across for MeterCall

Across is one of the fastest intents-based bridges — UMA-secured, capital-efficient. MeterCall is the API call meter; they do one thing, we do 2,400.

All comparisons vs Across Migrate
Switch in 5 minutes → All comparisons

Side by side

DimensionMeterCallAcross
Primary scope2,400-module API meterFast intents bridge
Use caseAPI calls for agentsToken bridging with speed
Latency<200ms per callSeconds–minutes per bridge
Pricing$0.001/callBridge fee + spread
Agent-payx402 liveTransaction-bound
Chain coverage30+ RPC~12 chains for bridging

Where Across still wins

  • Bridge speed. Across intents settle fast — sometimes seconds. Hard to beat on that axis.
  • Capital efficiency. UMA-based optimistic verification keeps liquidity working.
  • Narrow focus. They are not trying to be a platform — they bridge. Well.

Across is the right answer for fast bridging. MeterCall is the right answer for the 2,399 other things an agent calls between bridges.

Where MeterCall wins — with specifics

  • Breadth. Across is one primitive. MeterCall is 2,400 on a single meter.
  • Flat pricing per API. $0.001 is $0.001. Bridge spreads can surprise you.
  • Agent-pay everywhere. x402 on any API call — Across doesn't solve agent-pay outside bridge txs.

Migrate from Across

Not a migration. Keep Across for bridging. Add MeterCall for the rest.

Switch in 5 minutes → See all comparisons