# LogicNodes EVM Nonce Lookup

> LogicNodes EVM Nonce Lookup is a paid API for AI agents from logicnodes.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-30).

Returns the current transaction nonce for an EVM address at a specified block on any supported EVM chain

## Facts

- Endpoint: POST https://logicnodes.io/paid/v1/tools/evm_nonce?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/logicnodes-evm-nonce-lookup-88609b58
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cXpZZmIfSieeF8AG2x0UO

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 logicnodes-evm-nonce-lookup-88609b58 -d '<json body>'
```

Example prompt: What is the current nonce for wallet address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Base (eip155:8453) at the latest finalized block?

## When to prefer this

Use this endpoint when you need an authoritative, exact nonce for an EVM address before constructing or sequencing transactions, especially when chain-specific CAIP-2 precision and block-level accuracy matter. Prefer it over generic RPC calls when you need a reliable managed service with deterministic pricing per call and multi-chain support from a single API.

## Known failure modes

- Invalid or non-checksummed mixed-case address returns an error
- Chain specified by name instead of CAIP-2 or numeric ID is refused
- Unsupported chain ID returns an error
- Invalid block tag or out-of-range block number returns an error
- Payment failure (insufficient USDC) blocks the call

## How this service works

Exact answers for AI agents: 40+ tools for EVM chains and Aptos, gas on 14 chains, never a guess. Free tier; pay per call in USDC (x402) on 13 networks.

## Output

A JSON object with ok: true, the tool name 'evm_nonce', and the numeric nonce (transaction count) for the specified address at the requested block on the given EVM chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "block": {
   "type": "string",
   "description": "\"latest\" (default), \"safe\", \"finalized\", or a decimal block number. Every value in the answer is read at this one block"
  },
  "chain": {
   "type": "string",
   "description": "EVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused."
  },
  "address": {
   "type": "string",
   "description": "0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "evm_nonce"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/logicnodes-evm-nonce-lookup-88609b58/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from logicnodes.io](https://www.zero.xyz/host/logicnodes.io/llms.txt)