ENSUSD
ENS / United States dollar
crypto Composite

I've been building a platform that gives AI agents and apps access to about 300 structured data sources through a single API. Recently added an x402 payment gateway so any agent can pay per call with USDC on Base, no signup or API key needed.
The x402 part works like this: the agent makes a standard HTTP request, gets back a 402 Payment Required with pricing info, sends payment on Base mainnet, and gets the data back. Payment is the auth. There's no account creation, no wallet top-up, no API key. An autonomous agent running can consume data without a human in the loop.
The catalog behind it covers:
**Company data across 20 countries.** Direct integrations with government registries: Companies House (UK), Brreg (Norway), CVR (Denmark), PRH (Finland), KRS (Poland), and more. Not wrappers around an aggregator but separate integrations against the primary government source.
**Financial validation.** IBAN, SWIFT/BIC, VAT validation via VIES, LEI lookup from GLEIF, exchange rates, invoice extraction and validation.
**Compliance.** Sanctions screening, PEP checks, adverse media screening, beneficial ownership lookups, risk narrative generation. These chain into pre-built KYB workflows for 20 countries.
**Web3.** Wallet risk scoring and age checks via GoPlus Security and Etherscan V2. Token security analysis (honeypot detection, sell tax, hidden ownership, mint functions) across 30+ chains. Contract verification, approval security checks, phishing site detection. Protocol TVL and fees via DeFi Llama. Stablecoin flows, ENS resolution, Fear & Greed Index, crypto prices. VASP verification against ESMA's MiCA register. Pre-built solutions for token project due diligence, DeFi protocol risk checks, and crypto counterparty KYB.
**Web and general purpose.** URL-to-markdown, structured web scraping, DNS, SSL, WHOIS, domain reputation, plus things like forex, job board search, npm/PyPI package info.
Everything returns structured JSON, gets continuously tested in the background, and produces an audit trail with provenance metadata. The quality scores are public so an agent can check reliability before making a call.
The x402 gateway sits on top of the same catalog as the traditional API. Anything available through the REST API with an API key is also available through x402 with USDC. Discovery endpoint at `/.well-known/x402.json`, full catalog at `/x402/catalog`.
Still early. The x402 standard itself is young and agent-to-agent commerce is more talked about than practiced right now. But the infrastructure for "agent pays for data at the moment it needs it, no human approval step" seems worth building before demand arrives rather than after.
Current limitations: the platform is in early access. GoPlus coverage varies by chain (Ethereum and BSC strongest, smaller L2s have gaps). Etherscan V2 rate limits are tight. The ESMA MiCA register is new and sparse. A handful of EU registries intermittently block requests from certain IP ranges. Some capabilities are more reliable than others, which is why the quality scores exist.
If you're building something that needs data sources we don't cover yet, happy to hear what's missing.

I've been building a platform that gives AI agents and apps access to about 300 structured data sources through a single API. Recently added an x402 payment gateway so any agent can pay per call with USDC on Base, no signup or API key needed.
The x402 part works like this: the agent makes a standard HTTP request, gets back a 402 Payment Required with pricing info, sends payment on Base mainnet, and gets the data back. Payment is the auth. There's no account creation, no wallet top-up, no API key. An autonomous agent running can consume data without a human in the loop.
The catalog behind it covers:
**Company data across 20 countries.** Direct integrations with government registries: Companies House (UK), Brreg (Norway), CVR (Denmark), PRH (Finland), KRS (Poland), and more. Not wrappers around an aggregator but separate integrations against the primary government source.
**Financial validation.** IBAN, SWIFT/BIC, VAT validation via VIES, LEI lookup from GLEIF, exchange rates, invoice extraction and validation.
**Compliance.** Sanctions screening, PEP checks, adverse media screening, beneficial ownership lookups, risk narrative generation. These chain into pre-built KYB workflows for 20 countries.
**Web3.** Wallet risk scoring and age checks via GoPlus Security and Etherscan V2. Token security analysis (honeypot detection, sell tax, hidden ownership, mint functions) across 30+ chains. Contract verification, approval security checks, phishing site detection. Protocol TVL and fees via DeFi Llama. Stablecoin flows, ENS resolution, Fear & Greed Index, crypto prices. VASP verification against ESMA's MiCA register. Pre-built solutions for token project due diligence, DeFi protocol risk checks, and crypto counterparty KYB.
**Web and general purpose.** URL-to-markdown, structured web scraping, DNS, SSL, WHOIS, domain reputation, plus things like forex, job board search, npm/PyPI package info.
Everything returns structured JSON, gets continuously tested in the background, and produces an audit trail with provenance metadata. The quality scores are public so an agent can check reliability before making a call.
The x402 gateway sits on top of the same catalog as the traditional API. Anything available through the REST API with an API key is also available through x402 with USDC. Discovery endpoint at `/.well-known/x402.json`, full catalog at `/x402/catalog`.
Still early. The x402 standard itself is young and agent-to-agent commerce is more talked about than practiced right now. But the infrastructure for "agent pays for data at the moment it needs it, no human approval step" seems worth building before demand arrives rather than after.
Current limitations: the platform is in early access. GoPlus coverage varies by chain (Ethereum and BSC strongest, smaller L2s have gaps). Etherscan V2 rate limits are tight. The ESMA MiCA register is new and sparse. A handful of EU registries intermittently block requests from certain IP ranges. Some capabilities are more reliable than others, which is why the quality scores exist.
If you're building something that needs data sources we don't cover yet, happy to hear what's missing.