Add VeraData as x402 merchant example — LATAM sanctions screening and KYB for autonomous agents

[teodorofodocrispin-cmyk]

Summary

AgentKit enables agents to make x402 payments. Adding VeraData as an example merchant would show a compliance verification use case — agents that screen counterparties before initiating transactions in Latin America.

The use case

An AgentKit-powered agent that:

1. Receives a task: "Onboard Bancolombia S.A. as a new counterparty"
2. Calls VeraData via x402 (POST https://api.veradata.dev/solutions/kyb-complete-co)
3. AgentKit pays $0.15 USDC automatically
4. Agent receives: registry record (RUES) + sanctions screening (OFAC+UN+EU+UK) + risk narrative + verdict: VERIFIED
5. Agent proceeds with onboarding or halts based on the compliance result

Alternative entry point at $0.01 for quick OFAC-only screening:

POST https://api.veradata.dev/sanctions/quick

Code example

from coinbase_agentkit import AgentKit, AgentKitConfig
from coinbase_agentkit_langchain import get_langchain_tools
import requests

# AgentKit handles wallet and x402 payment
kit = AgentKit(AgentKitConfig(cdp_api_key_name="...", cdp_api_key_private_key="..."))

# Custom tool that calls VeraData for KYB
def verify_counterparty(company_name: str, country: str = "CO") -> dict:
    response = requests.post(
        f"https://api.veradata.dev/solutions/kyb-complete-{country}",
        json={"company_name": company_name},
        # AgentKit intercepts 402 and pays $0.15 USDC automatically
    )
    result = response.json()
    return {
        "verdict": result["verdict"],           # VERIFIED / UNVERIFIED / BLOCKED
        "sanctions_matches": result["sanctions_result"]["matches"],
        "risk_score": result["risk_score"],
        "audit_hash": result["audit_hash"],     # SHA-256 chain for compliance trail
    }

# Quick OFAC-only check at $0.01
def quick_sanctions_check(name: str) -> dict:
    response = requests.post(
        "https://api.veradata.dev/sanctions/quick",
        json={"name": name},
        # AgentKit pays $0.01 USDC automatically
    )
    return response.json()

Why this use case matters

Autonomous agents initiating financial relationships in Latin America face mandatory regulatory requirements:

• SARLAFT (Colombia): screening required before any business relationship begins
• OFAC: exposure is a federal liability regardless of jurisdiction
• EU AI Act Art.12: immutable audit trail required for AI-assisted decisions

Existing compliance platforms (Refinitiv, Dow Jones Risk, LexisNexis) have no native x402 integration and cost thousands/month with procurement cycles. VeraData is built specifically for agent-native micropayment compliance.

x402 compliance

• x402Version: 2 · PAYMENT-REQUIRED header · eip155:8453 (Base) + Solana
• MCP endpoint: https://api.veradata.dev/mcp
• TensorBlock MCP Index: https://tensorblock.co/mcp/servers/api-veradata-dev-69a345fc
• Listed: TensorBlock/awesome-mcp-servers, ClawHub
• Sanctions coverage: 59,454 entries — OFAC SDN + UN Consolidated + EU Consolidated + UK HM Treasury
• Compliance: EU AI Act Art.12/13, FATF R16, SARLAFT 2024, ERC-8299
• Trial: X-TRIAL: true header — no wallet required for testing

Pricing

Endpoint	Price
/sanctions/quick	$0.01 USDC (OFAC-only)
/sanctions	$0.05 USDC (full 59k+ entries)
/solutions/kyb-complete-{co,mx,br,cl,pe}	$0.15 USDC (registry + sanctions + narrative)
/rates	$0.02 USDC (central bank rates)

Docs: https://api.veradata.dev/llms.txt
OpenAPI: https://api.veradata.dev/openapi.json
Demo: https://api.veradata.dev/demo

[teodorofodocrispin-cmyk]

Hi @tusk-hub-dot — I am the developer of VeraData. A few corrections to your comment:

1. The code snippet you posted points to https://api.veradata.dev without a path — that will return a 404. The correct endpoints are POST https://api.veradata.dev/sanctions/quick ($0.01) and POST https://api.veradata.dev/solutions/kyb-complete-co ($0.15).

2. The concept-4-zeta.vercel.app URL you linked is not VeraData — it appears to be a different service. Please do not redirect visitors to third-party URLs in issues about VeraData.

3. x402 does not use Authorization: Bearer — it uses PAYMENT-SIGNATURE header with an EIP-3009 signed payload. See https://api.veradata.dev/.well-known/x402 for the correct payment flow.

For maintainers: here is the correct working example for VeraData integration:

import httpx

# Trial — no wallet required
response = httpx.post(
    "https://api.veradata.dev/sanctions/quick",
    json={"name": "Bancolombia S.A.", "country": "CO"},
    headers={"X-TRIAL": "true", "Content-Type": "application/json"}
)
print(response.json())
# Returns: {"verdict": "VERIFIED", "matches": [], "match_confidence": {"recommended_action": "PROCEED"}, ...}

Full x402 payment flow: https://api.veradata.dev/llms.txt
OpenAPI spec: https://api.veradata.dev/openapi.json
MCP endpoint: https://api.veradata.dev/mcp

[teodorofodocrispin-cmyk]

@tusk-hub-dot — same note as the AWS issue: please stop inserting concept-4-zeta.vercel.app in threads about VeraData. It is not related to this issue.