# ChainVerdict Payment Verification

> ChainVerdict Payment Verification is a paid API for AI agents from chainverdict.xyz, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Verifies a Base blockchain transaction by checking its confirmation depth, success/revert status, transferred value, token type, sender, and recipient address.

## Facts

- Endpoint: GET https://chainverdict.xyz/v1/verify/payment/:tx
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chainverdict-payment-verification-9764b81e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0u6vm-xjRyy8VRo_ao6vP

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 chainverdict-payment-verification-9764b81e
```

Example prompt: Can you verify that Base transaction 0x4a3b...f91c actually succeeded, confirm it sent the right amount to my wallet address, and tell me how many confirmations it has?

## When to prefer this

Choose this endpoint when you need to cryptographically confirm that a specific Base transaction occurred as claimed — particularly before releasing goods, services, or data in exchange for an on-chain payment. It combines confirmation depth, success status, value, token, sender, and recipient into one call, avoiding the need to stitch together multiple RPC queries. Prefer it over raw RPC calls when you want a structured, agent-friendly response without managing a Base node connection.

## Known failure modes

- Transaction hash not found or not yet indexed — returns not-found error
- Transaction still pending (0 confirmations) — may return unconfirmed status
- Invalid or malformed transaction hash format — returns validation error
- Base node connectivity issues — returns service unavailable
- Transaction exists but is a contract interaction with no direct value transfer — may return unexpected token/value fields

## How this service works

Verify a Base transaction actually did what a counterparty says it did: confirmation depth, success or revert, value, token, sender and recipient. Use it to confirm an inbound payment before releasing goods or data.

## Output

Returns confirmation depth (number of blocks since inclusion), success or revert status of the transaction, the value transferred, the token (ETH or ERC-20 contract), the sender address, and the recipient address — all read live from the Base chain.

## 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"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "tx"
     ],
     "properties": {
      "tx": {
       "type": "string",
       "description": "Base transaction hash"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chainverdict-payment-verification-9764b81e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chainverdict.xyz](https://www.zero.xyz/host/chainverdict.xyz/llms.txt)