agent.pocket.network
https://agent.pocket.network/v1/arb-oneShares a payout wallet with 129 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Read-only JSON-RPC access to Arbitrum One, the Nitro optimistic rollup on Ethereum, served by the Pocket Network decentralised supplier set. Pay per request in USDC; no account, no API key.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 119ms · p95 137msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 11/14/2026, 2:00:00 AM | 100% | 1 | 119ms |
| 11/16/2026, 11:00:00 AM | 100% | 1 | 139ms |
| 11/18/2026, 3:00:00 PM | 100% | 1 | 117ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 67
- Activity
- 15
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 60% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- GoDaddy.com, LLC
- Domain registered
- 2024-02-23
- Hosting network
- DE-HETZNER-20120425
- Hosting country
- DE
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 11/18/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 10/20/2026 | 4,333 | 21.67 | 50 |
| 10/21/2026 | 4,146 | 20.73 | 47 |
| 10/22/2026 | 3,830 | 19.15 | 51 |
| 10/23/2026 | 4,380 | 21.9 | 52 |
| 10/24/2026 | 4,353 | 21.77 | 47 |
| 10/25/2026 | 5,429 | 27.15 | 55 |
| 10/26/2026 | 4,574 | 22.87 | 51 |
| 10/27/2026 | 4,453 | 22.27 | 60 |
| 10/28/2026 | 4,467 | 22.34 | 60 |
| 10/29/2026 | 4,224 | 21.12 | 61 |
| 10/30/2026 | 4,160 | 20.8 | 55 |
| 10/31/2026 | 4,139 | 20.7 | 54 |
| 11/1/2026 | 4,066 | 20.33 | 63 |
| 11/2/2026 | 3,966 | 19.83 | 54 |
| 11/3/2026 | 4,080 | 20.4 | 58 |
| 11/4/2026 | 3,802 | 19.01 | 44 |
| 11/5/2026 | 3,847 | 19.24 | 51 |
| 11/6/2026 | 3,755 | 18.78 | 52 |
| 11/7/2026 | 3,737 | 18.69 | 45 |
| 11/8/2026 | 3,981 | 19.91 | 48 |
| 11/9/2026 | 3,643 | 18.22 | 46 |
| 11/10/2026 | 4,020 | 20.1 | 48 |
| 11/11/2026 | 4,180 | 20.9 | 51 |
| 11/12/2026 | 4,093 | 20.47 | 56 |
| 11/13/2026 | 3,986 | 19.93 | 53 |
| 11/14/2026 | 4,020 | 20.1 | 52 |
| 11/15/2026 | 3,992 | 19.96 | 54 |
| 11/16/2026 | 4,107 | 20.54 | 63 |
| 11/17/2026 | 4,137 | 20.69 | 58 |
| 11/18/2026 | 3,084 | 15.42 | 55 |
This payout wallet is shared: figures cover all 130 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.
Response schema
{
"description": "JSON-RPC 2.0 response envelope. Exactly one of `result` or `error` is present. `result` takes the shape the called method defines: hex-encoded quantities and byte strings per the Ethereum JSON-RPC specification, an object for block and receipt reads.",
"examples": [
{
"id": 1,
"jsonrpc": "2.0",
"result": false
}
],
"properties": {
"error": {
"description": "Present instead of `result` when the call failed",
"properties": {
"code": {
"description": "A JSON-RPC 2.0 error code",
"type": "integer"
},
"data": {
"description": "Method-specific detail, when the node supplies it"
},
"message": {
"type": "string"
}
},
"type": "object"
},
"id": {
"description": "The request id, echoed back",
"type": [
"string",
"number",
"null"
]
},
"jsonrpc": {
"description": "The protocol version, always \"2.0\"",
"type": "string"
},
"result": {
"description": "The method's result, in the shape the called method defines. Present when the call succeeded; absent when `error` is."
}
},
"type": "object"
}