
Vend Api Merchant
dev.paypercall.extractPublished by extract.paypercall.devOfficial publisherv1.0.4Updated Nov 2, 2026
Pay-per-call web intel: extract, search, link check, domain, geo, Nano. Settled via Nano x402.
Overview
Remote pay-per-call web intel API: page extraction, link checks, domain and IP lookups, web search, YouTube transcripts and arXiv metadata, paid in Nano.
- What you can do
- Extract clean text or markdown from web pages, PDFs and YouTube transcripts
- Pull structured fields with CSS selectors and list every anchor link on a page
- Check link status, redirect chains, TLS expiry and content drift
- Look up domain intelligence (DNS, WHOIS, SSL, headers) and IP geolocation
- Run web search and search AI job postings or arXiv paper metadata
- Query Nano account details such as balance, representative and pending blocks
- When to use it
- Useful when an assistant needs on-demand web extraction, link auditing, domain or IP reconnaissance, or quick search results without signing up for an API key, and you are willing to pay small per-request fees in Nano.
- Requirements
- A remote streamable HTTP endpoint; no account or API key. Each call first returns an HTTP 402 challenge, so a Nano (XNO) wallet is needed to send the stated amount and retry with the returned block hash in the X-PAYMENT header. Network access to the service is required.
Installation
In SourceWeft
- Open Vend Api Merchant 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.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.paypercall.extract%2Fvend-api-merchant/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"vend-api-merchant": {
"type": "http",
"url": "https://extract.paypercall.dev/mcp"
}
}
}README
Vend — Autonomous API Merchant
Pay-per-call APIs settled in Nano (XNO). No signup, no API keys — just HTTP 402 with an x402 v2 challenge.
Endpoints
Quick buyer guide
BUYERS_GUIDE.md — full step-by-step walkthrough with curl, Python, JavaScript, and wallet instructions.
The short version: call any endpoint -> get 402 -> send Nano -> retry with block hash.
How it works (buyer flow)
Python example
See examples/python-buyer.py for a full working script with error handling.
Conformance
All endpoints pass the Stelar x402 Doctor at 100.0/A:
- extract: https://api.stelardigital.com/doctor?url=https://extract.paypercall.dev/api/v1/extract
- check-link: https://api.stelardigital.com/doctor?url=https://check.paypercall.dev/api/v1/check-link
- domain-info: https://api.stelardigital.com/doctor?url=https://domain.paypercall.dev/api/v1/domain-info
- web-search: https://api.stelardigital.com/doctor?url=https://search.paypercall.dev/api/v1/web-search
- geoip: https://api.stelardigital.com/doctor?url=https://geoip.paypercall.dev/api/v1/geoip
- nano-info:
https://extract.paypercall.dev/api/v1/nano-info(nano.paypercall.dev DNS is still pointing at a dead deployment, so every advertised URL names this host)
x402 v2 challenge in both header and body. Per-endpoint subdomains. Bazaar input schema on every endpoint.
Discovery
- x402 manifest:
https://extract.paypercall.dev/.well-known/x402(also at check, domain, search) - OpenAPI spec:
https://extract.paypercall.dev/openapi.json(also at check, domain, search) - agent-tools.cloud: https://agent-tools.cloud/services/extract-paypercall-dev-sub822
Running locally
License
MIT
Source: README.md at commit a0cd84e
Tools
0Version history
6- v1.0.4LatestSep 25, 2026
- v1.0.3Sep 25, 2026
- v1.0.2Sep 20, 2026
- v1.0.1Sep 19, 2026
- v0.3.1Sep 19, 2026
- v0.3.0Sep 18, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts