AgentEconomy Compliance API
Run paid KYC, AML, and regulatory risk checks from your agent when you are shipping fintech, marketplace, or onboarding flows that need sanctions-aware gates.
Overview
Compliance API is an MCP server for the Ship phase that runs KYC, AML, and regulatory risk tools billed per call with x402 USDC micropayments on Base.
What is this MCP server?
- Three publisher-documented MCP tools: kyc_check ($0.01), aml_screen ($0.05), risk_report ($0.10) USDC
- x402 micropayments on Base network; caller-funded X-PAYMENT header per request
- kyc_check: OFAC SDN + UN sanctions identity check
- aml_screen: sanctions screening with risk score and approve/review/reject recommendation
- risk_report: sanctions plus multi-jurisdiction regulatory risk analysis
- 3 documented MCP tools with per-tool USDC prices: kyc_check $0.01, aml_screen $0.05, risk_report $0.10
- Payment protocol x402 on network base with asset USDC
- OpenAPI URL https://api.netbrainis.co.za/openapi.json; challenge URL https://api.netbrainis.co.za/.well-known/x402
What problem does it solve?
Wiring sanctions and AML checks into an agent-driven build is slow when every vendor has a different auth and billing model.
Who is it for?
Indie fintech and marketplace builders who want metered compliance API access over MCP with documented per-tool USDC prices.
Skip if: Products with zero identity or payments scope, or teams that require enterprise MSAs instead of on-chain micropayments.
What do I get? / Deliverables
Your agent calls priced kyc_check, aml_screen, and risk_report tools with X-PAYMENT while you finalize secure onboarding and launch checks.
- KYC identity checks against OFAC SDN and UN sanctions (kyc_check)
- AML sanctions screening with scored approve/review/reject guidance (aml_screen)
- Regulatory risk reports combining sanctions and multi-jurisdiction analysis (risk_report)
Recommended MCP Servers
Journey fit
How it compares
Paid compliance API over MCP with x402 USDC, not a free local security linter skill.
Common Questions / FAQ
Who is compliance-api for?
Solo developers shipping regulated-adjacent flows who need agent-callable KYC, AML, and risk reports with transparent per-tool USDC pricing.
When should I use compliance-api?
Use it during ship and security hardening when onboarding, sanctions screening, or multi-jurisdiction risk reports must run before you launch real users.
How do I add compliance-api to my agent?
Register io.github.Piwe/compliance-api in your MCP client, fund USDC on Base, sign x402 challenges, and send the X-PAYMENT header on each tool call per the registry payment block.