# VeraData LATAM Rates Stream Token

> VeraData LATAM Rates Stream Token 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).

Streams verified Latin American financial or economic rate data for a given type and method, returning structured results with an audit hash

## Facts

- Endpoint: POST https://api.veradata.dev/rates/stream/token
- 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-latam-rates-stream-token-72cc02ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u8ERCfII577p1pM2A8C_U

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-latam-rates-stream-token-72cc02ec -d '<json body>'
```

Example prompt: Pull verified LATAM rate data from VeraData using a token stream — I need the spot type with a real-time method, and I want the result as structured JSON so I can audit the hash afterward.

## When to prefer this

Choose this endpoint when you need verified, auditable rate or economic data specifically for Latin American markets, especially when tamper-evidence (audit hash) is required or when integrating into autonomous AI agent workflows using x402 micropayments. Prefer this over generic FX or data APIs when LATAM-specific coverage and cryptographic auditability are priorities.

## Known failure modes

- Missing required 'type' or 'method' fields in input object returns a validation error
- Payment failure or insufficient USDC balance causes 402 response before data is returned
- Invalid data type or method combination returns an error or empty result
- Network timeout during streaming may result in incomplete data delivery
- Unsupported output type specification may cause malformed response

## How this service works

Verified Latin American Data for Autonomous AI Agents — x402 micropayments

## Output

A JSON object containing 'result' with structured LATAM rate or economic data, and 'audit_hash' (sha256 fingerprint) for tamper verification of the returned data payload.

## 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-latam-rates-stream-token-72cc02ec/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)