Live API · api.clearagent.dev

AI Agents Are Moving Money. No One Screens Them Pre-Settlement.

The GENIUS Act makes every payment stablecoin issuer a financial institution under BSA. FinCEN implementing regulations land July 2026. Banks are building AI to automate compliance review workflows. Nobody is screening the AI agents themselves before they transact. CLEARAGENT is that pre-settlement middleware.

Get Early Access View Live Demo →
OFAC sanctions screening · live Verdict in <50ms BSA officer-validated Protocol-agnostic
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 pre-settlement screening exists at the agent layer

Banks are deploying AI to automate post-settlement compliance work — alert triage, EDD, payment review. That's AI doing compliance. ClearAgent is different: it screens the AI agent's payment request before the payment settles. Existing tools operate after the fact. None inspect the autonomous transaction at the transport layer.

What institutions get on every transaction

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

PROCEED — OFAC clear, PEP clear, adverse media clear, policy within limits
REVIEW — PEP match or adverse media flag, human approval required
BLOCK — OFAC hit, invalid credential, policy violation, or sanctions match
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",
    "pep:CLEAR",
    "adverse_media:CLEAR",
    "policy:within_limit"
  ],
  "auditId":   "txn_8Kx2..."
}
x402 Extension

Compliance middleware for x402 payments

One line adds OFAC sanctions screening plus spend policy enforcement to any x402-protected endpoint. Ships as an npm package that hooks into the x402 server before payment processing. Free tier. Roadmap: PEP, adverse media, and full BSA compliance with a config change.

// 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 screening rules. <50ms. OFAC sanctions check. 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 + PEP 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
  • Free tier (OFAC only) gets you integrated. Upgrade to full BSA compliance with a config change
  • 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 + PEP + adverse media screened on every call with daily counterparty re-scrubs
  • Nightly SDN sync — yesterday's clean operator is blocked today if added to the list
  • Full BSA program: OFAC, PEP, KYB, MSB, adverse media, domestic crime, durable audit log
  • Plugs into existing transaction monitoring systems as an enrichment feed
Existing compliance AI
Automating the analyst

Verafin, Hawk AI, SymphonyAI, Greenlite, Diligent — AI agents that triage sanctions alerts, write EDD reports, and review human-initiated payment flags. Human wire goes through. AI agent reviews the alert afterward.

vs
CLEARAGENT
Screening the automator

Middleware that intercepts the AI agent's payment request before settlement. OFAC check happens at the transport layer — before the transaction clears, not after. The agent is the subject being screened.

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.

1

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.

2

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.

3

Screen Every Payment

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

Regulatory Landscape

Three frameworks. One deadline.

BSA, GENIUS Act, and FinCEN implementing regulations are all converging on the same requirement: full compliance screening before money moves. The clock starts July 2026.

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 (July 2025)

Stablecoin Issuers = Financial Institutions

Makes every payment stablecoin issuer a "financial institution" under BSA. Any "agent for" the issuer is an "institution-affiliated party." AI agents initiating stablecoin payments fall under this umbrella.

FinCEN Regulations (July 2026)

The Implementing Deadline

FinCEN implementing regulations due July 2026. No FFIEC examination guidance exists for agentic payments. Every stablecoin issuer and delegated agent will need a complete BSA compliance program — OFAC, PEP, KYB, adverse media, and more.

Validated by Practitioners

"A real BSA compliance program for delegated AI agents would need OFAC, PEP screening, adverse media, KYB, MSB checks, domestic crime, and daily re-scrubs. I would use this product once it includes PEP screening and adverse media alongside OFAC."

— Former BSA Officer, Custodia Bank  ·  Design partner defining the product roadmap

Pricing

Start free. Scale to full BSA compliance.

Integrate once. Upgrade compliance tiers with a config change, not a re-integration. Your audit trail, review workflows, and switching costs compound over time.

Tier 1 · Developer

Free

up to 1,000 screens/month

OFAC sanctions screening only. Zero COGS — uses free Treasury data with nightly SDN sync. The acquisition wedge for x402 developers.

Tier 2 · Standard Compliance
Roadmap

$0.03 – $0.05

per screen

OFAC + PEP + adverse media + MSB registry + daily counterparty re-scrubs. The minimum viable compliance program a BSA officer would approve for a pilot.

Tier 3 · Full BSA Program
Roadmap

$0.10 – $0.25

per screen or $2K–$10K/mo SaaS

Adds KYB, domestic crime screening, 5-year durable audit log, and compliance digest reports. The complete BSA program a regulated institution requires.

Early Access

Get API access

We're onboarding a small group of design partners from both sides of the market. Tell us about your use case.

ACCESS REQUEST: PROCEED
{
  "verdict":     "PROCEED",
  "latencyMs":   42,
  "trace": [
    "vibe_check: CLEAR",
    "spam_filter: CLEAR",
    "we_like_you: true"
  ],
  "message":    "we'll be in touch soon",
  "auditId":    "req_"
}

Your request has been logged. A human will review it shortly — no autonomous agent involved, we promise.

Or email directly: jake.severn@icloud.com  ·  x402 RFC discussion