Structured data
RESTMCPx402
Afterwren
Public-data lookups for companies, geocoding, books and Wikipedia through REST and a remote MCP server.
Free tier
SOURCE-BACKED AGENT TOOLS
Discover x402 services before authorizing payment.
x402 discovery and a paid provider call are separate decisions. Use this collection to identify source-backed x402 interfaces, then review the provider’s operation, payment requirements and host support. Browsing this page or receiving a payment challenge does not authorize a wallet transaction or establish that a paid task has completed.
COMPARE THE PUBLISHED OPTIONS
How we review sources →6 catalogue listings
Alphabetical order. These are published metadata records, not a performance ranking. Pricing, connection requirements and evidence status remain visible on each profile.
Web extraction
RESTx402
Agent Utility API
REST utilities for compact YouTube context, workflow text transformations and commerce parsing.
Usage-based
Structured data
RESTMCPx402
agentic-endpoints
Pay-per-call agent utilities for scraping, PDF text, context compression and workflow state, exposed over HTTP with documented MCP support.
Usage-based
Web extraction
RESTx402
AgentReader
HTTP extraction utilities with per-request USDC payment through x402.
Usage-based
Browser tools
RESTx402
Steel x402
Scrape, screenshot or render pages using wallet payments.
Usage-based
Web search
RESTx402
You.com Search x402
Search the web with per-request wallet payments.
Usage-based
What to check before connecting
Review the complete payment requirement
Inspect the current provider documentation and the actual challenge for the intended operation. Confirm the network, asset, amount and spending limit in your host before any payment.
Separate a challenge from a result
An HTTP 402 response describes a payment-required state. A successful paid task needs its own result evidence; a captured unpaid challenge is not a completed transaction.
Keep permission explicit
A service can be worth discovering even when the agent has no permission to pay. Keep discovery constraints separate from wallet authorization and never infer spending permission from a directory listing.
Questions to resolve before integration
Does ToolSkipper pay x402 providers automatically?
No. Public discovery does not connect a wallet, send credentials or make a payment. Any later paid provider call requires a separately authorized workflow in your host.
Does x402 mean no account and no authentication?
Not necessarily. Review the particular documented operation, connection requirements and wallet setup. Account requirements and payment requirements are separate conditions.
Inspect the evidence, then choose.
Read source links and check dates before relying on a service. ToolSkipper discovery never connects accounts or authorizes a payment.
Connect your agent →