# VeraData Compliance Report

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

Generates verified compliance reports on Latin American entities using structured LATAM data with an auditable hash, paid via x402 micropayment.

## Facts

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

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-compliance-report-d9105dec -d '<json body>'
```

Example prompt: Can you pull a verified compliance report on this Brazilian company — use entity type 'business' and method 'tax_id' — I need the audit hash included so I can log it for our due diligence records.

## When to prefer this

Use this endpoint when you need verified, auditable compliance or due diligence data specifically for Latin American entities (individuals or businesses). It is best suited for KYC/AML workflows, supplier vetting, or regulatory checks in the LATAM region where an audit trail (SHA256 hash) is required. Prefer this over generic business lookup APIs when jurisdiction-specific LATAM coverage and audit accountability matter.

## Known failure modes

- Missing required 'type' or 'method' fields in the input object returns a 400 validation error
- Invalid entity type or lookup method returns an unrecognized input error
- Payment not received or x402 micropayment fails results in a 402 Payment Required response
- Entity not found in LATAM data sources returns an empty or null result
- Network timeout or upstream data source unavailability returns a 503 or timeout error

## How this service works

Verified Latin American Data for Autonomous AI Agents — x402 micropayments

## Output

A structured JSON object containing verified LATAM compliance data relevant to the queried entity, along with a SHA256 audit hash for traceability and record-keeping.

## 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-compliance-report-d9105dec/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)