{"slug": "how-we-built-a-pep-screening-api-with-19408-records-and-x402-payments", "title": "How we built a PEP Screening API with 19,408 records and x402 payments", "summary": "A team launched a free PEP screening API backed by 19,408 unique records ingested from Wikidata and OpenSanctions, covering politicians, judges, military officers and state-owned enterprise executives. The API uses x402 (HTTP 402) pay-per-call payments in USDC on Base at 0.01 USDC per request with no signup or API keys, and the team also released an MCP server exposing the screening as a tool for Claude and Cursor. The team said x402 lets AI agents pay for tools without human intervention and called MCP the emerging standard for AI tool integration.", "body_md": "We recently launched a free PEP (Politically Exposed Persons) screening API. Here's how it works and what we learned.\n\nThe problem: Compliance teams need to screen names against PEP lists, but existing solutions are expensive and require enterprise contracts. We wanted to build something simple: a single API call that returns matches.\n\nThe data: We ingested 19,408 unique PEP records from Wikidata and OpenSanctions. The data covers politicians, judges, military officers, and state-owned enterprise executives.\n\nThe API: It's a simple GET request:\n\ntext\n\nGET [https://compliance-engine.boring-saas-infra.workers.dev/check/pep?q=Rosneft](https://compliance-engine.boring-saas-infra.workers.dev/check/pep?q=Rosneft)\n\nThe payment: We use x402 (HTTP 402) for pay-per-call. It's a new protocol that lets AI agents pay for API calls with USDC on Base. No signup, no API keys. Just send a request and pay 0.01 USDC per call.\n\nThe MCP server: We also built an MCP server that exposes the PEP screening as a tool for Claude and Cursor. You can find it on GitHub.\n\nWhat we learned:\n\nx402 is a game-changer for AI agents. They can pay for tools without human intervention.\n\nMCP is becoming the standard for AI tool integration.\n\n19K records is enough to cover most compliance use cases.\n\nIf you're building compliance tools, feel free to test our API. It's free for 50 requests/day.", "url": "https://wpnews.pro/news/how-we-built-a-pep-screening-api-with-19408-records-and-x402-payments", "canonical_source": "https://dev.to/alexcodebytes/how-we-built-a-pep-screening-api-with-19408-records-and-x402-payments-28j8", "published_at": "2026-10-18 09:37:32+00:00", "updated_at": "2026-10-18 09:44:55.430835+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "ai-tools", "developer-tools"], "entities": ["Wikidata", "OpenSanctions", "Base", "Claude", "Cursor", "USDC"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/how-we-built-a-pep-screening-api-with-19408-records-and-x402-payments", "markdown": "https://wpnews.pro/news/how-we-built-a-pep-screening-api-with-19408-records-and-x402-payments.md", "text": "https://wpnews.pro/news/how-we-built-a-pep-screening-api-with-19408-records-and-x402-payments.txt", "jsonld": "https://wpnews.pro/news/how-we-built-a-pep-screening-api-with-19408-records-and-x402-payments.jsonld"}}