# EVM Account Nonce Lookup

> EVM Account Nonce Lookup is a paid API for AI agents from saylorinnovations.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-30).

Returns the latest and pending nonce for an EVM account address on a specified chain, plus the next nonce to use and advice for replacing stuck transactions.

## Facts

- Endpoint: GET https://saylorinnovations.com/api/explorer/nonce?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-account-nonce-lookup-d34c1d80
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Hv7LunHnBl-pFjzzvLKLx

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 evm-account-nonce-lookup-d34c1d80
```

Example prompt: What's the current nonce situation for my address 0xAbC1234...on Ethereum mainnet — latest vs pending, how many transactions are in flight, and what nonce should I use next?

## When to prefer this

Use this endpoint when an AI agent needs to determine the correct nonce for broadcasting an EVM transaction, diagnose why a transaction is stuck in the mempool, count in-flight transactions, or retrieve actionable replacement advice — especially across 16 supported chains without having to run your own RPC node.

## Known failure modes

- Invalid or malformed EVM address returns an error response
- Unsupported or misspelled chain name returns a chain-not-found error
- RPC node unavailability for a specific chain may return null for pending fields
- Network timeout resulting in incomplete nonce data
- Address with no on-chain activity may return nonce 0 with minimal context

## How this service works

EVM account nonce on 16 chains: latest versus pending, transactions in flight, next nonce to use, and how to replace a stuck transaction.

## Output

A JSON object containing the chain name and chain ID, the queried address, nonce_latest (confirmed on-chain), nonce_pending (including mempool), next_nonce_to_use (the recommended nonce for the next send), pending_transactions count, native token balance, current gas price in gwei, a status label, human-readable advice for handling stuck or pending transactions, a caveat note, and the data source used.

## Request schema (JSON Schema)

```json
{
 "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": [
      "chain",
      "address"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "description": "chain name or id"
      },
      "address": {
       "type": "string",
       "description": "the sending account address"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "required": [
      "chain",
      "chain_id",
      "address",
      "nonce_latest",
      "next_nonce_to_use",
      "status",
      "native_symbol",
      "advice",
      "note",
      "source"
     ],
     "properties": {
      "note": {
       "type": "string",
       "description": "Caveat or context for reading the result"
      },
      "chain": {
       "type": "string",
       "description": "Blockchain the data is for"
      },
      "advice": {
       "type": "string",
       "description": "The advice text"
      },
      "source": {
       "type": "string",
       "description": "Data source the values come from"
      },
      "status": {
       "type": "string",
       "description": "Current status"
      },
      "address": {
       "type": "string",
       "description": "Account or contract address"
      },
      "chain_id": {
       "type": "number",
       "description": "EVM chain id"
      },
      "nonce_latest": {
       "type": "number",
       "description": "Nonce latest"
      },
      "native_symbol": {
       "type": "string",
       "description": "Native symbol"
      },
      "nonce_pending": {
       "type": [
        "number",
        "null"
       ],
       "description": "Nonce pending"
      },
      "balance_native": {
       "type": [
        "number",
        "null"
       ],
       "description": "Balance native"
      },
      "gas_price_gwei": {
       "type": [
        "number",
        "null"
       ],
       "description": "Gas price in gwei"
      },
      "next_nonce_to_use": 
… (truncated)
```

## More

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