# VeraData Monitor — Verified LATAM Data Monitor

> VeraData Monitor — Verified LATAM Data Monitor is a paid API for AI agents from api.veradata.dev, paid per call via x402, $0.02/call, status down (last checked 2026-09-15).

Monitors and retrieves verified, structured data about Latin American entities or events via micropayment-gated API

## Facts

- Endpoint: POST https://api.veradata.dev/solutions/monitor
- Price: $0.02/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/veradata-monitor-verified-latam-data-monitor-989d45fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_izvNANE3ucOYW_3JNDzQk

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-monitor-verified-latam-data-monitor-989d45fb -d '<json body>'
```

Example prompt: Can you monitor and pull the latest verified data on the Brazilian entity I'm tracking and give me the structured result along with the audit hash so I can verify it?

## When to prefer this

Choose this endpoint when you need verified, auditable data specifically about Latin American entities, businesses, or markets, and require a cryptographic audit trail (SHA-256 hash) to prove data provenance. Prefer it over generic data APIs when LATAM regional coverage and verifiability are critical requirements, and when micropayment-per-call pricing is acceptable.

## Known failure modes

- Payment not received or insufficient USDC balance — request rejected before data is returned
- Unknown or unsupported LATAM entity/query — returns empty or null result
- Rate limiting if too many calls are made in a short window
- Invalid request body format — 400 error
- Audit hash mismatch if data integrity check fails downstream

## How this service works

Verified Latin American Data for Autonomous AI Agents — x402 micropayments

## Output

Returns a JSON object with 'result' containing structured LATAM data relevant to the monitored subject, and 'audit_hash' (SHA-256) for cryptographic verification of the data's integrity.

## 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-monitor-verified-latam-data-monitor-989d45fb/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)