Live API · api.clearagent.dev

AI Agents Are Moving Money. Nobody's Screening Them.

Major card networks are issuing dedicated payment cards directly to AI agents. Agentic framework teams are shipping agents that move real money autonomously — across tens of thousands of businesses. Zero of those transactions are OFAC-screened. Banks that process them are exposed. CLEARAGENT closes that gap.

Get Early Access View Live Demo →

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

Why This Matters Now

A compliance gap just opened — at scale

The agent payment wave isn't coming. It's here. And the regulatory obligation to screen those payments was never optional.

The Shift

Agents are executing payments today

Agentic frameworks are being deployed that initiate real stablecoin payments — autonomously, without human approval per transaction. Major fintech platforms are issuing dedicated payment cards directly to AI agents across tens of thousands of businesses. This is present tense.

The Law

Banks must screen every transaction

BSA and OFAC regulations require financial institutions to screen all transactions. Agent-initiated payments are transactions. There is no carve-out for autonomous execution, stablecoins, or programmable money. The obligation is the same.

The Gap

No compliance layer exists for agents

Payment rails weren't built for autonomous agents. There's no standard way to answer "who sent this, are they credentialed, and is this transaction within policy?" before a payment clears. That's the gap CLEARAGENT fills.

What institutions get on every transaction

One API call before any payment clears. Three possible answers. Full audit trail either way.

PROCEED — operator credentialed, OFAC clear, policy within limits

REVIEW — flag raised, human approval required before processing

BLOCK — OFAC hit, invalid credential, or policy violation

The Integration

One call. Verdict in <50ms. No new infrastructure.

Works over any identity layer — x402 wallet, ACK-ID, Mastercard token, or raw address.

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..."
}

x402 Extension

Compliance middleware for x402 payments

One line adds OFAC sanctions screening, spend policy enforcement, and behavioral monitoring to any x402-protected endpoint. Ships as an npm package that hooks into the x402 server before payment processing.

// npm install @clearagent/x402
import { kyaComplianceHook } from "@clearagent/x402";

// Add to your x402 server — one line
httpServer.onProtectedRequest(kyaComplianceHook({
  apiKey: process.env.CLEARAGENT_API_KEY,
}));

25 rules. <50ms. Every payment screened before it settles.

Who It's For

Two problems. One shared infrastructure.

Agent operators need a way to prove their agents are credentialed before a bank touches the payment. Regulated institutions need a way to screen what's coming at them. CLEARAGENT serves both.

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 transaction monitoring systems as an enrichment feed

How It Works

Three calls. Closes the gap completely.

Register your agent once. Screen every payment. Full audit trail. No changes to existing payment infrastructure required.

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

Three frameworks. One answer.

OFAC, BSA, and emerging stablecoin regulation are all converging on the same requirement: you need to know who's transacting and screen them before money moves. Agent or not.

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.