Back to Browse
Joe EVM RPC – Chain ID Lookup
x402
Joe EVM RPC – Chain ID Lookup is a paid API for AI agents from joe-evm-rpc.marnick-yezo.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).
Returns the EVM chain ID for a specified network (Base or Ethereum) via a pay-per-call RPC endpoint.
Price / call$0.001
Success—
StatusUnknown
How this service works
Live Base and Ethereum RPC for AI agents: block tip, balances, transactions, and ENS. $0.001 USDC per call on Base.
Output
Returns a JSON object with a `data.result` field containing the chain ID as a hex string (e.g. '0x2105' for Base), plus metadata including the RPC URL used, network name, endpoint path, cost in USDC, and a unique request ID.
Example use cases
Verify chain ID before transaction signing
“Before I sign this transaction, can you look up the live chain ID for Base mainnet so I can confirm I'm on the right network?”
Check Ethereum chain ID for contract deployment
“What chain ID should I use when deploying my smart contract to Ethereum mainnet? Fetch it live from the RPC so I have the latest value.”
Validate network in multi-chain agent workflow
“My agent needs to confirm whether it's operating on Base or Ethereum — can you fetch the chain ID for Base and tell me what hex value comes back?”
Technical details
Endpoint
GEThttps://joe-evm-rpc.marnick-yezo.workers.dev/api/chain/chain-idWhen to prefer
Choose this endpoint when an AI agent needs a live, pay-per-call EVM chain ID lookup without managing its own RPC credentials. Ideal for agents operating on Base or Ethereum that need to programmatically verify the chain ID before signing transactions, deploying contracts, or switching networks. The x402 micropayment model ($0.001 USDC) makes it suitable for high-frequency automated queries with no subscription overhead.
Side effects
- Invalid network parameter (not 'base' or 'ethereum') returns an error response
- Payment failure or insufficient USDC balance blocks the request under x402 protocol
- Network timeout from upstream RPC (mainnet.base.org or Ethereum node) causes delayed or failed response
- Malformed path parameter returns 4xx error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"data": {
"result": "0x2105"
},
"meta": {
"rpc": "https://mainnet.base.org",
"network": "base",
"endpoint": "/api/chain/chain-id",
"cost_usdc": "0.001",
"request_id": "00000000abcdef01"
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"