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.

[Wetware] Integrate x402 payment protocol for capability interactions

Requests x402 payment integration for capability interactions within Wetware, where the host HTTP server would respond with 402 and payment terms, with settlement via USDC on Base.

Original Source

@@lthibault | 0 pts | 2/26/2026

Capability interactions can require payment via x402 (HTTP 402 Payment Required). The host HTTP server responds with 402 and payment terms. Settlement via USDC on Base. Ref: https://github.com/coinbase/x402 ## Current Context (2026-03-30) Wetware now has: - **HTTP capability track** (#241-#246, open) — phased implementation of HTTP support including FastCGI mode - **Cell::http type** (#291-#293, shipped) — WASM binaries can declare HTTP path prefixes via cell.capnp - **Wallet capability** (#216, shipped) — Membrane-attenuated signing constraints - **MPP (Machine Payments Protocol)** — launched March 2026 by Stripe/Tempo, live across 50+ services, submitted to IETF as HTTP 402 x402 integration naturally fits the HTTP track. A `Cell::http` binary serving a paid endpoint would: 1. Receive HTTP request via FastCGI on stdin 2. Check for x402 payment header 3. If missing, respond with 402 + payment terms 4. If valid, process the request using granted capabilities 5. Settlement via wallet

Discussion

Loading comments...