# VeraData Wallet Screen

> VeraData Wallet Screen is a paid API for AI agents from api.veradata.dev, paid per call via x402, $0.05/call, status down (last checked 2026-09-15).

Screens a wallet or financial entity against verified Latin American data sources for compliance or identity checks

## Facts

- Endpoint: POST https://api.veradata.dev/wallet/screen
- Price: $0.05/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/veradata-wallet-screen-d85bbe53
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BjzOxlU8U3sfjO_pPhqGq

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 veradata-wallet-screen-d85bbe53 -d '<json body>'
```

Example prompt: Screen this wallet address against VeraData's verified Latin American database using an address lookup method and give me the structured result with the audit hash.

## When to prefer this

Choose this endpoint when you need to screen or verify a wallet or financial entity specifically against Latin American (LATAM) data sources, particularly for AML/KYC compliance workflows. It is ideal for agents operating in Latin American markets that require verified, auditable data with a tamper-evident hash. Use it over generic screening services when LATAM-specific data coverage and x402 micropayment-based access are preferred.

## Known failure modes

- Missing required 'type' or 'method' fields in the input object returns a validation error
- Payment failure or insufficient USDC balance returns a 402 Payment Required
- Unknown or unsupported screening type/method combination returns an error
- Rate limiting may occur if too many calls are made in quick succession
- Network or upstream LATAM data source unavailability may cause timeouts

## How this service works

Verified Latin American Data for Autonomous AI Agents — x402 micropayments

## Output

Returns a JSON object with a 'result' field containing structured LATAM compliance data about the screened entity, and an 'audit_hash' (SHA-256) for tamper-evident audit trail purposes.

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": "structured LATAM data",
  "audit_hash": "sha256:..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/veradata-wallet-screen-d85bbe53/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.veradata.dev](https://www.zero.xyz/host/api.veradata.dev/llms.txt)