# Ethereum Wallet Nonce Lookup

> Ethereum Wallet Nonce Lookup is a paid API for AI agents from agent-data-tools.revmesh2074.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-28).

Returns the current confirmed and pending transaction nonce for an Ethereum address, plus whether the address has ever sent a transaction.

## Facts

- Endpoint: GET https://agent-data-tools.revmesh2074.workers.dev/eth/nonce?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ethereum-wallet-nonce-lookup-206ff99e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Uq6MIEHJPedryVYhFOO2t

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ethereum-wallet-nonce-lookup-206ff99e
```

Example prompt: What's the current nonce for the Ethereum wallet 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045? I need to know if it's ever sent transactions and what the pending nonce is.

## When to prefer this

Choose this endpoint when you need to read the Ethereum mainnet transaction nonce for a wallet, especially before constructing or troubleshooting transactions. It is pay-per-call with no API key required, making it ideal for ad-hoc agent workflows. Use sibling endpoints for other chains (Base, Arbitrum, Optimism, Polygon) if those networks are needed.

## Known failure modes

- Invalid or malformed 0x address returns an error response
- Address with no on-chain history may return nonce 0 and hasSent false
- Network or RPC node outage may cause a timeout or 5xx error
- Missing required 'address' query parameter returns a validation error

## How this service works

Read the transaction count (nonce) of a 0x address on Ethereum, both confirmed and including pending transactions. Use to build the next transaction or to tell whether an address has ever sent anything; for its balance use eth_balance. A malformed address is rejected with 400, uncharged.

## Output

A JSON object with the wallet address, the confirmed transaction nonce, the pending nonce (including mempool), a boolean indicating whether the address has ever sent a transaction, the chain name (Ethereum), and the chain ID (1).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address"
 ],
 "properties": {
  "address": {
   "type": "string",
   "description": "0x address"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string"
  },
  "nonce": {
   "type": "number"
  },
  "address": {
   "type": "string"
  },
  "chainId": {
   "type": "number"
  },
  "hasSent": {
   "type": "boolean"
  },
  "pendingNonce": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ethereum-wallet-nonce-lookup-206ff99e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-data-tools.revmesh2074.workers.dev](https://www.zero.xyz/host/agent-data-tools.revmesh2074.workers.dev/llms.txt)
