# VeraData Entity Lookup

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

Returns verified structured data about Latin American entities (persons, companies, etc.) via x402 micropayment, with an audit hash for provenance.

## Facts

- Endpoint: POST https://api.veradata.dev/entity
- Price: $0.03/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/veradata-entity-lookup-9f71cc59
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vjcv53z7xpFYCmZN7wvks

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-entity-lookup-9f71cc59 -d '<json body>'
```

Example prompt: Can you pull verified entity data on a Brazilian company called 'Grupo Horizonte' using VeraData — I need the structured result and the audit hash for our compliance records?

## When to prefer this

Use this endpoint when you need verified, auditable data about Latin American entities (persons or companies) with a cryptographic audit trail. Prefer it over generic web search when compliance-grade provenance (audit hash) is required, or when enriching KYC/AML workflows for LATAM counterparties. The OFAC-only sibling endpoint is cheaper for simple sanctions screening, but this endpoint provides broader structured LATAM data.

## Known failure modes

- Missing required 'type' or 'method' fields in input returns a 400 validation error
- Invalid entity type or unsupported lookup method returns an error or empty result
- Payment failure via x402 (insufficient USDC balance, payment timeout) prevents the call from completing
- Entity not found in LATAM data sources returns an empty or null result
- Network timeout or upstream data provider outage returns a 5xx error

## How this service works

Verified Latin American Data for Autonomous AI Agents — x402 micropayments

## Output

A JSON object containing structured LATAM entity data (e.g. corporate records, identity details) relevant to the queried entity type and lookup method, plus a SHA-256 audit hash confirming data provenance.

## 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-entity-lookup-9f71cc59/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)