Arbitrum One Onchain Data
Identify what lives at a Arbitrum One address: wallet (EOA, including EIP-7702 delegation) or contract, which token standard it implements (ERC-20, ERC-721, ERC-1155), name and symbol, upgradeable-proxy implementation and admin, smart-wallet proxies, bytecode size, nonce and ETH balance.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
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.
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": {
"address": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831"
}
},
"output": {
"type": "json",
"example": {
"kind": "ERC-20 token",
"name": "USD Coin",
"chain": "arbitrum",
"proxy": {
"admin": "0x2E0A67588cfBCAD40f9e4DD76052436190A77a68",
"upgradeable": true,
"implementation": "0x86E721b43d4ECFa71119Dd38c0f938A75Fdb57B3"
},
"symbol": "USDC",
"address": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831",
"decimals": 6,
"standards": {
"erc20": true,
"erc165": false,
"erc721": false,
"erc1155": false
},
"isContract": true,
"totalSupply": "2595465640.458979",
"bytecodeBytes": 1852,
"nativeBalance": "0"
}
}
},
"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": {
"address": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{40}$",
"description": "Any 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-24 07:49Z
- Last indexed by Roundhouse
- 2026-10-26 17:20Z
- Last enriched (probe, favicon, geo)
- 2026-10-24 07:46Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 402
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
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide 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://onchaincheck.dev/arbitrum/contract, 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.