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.

[Omi] Expose starred/highlighted moments in Developer API

The user requests that starred/highlighted conversation moments be exposed through the Developer API. Currently, these moments are only accessible in the Omi app, but programmatic access would enable integrations to process high-signal content.

Original Source

@@joshdavisind | 0 pts | 3d ago

## Summary Expose starred/highlighted conversation moments through the Developer API (`/v1/dev/` endpoints). Currently, users can star moments in the Omi app, but there is no way to access these starred moments programmatically via the API. ## Use Case I'm building an integration that processes Omi memories via webhooks (Memory Trigger). Starred moments represent high-signal content that the user has explicitly flagged as important. Being able to access these through the API would enable: - **Priority processing**: Integration apps could treat starred moments with higher priority than unstarred content - **Smart extraction**: Pull only the moments the user deemed important, rather than processing entire transcripts - **Bookmark sync**: Sync starred moments to external knowledge bases (Notion, Obsidian, etc.) - **Action item enrichment**: Cross-reference starred moments with action items for richer context ## Proposed Endpoints ### Option A: Filter on existing endpoints Add a `sta

Discussion

Loading comments...