payfetch — alternative #1 to voice-mcp
📇 🏠 🍎 🪟 🐧 - Non-custodial paying-fetch client for agents that pay APIs over HTTP 402 (x402, USDC on Base). The operator sets hard per-call/p...
Search tools, jump to categories, and open key destinations
Recorded alternatives
Every candidate below sits in AI Coding. What ends up on this page is decided entirely by a recorded score — not by bidding, not by editor taste. Review both records, check current vendor terms, then decide.
📇 🏠 🍎 🪟 🐧 - Non-custodial paying-fetch client for agents that pay APIs over HTTP 402 (x402, USDC on Base). The operator sets hard per-call/p...
📇 ☁️ - Settlement protocol MCP server for institutional cross-border USDC transactions on Base mainnet. 14 tools: 10-source Stability Oracle...
📇 ☁️ - x402-native API gateway with 20+ capabilities (web-extract, web-search, translate, image-generate, screenshot, PDF, OCR, and more) pa...
📇 ☁️ - Convert any URL into clean, agent-ready Markdown with structured metadata (title, byline, published date, language). Pay-per-use via...
🐍 ☁️ - Runtime discovery layer for x402-payable APIs. Agents discover and route to pay-per-call x402 endpoints by capability, get quality-ra...
Each candidate is a live catalogue record in the same primary category, picked by a deterministic score that Oryxen records in its catalogue: how many meaningful words the two listings share, whether their pricing classes oppose (a paid product against a free one), whether both are open source, and whether either record is featured. The same catalogue state always produces the same list — no randomness, no manual ranking.
No. Rows are ordered only by the recorded score, highest first, with alphabetical ties — payment never influences the order, nothing here is paid placement, and Oryxen charges no listing or placement fee.
Always verify current terms with voice-mcp directly — Oryxen records pricing classes, not live quotes.