ClearAgent doesn't settle payments, verify wallet-address risk, or issue agent identity — those problems are already solved, and solved well, by the partners below. ClearAgent screens the counterparty, enforces operator policy, and issues a signed verdict an examiner can pull. Every relationship on this page exists to keep it that way.
Four positions, one map. Screening scope runs from wallet/transaction data to entity names and operator policy; output runs from raw lookups to an audited, signed verdict. ClearAgent occupies the corner nobody else does — entity-name and operator-policy screening, packaged as a verdict with a policy record and a reviewer file.
Entity-name screening against OFAC/UN/EU/UK sanctions, evaluated against the operator's spend policy, at the moment of payment. Output is a signed, offline-verifiable verdict with an examiner-pullable audit trail — not a match score.
Sanctions, PEP, and adverse-media data and matching. ClearAgent consumes this as an input signal — the data supplier, not a program-layer competitor.
Case management and SAR filing once a human needs to review something. No screening of its own — it needs a verdict to open a case with. That verdict is ClearAgent's.
Wallet-cluster and transaction-graph tracing — a deeper, different problem than pre-settlement entity screening. Runs alongside ClearAgent's verdict where a program needs that depth, not in place of it.
What this is not. ClearAgent is not a settlement rail, not a wallet-address KYT provider, and not an agent-identity issuer. It does not compete with Coinbase CDP, Stripe, Visa TAP, Skyfire, or Google AP2 — it consumes their outputs as signals in the screening decision.
The rail, identity, and data partners ClearAgent's program layer runs on top of — some integrated today, some in active outreach.
ClearAgent runs entirely on Cloudflare Workers, KV, and D1 — no origin server, ~80ms median verdict. Working toward a listing in Cloudflare's agent / Monetization Gateway docs as a compliance option for Workers-hosted agent developers.
ClearAgent screens live on x402 today — $0.005 USDC per verdict on Base mainnet via the Coinbase CDP facilitator. Proposing a signed-receipt / compliance-manifest extension to the spec so any x402 payment can carry an audit-ready verdict.
Machine Payments Protocol support ships via @clearagent/mpp. Building a reference-merchant demo for the MPP preview team so compliance-aware screening is visible in MPP's reference integrations.
OEM sanctions, PEP, and adverse-media data, integrated in production behind ClearAgent's multi-list screening option. ClearAgent is the program layer on top of dilisense's data — not a competing data vendor.
Case management and SAR filing, with no screening of its own. Defining a SAR-handoff spec so a ClearAgent REVIEW/BLOCK verdict — with prior-screening history attached — opens a case directly.
A permitted-stablecoin-issuer compliance program — the archetypal buyer for an audited verdict. In discussion for a paid pilot, no exclusivity.
Identity inputs, accepted not built. Visa TAP, Skyfire KYAPay, and Google AP2 answer "who is the agent." ClearAgent accepts their assertions as an input to a screen and logs them in the audit trail — it does not build agent-identity verification.