canonical: https://jentic.com/apis/painspotter.ai/painspotter # Pain Spotter Public API The Pain Spotter Public API returns AI-scored business opportunities mined from user complaints on Reddit, Hacker News, Product Hunt, Stack Exchange, and other open communities. Each opportunity carries a Build, Validate, or Skip recommendation, an overall score, and sub-scores for pain point intensity, willingness to pay, technical difficulty, and sustainability, along with target audience and monetization model. The detail view adds a market size estimate, key features, competitors, differentiation, and risks, and a companion blog endpoint serves the published analyses with their raw Markdown body. Access is read-only. ## For AI agents Search AI-scored startup and product opportunities mined from Reddit, Hacker News, Product Hunt, and Stack Exchange, filter them by platform, score, or Build/Validate/Skip recommendation, and read the full opportunity analysis or related blog article. ## Scope Does not post to communities, return raw Reddit or Hacker News threads, or track brand mentions. Use for reading Pain Spotter's scored business opportunities and published analyses only. ## Capabilities - Filter opportunities by platform, channel, keyword q, min_score, and a Build, Validate, or Skip recommendation through `/api/v1/opportunities` - Restrict results to online-deliverable ideas with the online_only parameter - Read an opportunity's market_size_estimate, key_features, competitors, differentiation, and risks from `/api/v1/opportunities/{id}` - Compare ideas on pain_point_intensity, willingness_to_pay_score, tech_difficulty, and sustainability_score - Search published blog analyses with q and fetch an article's body_md by slug ## Use cases ### Agent idea research through Jentic A founder asks their agent for validated product ideas in a niche. Through Jentic the agent calls listOpportunities with q set to the niche, recommendation set to Build, and a min_score threshold, then fetches each top result with getOpportunity to read competitors and risks before writing a shortlist. Your own Jentic One instance injects the X-API-Key value, so the agent never holds it. Example prompt: GET `/api/v1/opportunities` with q 'invoicing', recommendation 'Build', and min_score 75, then GET `/api/v1/opportunities/{id}` for the top three and summarise their competitors and risks ### Community pain point monitoring by platform Product teams track what users complain about on a specific community. Filtering by platform and channel returns the scored opportunities mined there, each with evidence_count showing how many source posts back it, so a team can watch a subreddit or forum for recurring problems worth solving. Example prompt: GET `/api/v1/opportunities` with platform 'reddit', page_size 20, and online_only true, then rank the results by evidence_count ### Content pipeline from published analyses Newsletters and research digests reuse Pain Spotter's published analyses. GET `/api/v1/blog` lists articles with excerpt, tags, and related_opportunity_id, and GET `/api/v1/blog/{slug}` returns the article including its raw Markdown body_md, ready to quote or summarise. Example prompt: GET `/api/v1/blog` with q 'saas', then GET `/api/v1/blog/{slug}` for the newest result and summarise its body_md in five bullet points ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/opportunities` | List opportunities with filters | | GET | `/api/v1/opportunities/{id}` | Get opportunity detail | | GET | `/api/v1/blog` | List blog analyses | | GET | `/api/v1/blog/{slug}` | Get an article with Markdown body | ## Key resources - **Opportunities** — Scored business opportunities with filters and pagination, plus full detail per opportunity - **Blog** — Published opportunity analyses with search and raw Markdown bodies ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 60 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 73 / 100 - Developer Experience & Jentic Compatibility: 65 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/painspotter.ai/painspotter/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Pain Spotter by hand means passing the X-API-Key header, tracking a monthly call quota, and paging through filtered results. Through Jentic you install once, import Pain Spotter from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Pain Spotter puts the opportunity id and article slug in the URL path, so a rule can pin your agent to a single opportunity or article. You choose which of the four read operations it may call, which also bounds how fast it uses the monthly quota. - **Credential handling:** Your Pain Spotter API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find startup ideas from Reddit complaints', and Jentic returns the matching Pain Spotter operation with its input schema so the agent sets the right filters. ## Related APIs - **Exa API** — Web search built for agents, usable to find discussions directly - **Reddit API** — Posts and comments from Reddit communities - **Product Hunt API** — Product launches, makers, and comments ## FAQ ### What authentication does the Pain Spotter Public API use? The Pain Spotter Public API authenticates with an API key sent in the X-API-Key header per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs. ### What are the rate limits for the Pain Spotter Public API? The spec states monthly quotas by plan: Free 20, Pro 1,000, and Business 5,000 calls per month, resetting on the 1st of each month UTC. ### Can I filter Pain Spotter opportunities by recommendation and score? Yes. GET `/api/v1/opportunities` accepts recommendation with the values Build, Validate, or Skip, a min_score threshold, platform, channel, a keyword q, and online_only, plus page and page_size for pagination. ### How do I find buildable ideas through Jentic? Install Jentic One, add the Pain Spotter Public API from the Jentic API Directory, and store your API key once. Your agent searches for 'find scored business opportunities', gets listOpportunities with its input schema, and calls it with recommendation set to Build. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a Pain Spotter MCP server? You don't need an MCP server to give your agent the Pain Spotter Public API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. ### Can I limit what my agent is allowed to do with the Pain Spotter Public API? Yes. The API is read-only, so the main reason to limit it is quota: write a rule that allows only listOpportunities and getOpportunity, and the agent cannot spend calls on the blog endpoints. Your own Jentic One instance logs what it called.