# Kertivo Deep Payment Verify

> Kertivo Deep Payment Verify is a paid API for AI agents from kertivo.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-29).

Deeply verifies a Base USDC payment by checking confirmations, payTo/amount match, fake-token and lookalike warnings, and the payer's full USDC funding history with top funders and a sha256 receipt

## Facts

- Endpoint: POST https://kertivo.com/check/deep?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kertivo-deep-payment-verify-d4fa29b3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_D7yOlupL6mhx5XADPo8Pv

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 kertivo-deep-payment-verify-d4fa29b3 -d '<json body>'
```

Example prompt: Can you do a deep verification on USDC payment 0x3a7f...b2c1 — I was expecting exactly 5.00 USDC sent to my address 0xABcd...1234, and I want to know if it really settled, whether the payer's funding source looks legitimate, and get the full funding history and any fraud warnings?

## When to prefer this

Choose this endpoint over the basic Kertivo payment verify when you need not just settlement confirmation but also deep due-diligence on the payer — specifically their full USDC funding history, top funders, address-poisoning and fake-token risk signals, and an auditable sha256 receipt. Ideal for high-value transactions, compliance workflows, fraud prevention pipelines, or any scenario where knowing the provenance of the payer's funds matters. Use the basic check endpoint for lightweight, low-cost settlement-only verification.

## Known failure modes

- Invalid or malformed txHash returns 400 validation error
- Unsupported token (non-USDC) returns 400 unsupported_token, not charged
- Transaction not found on Base mainnet returns appropriate not-found response
- expectedPayTo mismatch reported in match result fields
- expectedAmount mismatch reported in amount match fields
- Funding index unavailable — endpoint returns result without history data and does not charge
- Network timeout or Base RPC issues may delay or fail the response
- Authorization object provided but nonce or from address is invalid returns 400

## How this service works

Did this USDC payment settle, and what is the payer's funding source? Deep Base verification: confirmations, payTo/amount match, fake-token and lookalike warnings, plus the payer's inbound USDC funding history from an index (latest 500 transfers before the payment, then up to 5 more pages; coverage.historyComplete says if that was the full history), top funders, coverage stats and a recheckable sha256 receipt. Not charged if the index is down. Body {txHash, expectedPayTo?, expectedAmount?}.

## Output

Returns settlement status with confirmation count, payTo and amount match results, fake-token and lookalike address warnings, the payer's inbound USDC funding history (up to 500 transfers plus up to 5 more pages), top funders list, coverage statistics including a historyComplete flag indicating whether the full history was retrieved, and a recheckable sha256 receipt of the response. Not charged if the funding index is unavailable.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "token": {
   "type": "string",
   "description": "Optional (aliases asset, currency): \"USDC\" or the Base USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (apexfaucet-style). Any other token is a 400 unsupported_token, not charged. Responses always echo token \"USDC\"."
  },
  "txHash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "Base mainnet transaction hash"
  },
  "minAmount": {
   "type": [
    "string",
    "number"
   ],
   "description": "Optional floor (aliases min_amount, min): payment must be at least this many USDC; unlike expectedAmount it is not exact"
  },
  "authorization": {
   "type": "object",
   "required": [
    "from",
    "nonce"
   ],
   "properties": {
    "from": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{40}$"
    },
    "nonce": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{64}$"
    },
    "validAfter": {
     "type": [
      "string",
      "integer"
     ]
    },
    "validBefore": {
     "type": [
      "string",
      "integer"
     ],
     "description": "unix seconds"
    }
   },
   "description": "Optional EIP-3009 authorization (x402 exact payload) to check when there is no tx or the tx is not found"
  },
  "expectedPayTo": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "Expected recipient (full-address, case-insensitive compare)"
  },
  "expectedPayer": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "Optional expected payer (aliases from, payer): the USDC Transfer's from must equal it"
  },
  "selfAddresses": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 10,
   "description": "Optional: other addresses you control; funding from them counts as self_funded"
  },
  "expectedAmount": {
   "type": [
    "string",
    "number"
   ],
   "description": "Expected USDC amount, decimal (e.g. \"0.01\")"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kertivo-deep-payment-verify-d4fa29b3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kertivo.com](https://www.zero.xyz/host/kertivo.com/llms.txt)