Live API · api.clearagent.dev

The Compliance Layer Every Agent Payment Has to Clear First

KYA Protocol screens AI agents against OFAC, validates spend policy, and returns a BSA-defensible verdict in under 50ms — before any regulated institution touches the payment.

Get Early Access View Live Demo →

OFAC re-screened on every call W3C Verifiable Credentials Protocol-agnostic Verdict in <50ms

Screen a transaction

# Any identity layer · Any counterparty
curl -X POST https://api.clearagent.dev/v1/screen \
  -H "Authorization: Bearer <key>" \
  -d '{
    "token":       "<KYA-credential-JWT>",
    "amount":      50000,
    "currency":    "USDC",
    "counterparty":"0x71C7656EC7ab88b0..."
  }'

Response · 23ms

{
  "verdict":    "PROCEED",
  "latencyMs":  23,
  "trace": [
    "ofac:CLEAR",
    "policy:within_limit",
    "counterparty:CLEAR"
  ],
  "auditId":   "txn_8Kx2..."
}

PROCEED — all checks pass

REVIEW — human approval required

BLOCK — OFAC hit or policy violation

Two-Sided Compliance API

Built for both sides of every agent payment

Operators register once. Institutions screen on every call. Network effects compound from both directions.

🤖

Agent Operators

I build and deploy AI agents that initiate payments

Register agents at deployment — OFAC screened at issuance
W3C Verifiable Credential issued as a JWT — store alongside your API keys
Spend policy encoded in the credential — single tx limit, daily cap, allowed chains
Works over any identity layer: ACK-ID, x402 wallet, Mastercard token, raw address
Documented compliance process before any regulator asks

🏦

Regulated Institutions

I process or facilitate payments that agents initiate

Call POST /screen before processing any agent-initiated payment
OFAC re-screened live on every call — not just at credential issuance
Nightly SDN sync — yesterday's clean operator is blocked today if added to the list
Tamper-evident audit log per transaction — BSA examination-ready
Plugs into existing TMS (Actimize, Verafin) as enrichment feed

How It Works

Three calls. Zero new infrastructure.

Integrate KYA Protocol into your existing stack without replacing anything.

📋

Register the Agent

Call POST /v1/agents/register with operator identity and spend policy. KYA screens against OFAC live and issues a signed W3C Verifiable Credential as a JWT. One-time per agent deployment.

🔑

Store the Credential

The KYA credential is a JWT — store it as an env var alongside your API keys. Zero new infrastructure required. Works with ACK-ID, x402, Mastercard tokens, or any identity layer.

⚡

Screen Every Payment

Before any payment processes, call POST /v1/screen with the KYA token and transaction details. Get a PROCEED / REVIEW / BLOCK verdict in <50ms with full reasoning trace and audit log entry.

Regulatory Landscape

The compliance gap is structural, not optional

Multiple regulatory frameworks are converging on the same requirement. KYA is the answer.

BSA / 31 U.S.C. § 5318

Bank Secrecy Act

Financial institutions must maintain AML programs and screen transactions against OFAC. Agent-initiated payments are transactions. BSA programs must cover them.

GENIUS Act (pending)

Stablecoin Payments

Creates federal licensing requirements for stablecoin issuers and payment processors. Mandates OFAC screening for stablecoin transactions. Compliance infrastructure required before the license matters.

BRCA (pending)

Blockchain Regulatory Certainty

Clarifies that non-custodial software providers are not money transmitters. Does not eliminate OFAC obligations — 31 CFR Part 501 applies to all U.S. persons regardless of custody status. KYA is the OFAC answer BRCA can't give you.