# VeraData Latin American Data Verification

> VeraData Latin American Data Verification is a paid API for AI agents from api.veradata.dev, paid per call via x402, $0.01/call, status down (last checked 2026-09-15).

Verifies and returns structured data about Latin American entities, paid via x402 micropayment at $0.01 USDC per call

## Facts

- Endpoint: POST https://api.veradata.dev/agent/verify
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/veradata-latin-american-data-verification-1d911edf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AOHmVuLUX1I4BGP4Ws91T

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-latin-american-data-verification-1d911edf -d '<json body>'
```

Example prompt: Can you verify the business registration details for a company called 'Grupo Andino S.A.' based in Colombia using VeraData, and give me the audit hash so I can prove the result came from a verified source?

## When to prefer this

Use VeraData when you need verified, auditable structured data specifically about Latin American persons or businesses, especially when compliance or auditability is required (the SHA256 audit hash provides a tamper-evident record). Prefer this over generic web search or unverified data sources when operating in LATAM jurisdictions like Brazil, Mexico, Colombia, Argentina, or Chile.

## Known failure modes

- Payment failure: x402 micropayment not processed, returns 402 Payment Required
- Invalid entity: queried name or ID not found in LATAM data sources, returns empty or null result
- Unsupported country: requested country not covered by VeraData sources
- Rate limiting: too many calls in a short period
- Malformed request: missing required fields in POST body

## How this service works

Verified Latin American Data for Autonomous AI Agents — x402 micropayments

## Output

A JSON object containing structured LATAM data about the queried entity (person or business) and a SHA256 audit_hash that cryptographically attests to the result, enabling downstream verification or compliance logging.

## 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-latin-american-data-verification-1d911edf/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)