# LogicNodes Payment Verify

> LogicNodes Payment Verify is a paid API for AI agents from logicnodes.io, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-28).

Verifies that a specific on-chain payment transaction meets expected conditions (asset, chain, recipient, payer, amount) for EVM networks

## Facts

- Endpoint: POST https://logicnodes.io/paid/v1/tools/payment_verify?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/logicnodes-payment-verify-717a99f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8M414uVkRySsa6pqrpIsx

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-payment-verify-717a99f1 -d '<json body>'
```

Example prompt: Check if transaction 0xabc123... on Base (eip155:8453) actually sent 1000000 USDC (contract 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48) from wallet 0xSender... to my wallet 0xRecipient... — I need to confirm the payment before I release the goods.

## When to prefer this

Choose this endpoint when you need a trustworthy, pay-per-call verification of a specific EVM on-chain payment transaction without running your own node. It is ideal for AI agents that must confirm receipt of a crypto payment before taking an action (releasing content, granting access, processing an order). Prefer it over general-purpose RPC calls when you want strict parameter validation (checksum-enforced addresses, CAIP-2 chain IDs) and a simple boolean result rather than raw transaction data.

## Known failure modes

- Transaction hash not found or not yet confirmed on chain — returns ok:false or error
- Chain ID provided as a name instead of CAIP-2 format (e.g. 'base' instead of 'eip155:8453') — refused with error
- Address checksum mismatch when mixed-case address fails EIP-55 validation — returns error
- Amount format invalid (non-integer, leading zeros, or too large) — schema validation failure
- Unsupported chain ID — endpoint returns an error for chains not in its supported set
- Payment parameters mismatch (wrong amount, wrong recipient, wrong asset) — returns ok:false

## 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

Returns a JSON object with an 'ok' boolean indicating whether the transaction satisfies all specified conditions (correct asset, chain, recipient, payer, and amount), plus the tool name 'payment_verify' for traceability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string"
  },
  "asset": {
   "type": "string",
   "description": "0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)"
  },
  "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."
  },
  "payTo": {
   "type": "string",
   "description": "0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)"
  },
  "payer": {
   "type": "string",
   "description": "0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)"
  },
  "amount": {
   "type": "string",
   "pattern": "^(0|[1-9][0-9]{0,77})$",
   "description": "base units"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/logicnodes-payment-verify-717a99f1/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)