Roundhouse

Arbitrum One Onchain Data

Native ETH balance of a Arbitrum One wallet plus the balances of up to 20 ERC-20 tokens you list, formatted with each token's symbol and decimals, read live from Arbitrum One.

DataLiveeip155:8453Exactvia cdp
https://ca-tax-api-mainnet.lxtap.workers.dev/arbitrum/balances
ArbitrumOnchainerc20TokenWallet
Calls · 30d
2
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 7 snapshots so far.
$2.05
Verified settled volume
276 settlements proven x402 by their on-chain EIP-3009 marker.
$0.0050
Listed price
As published in the catalog. Always read the live 402 before paying.
2
Calls · 30d
Upstream's own call count for this endpoint, not ours.
2
Unique payers · 30d
Last called 2026-10-23 08:16Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x2ECB9E1fcca7A62758c679F11bC3241466d181d8

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.005USDC≈ $0.005 USD
on Base · exact scheme

Pay 0.005 USDC on Base to 0x2ECB…181d8. The signed payment is good for 5 minutes.

Paid to
0x2ECB…181d8
USD Coin contract
0x8335…02913
Payment window
5 minutes
As published
5000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2"
    },
    "payTo": "0x2ECB9E1fcca7A62758c679F11bC3241466d181d8",
    "amount": "5000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "type": "http",
        "method": "GET",
        "queryParams": {
          "tokens": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831,0x912CE59144191C1204E64559FE8253a0e49E6548",
          "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
        }
      },
      "output": {
        "type": "json",
        "example": {
          "chain": "arbitrum",
          "tokens": [
            {
              "raw": "158162265",
              "token": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831",
              "symbol": "USDC",
              "balance": "158.162265",
              "decimals": 6
            },
            {
              "raw": "23671066717268252605",
              "token": "0x912CE59144191C1204E64559FE8253a0e49E6548",
              "symbol": "ARB",
              "balance": "23.671066717268252605",
              "decimals": 18
            }
          ],
          "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
          "nativeSymbol": "ETH",
          "nativeBalance": "0.159411760906900921"
        }
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method"
          ],
          "properties": {
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "GET"
              ],
              "type": "string"
            },
            "queryParams": {
              "type": "object",
              "required": [
                "address"
              ],
              "properties": {
                "tokens": {
                  "type": "string",
                  "pattern": "^(0x[0-9a-fA-F]{40})(,0x[0-9a-fA-F]{40}){0,19}$",
                  "description": "Comma-separated ERC-20 contract addresses on Arbitrum One, up to 20"
                },
                "address": {
                  "type": "string",
                  "pattern": "^0x[0-9a-fA-F]{40}$",
                  "description": "Wallet address on Arbitrum One"
                }
              },
              "additionalProperties": false
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-10-23 08:16Z
Last indexed by Roundhouse
2026-10-26 17:20Z
Last enriched (probe, favicon, geo)
2026-10-22 20:17Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 402
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 7 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service Arbitrum One Onchain Data and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Arbitrum%20One%20Onchain%20Data'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://ca-tax-api-mainnet.lxtap.workers.dev/arbitrum/balances, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.