If you're building autonomous agents, you've hit this wall: your agent needs to enrich a company by domain or size up a wallet before it sends funds, but every good data source (Clearbit, Apollo, Nansen) is signup- and KYC-gated. An autonomous agent can't click "Sign up," verify an email, and paste an API key.
So I put a small data gateway behind x402 — HTTP 402 + pay-per-call USDC on Base. No account, no API key, no subscription. Your agent does a GET, gets a 402 with the price, pays a couple cents of USDC, and replays the request. That's it.
30-second install (Claude / Cursor / any MCP agent)
npx skills add epistemedeus/x402-data-gateway-skills --all
That drops in Agent Skills that teach your agent when to call each endpoint — so "enrich this company" or "profile this wallet" just works.
The two I actually built this for
company-enrich — a domain → clean firmographics (name, description, tech stack, socials, contact), plus two layers generic enrichment APIs don't return:
- DNS / email-infra (MX, SPF, DMARC — great for outreach validation)
- an AI-search-readiness score (JSON-LD, OpenGraph, robots/sitemap/llms.txt) — "can an AI assistant actually read and cite this site?"
wallet-enrich — a Base/EVM 0x address → on-chain profile: EOA vs contract, native + token holdings, ERC-20/721/1155 metadata, EIP-1967 proxy detection, activity, and the Basename (e.g. jesse.base.eth), forward-confirmed so it's never wrong. The crypto-native counterpart for sizing up a counterparty before you transact.
Calling it from code (x402-fetch)
import { wrapFetchWithPayment } from "x402-fetch";
// walletClient = a viem wallet funded with a little USDC on Base
const fetchPaid = wrapFetchWithPayment(fetch, walletClient);
const res = await fetchPaid(
"https://x402-url-extractor-production.up.railway.app/wallet-enrich?address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
);
console.log(await res.json());
// -> { type: "contract", contract: { standard: "ERC-20 (token)", token: { symbol: "USDC", ... } }, profile: "token-contract:USDC" }
Settlement is non-custodial: the facilitator verifies your signed EIP-3009 authorization and the USDC moves straight to the service wallet. Nobody holds your funds.
Also exposed as an MCP server
Prefer MCP? The same tools are an x402-gated MCP server (tools/list is free, tools/call is paid), listed in the official MCP Registry as io.github.epistemedeus/x402-data-gateway. tools/list to see all six; pay-per-call on the ones you use.
What's in the gateway
| Skill | Does | Price |
|---|---|---|
| company-enrich | domain → company intel + AI-readiness + DNS | $0.02 |
| wallet-enrich | 0x address → on-chain profile + Basename | $0.02 |
| web-extract | URL → structured JSON or LLM-ready Markdown | $0.05 |
| repo-security-scan | static supply-chain scan of a GitHub repo before you install it | $0.20 |
| schema-generate | business site → paste-ready JSON-LD bundle | $0.25 |
Public data only, deterministic, pay-per-call. Repo + full docs: https://github.com/epistemedeus/x402-data-gateway-skills
If you wire it into an agent, I'd genuinely like to hear what task you used it for.













