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.

[x402 API] Migrate payment middleware to X402_RELAY RPC service binding

Requests migration of the 'x402-api' payment middleware from the synchronous HTTP '/settle' path to the 'X402_RELAY' RPC service binding, enabling a queue-backed async path with retry semantics to avoid nonce conflict failures.

Original Source

@@whoabuddy | 0 pts | 20d ago

## Summary `x402-api` still uses the synchronous HTTP `/settle` path via `X402PaymentVerifier` for payment verification. `landing-page` and `agent-news` have already migrated to the `X402_RELAY` service binding with the `RelayRPC` entrypoint, which routes payments through a queue-backed async path with retry semantics. The HTTP path has no queue retry and is directly exposed to the nonce conflict failures documented in [x402-sponsor-relay#236](https://github.com/aibtcdev/x402-sponsor-relay/issues/236). ## Evidence `src/middleware/x402.ts:364-379` (current HTTP path): ```typescript // Verify payment with settlement relay using v2 API const verifier = new X402PaymentVerifier(c.env.X402_FACILITATOR_URL); log.debug("Settling payment via settlement relay", { relayUrl: c.env.X402_FACILITATOR_URL, expectedRecipient: c.env.X402_SERVER_ADDRESS, minAmount: paymentRequirements.amount, asset, network: networkV2, }); let settleResult: SettlementResponseV2; try { settleResult = awa

Discussion

Loading comments...