
AgentPay (all tools)
io.github.noah-silverv1.1.0Updated Oct 1, 2026
Pay-per-call web extract, DNS/WHOIS/IP lookup, PDF/RSS/sitemap tools. x402 USDC on Base/Algorand.
Overview
Remote MCP server that lets an assistant extract web pages, look up DNS/WHOIS/IP data, and parse PDFs, feeds, and sitemaps on a pay-per-call basis.
- What it does
- Exposes eight paid tools: extract_page turns any URL into clean markdown with metadata and links; lookup_dns, lookup_whois, lookup_ip and lookup_domain_report return DNS records, RDAP registration data, IP ownership and a combined domain report; tools_pdf_text, tools_feed and tools_sitemap return per-page PDF text, normalized RSS/Atom/JSON feed items and site URL lists. Listing tools is free; each tool call is billed per request.
- When to use it
- Useful when an assistant needs live web page content, domain or network intelligence, or document and feed parsing without building its own scrapers or lookup clients. Best for occasional, metered calls where per-request pricing is preferable to a subscription.
- Requirements
- A remote Streamable HTTP endpoint; no local runtime or package is needed. Either an x402-capable client with a funded USDC wallet on Base or Algorand, or a prepaid credits API key sent as the Authorization header (Bearer). Network access to the AgentPay hosts is required.
Installation
In SourceWeft
- Open AgentPay (all tools) in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"agentpay-bundle": {
"type": "http",
"url": "https://agentpay.agentpay-apis.workers.dev/mcp"
}
}
}README
AgentPay — pay-per-call APIs and MCP tools for AI agents
Web extraction, domain/network intelligence, and document tools that agents can use without signing up. Pay per request with x402 in USDC on Base or Algorand, or prepay credits for an API key. Every product is available as a REST API and as a remote MCP server.
Machine-readable docs: /llms.txt ·
/openapi.json ·
/.well-known/x402
Endpoints and pricing
Same price on Base and Algorand. Invalid input is rejected before payment, and x402 payments are only settled if the call succeeds — failed calls cost nothing.
Paying
x402 (no account)
Call any endpoint. You get 402 Payment Required with a base64 PAYMENT-REQUIRED header (x402 v2) offering:
- Base —
eip155:8453, USDC0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, exact scheme (EIP-3009) - Algorand —
algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73k, USDC ASA31566704, exact scheme
Any x402 v2 client handles this automatically:
Full example for both networks: examples/x402-client.mjs.
Prepaid credits (fastest for repeated use)
GET https://agentpay.agentpay-apis.workers.dev/credits/buy?usd=5 (paid once via x402) returns { "apiKey": "ak_…" }.
Send Authorization: Bearer ak_… on any endpoint or MCP server. Failed calls are refunded automatically.
Balance: GET /credits/balance. Algorand holders can also pay by transfer: examples/buy-credits.mjs.
Using the MCP servers
Remote MCP over Streamable HTTP. Listing tools is free; tool calls are paid via x402
(params._meta["x402/payment"], per the x402 MCP transport) or with a credits key header.
Claude Code
Cursor / Claude Desktop / any client with remote MCP support
Example responses
GET /lookup/v1/whois?domain=anthropic.com
GET /lookup/v1/ip?ip=1.1.1.1
Data sources
DNS over HTTPS (Cloudflare 1.1.1.1), IANA RDAP bootstrap → authoritative registry RDAP servers, and the regional internet registries. Web, PDF, feed and sitemap tools fetch the URL you provide at request time.
Support
Open an issue in this repository.
Source: README.md at commit 5df9d36
Tools
0Version history
1- v1.1.0LatestOct 1, 2026
