Research agents don't browse — they gather sources. Every call to the x402 Search API returns structured results with title, URL, and snippet: citation-ready fields your agent can quote, rank, and follow without parsing HTML or fighting bot blocks.
POST https://x402.eleeth.com/api/search
{"query": "solid state battery energy density 2026", "num_results": 10}
Response: {"provider","query","results":[{"title","url","snippet"}]} — up to 10 sources per call, each with a snippet your agent can use to decide what to open next.
POST https://x402.eleeth.com/api/search with no payment header → HTTP 402 with payment requirements.X-PAYMENT header.Any x402 v2 client library (@x402/core / x402-fetch) handles this automatically.
What exactly does a result contain? Title, URL, and a text snippet (up to ~300 chars). No HTML, no scraping, no parsing.
How does this compare to giving my agent a browser? A browser session is slow, flaky, and expensive per page. One $0.01 call returns up to 10 structured sources.
Do I need an account? No. No signup, no API key, no dashboard. Point your agent at the endpoint and fund its wallet with USDC.
Run by Eleeth. Questions: seo@eleeth.com