RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Paystack MCP Server] Add x402 payment protocol support for agent-to-agent transactions

Requests support for the x402 payment protocol within Paystack's MCP server to enable autonomous agent-to-agent payments for API calls, data, and compute, as the current system focuses on human-to-merchant payments.

Original Source

@@up2itnow0822 | 3 pts | 3/16/2026

Paystack's MCP server handles human-to-merchant payments through agents. But what about agent-to-agent payments where there's no human in the loop? **The gap:** Your current MCP server lets an agent initiate a Paystack checkout on behalf of a user. That works for e-commerce. But the growing use case is agents paying other agents for API calls, data, compute - autonomously and without a human credit card. **What x402 solves:** x402 is the HTTP payment protocol (started by Coinbase, now adopted by AWS and others). When an API returns HTTP 402, the calling agent: 1. Reads payment terms from the response header 2. Signs a USDC payment from its own wallet 3. Retries with payment proof attached No checkout page. No credit card. No human. **Integration proposal:** We maintain [Agent Wallet SDK](https://github.com/up2itnow0822/agent-wallet-sdk) and [AgentPay MCP](https://github.com/up2itnow0822/agentpay-mcp) - open-source x402 payment infrastructure for AI agents. A Paystack x402 bridg

Discussion

Loading comments...