AgentEconomy Compliance API
v1.0.0Paid KYC, AML, and regulatory risk assessment over MCP via x402 USDC micropayments on Base.
Endpoint health
online- Last checked
- 11/20/2026, 5:15:48 AM
- Latency
- 261 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.Piwe%2Fcompliance-api
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.Piwe/compliance-api": {
"url": "https://api.netbrainis.co.za/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
4 shown · authentication unknown
aml_screen
Screen an entity against Anti-Money Laundering (AML) watchlists including OFAC SDN and UN sanctions. Returns risk level, risk score, recommendation (approve/review/reject), and sanctions match details. Uses Jaro-Winkler fuzzy name matching for accurate detection. Cost: $0.05 USDC per screening. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.
Schema valid · SHA-256 1110c36a97de…
View input schema
{ "type": "object", "properties": { "amount": { "description": "Transaction amount", "type": "string" }, "currency": { "description": "Currency code (e.g. USDC, ETH, BTC)", "type": "string" }, "entity_name": { "description": "Full legal name of the person or entity to screen", "type": "string" }, "transaction_id": { "description": "Transaction identifier for audit trail", "type": "string" }, "wallet_address": { "description": "Blockchain wallet address to check", "type": "string" } }, "required": [ "entity_name" ] }kyc_check
Run a KYC (Know Your Customer) identity verification check against OFAC and UN sanctions lists. Returns verification status, risk score (0-100), and sanctions/PEP match results. Powered by real government sanctions data (OFAC SDN + UN Security Council). Cost: $0.01 USDC per check. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.
Schema valid · SHA-256 9e5a5bb4fd98…
View input schema
{ "type": "object", "properties": { "country": { "description": "ISO 3166-1 alpha-2 country code (e.g. US, GB, ZA, IR)", "type": "string" }, "entity_id": { "description": "National ID, passport number, or company registration number", "type": "string" }, "entity_name": { "description": "Full legal name of the person or entity to verify", "type": "string" }, "wallet_address": { "description": "Blockchain wallet address (e.g. 0x...)", "type": "string" } }, "required": [ "entity_name" ] }
Connections
streamable-http
https://api.netbrainis.co.za/mcp