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), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Open Codesign] Enhance provider/gateway compatibility and external API integration

Strengthen API compatibility across various gateways and external API integrations by addressing inconsistencies in OpenAI-compatible interface implementations, /models endpoint availability, and support for different API endpoints like responses versus chat/completions.

Original Source

@@Sun-sunshine06 | 0 pts | 6d ago

# [Feature]: 加固 Provider / Gateway 兼容性与外部 API 接入 / Harden provider-gateway compatibility and external API integration ## Problem / pain point / 问题 Open CoDesign 已经支持多 provider、自定义 OpenAI-compatible endpoint、keyless provider、以及外部配置导入，但 API 兼容性仍然偏“隐式”： - 不同 gateway 只实现了部分 OpenAI-compatible 接口 - 有些 endpoint 有 `/models`，有些没有 - 有些支持 `responses`，有些只支持 `chat/completions` - `system` / `developer` role 行为不一致 - reasoning 支持依赖 provider 和 model - 外部配置导入正在增多，但每个来源仍然有独立逻辑 Open CoDesign already supports multiple providers, custom OpenAI-compatible endpoints, keyless providers, and external config import. The remaining pain is compatibility hardening: - different gateways partially implement OpenAI-compatible APIs - some endpoints expose `/models`, some do not - some providers support `responses`, others only `chat/completions` - role handling differs across gateways - reasoning support depends on provider/model - external imports are growing, but each source still has bespoke logic ## Proposed

Discussion

Loading comments...