# Legible Check EVM Nonce Lookup

> Legible Check EVM Nonce Lookup is a paid API for AI agents from legible-check.ezealfa.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-20).

Returns the current transaction nonce for an Ethereum address on the Base blockchain, paid per-call in USDC via x402.

## Facts

- Endpoint: GET https://legible-check.ezealfa.workers.dev/evm/nonce?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/legible-check-evm-nonce-lookup-a84ff58e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kCPsw0e1ERCNbLwK4t7KP

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 legible-check-evm-nonce-lookup-a84ff58e
```

Example prompt: What's the current transaction nonce for wallet address 0x8424... on Base right now?

## When to prefer this

Use this endpoint when you need a lightweight, no-signup nonce lookup for an EVM address on Base and are already operating in an x402-compatible payment environment. Prefer this over self-hosted RPC calls when you want a pay-per-use model with no API key management, or when building agents that pay micropayments per data fetch.

## Known failure modes

- HTTP 402 returned if payment not provided — includes price ($0.002 USDC) and receiving wallet address
- Invalid or malformed EVM address may return an error or empty result
- Network issues with Base RPC may cause timeouts or stale data
- Missing required 'type' or 'method' input fields returns a schema validation error

## How this service works

Pay-per-call data endpoints on Base, settled in USDC over x402. No account, no API key, no signup. Unpaid calls answer HTTP 402 with the price and the receiving wallet.

## Output

A JSON object containing the chain name (e.g. 'base'), the integer nonce (transaction count) for the queried address, and the address itself. Example: {chain: 'base', nonce: 12, address: '0x8424...'}.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": "base",
  "nonce": 12,
  "address": "0x8424..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/legible-check-evm-nonce-lookup-a84ff58e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from legible-check.ezealfa.workers.dev](https://www.zero.xyz/host/legible-check.ezealfa.workers.dev/llms.txt)
