CitationBench's API mines specific subreddits for structured user pain points, delivering contextual insights your custom SEO agents can act on. Generic APIs miss the nuance Reddit discussions contain.
# Mine a subreddit for user pain pointsPOST /v1/research/discuss> { "source": "reddit", "subreddit": "saas", "topic": "onboarding friction" }{ "pain_points": [ { "theme": "no in-app guidance", "frequency": 38, "sentiment": -0.74 }, { "theme": "too many steps to first value", "frequency": 27, "sentiment": -0.81 }] }# Results stored — pipe into blog or landing page agentresearch.discuss.research✓ 64 posts analyzed · 12 pain themes extracted · storedCommunity language is specific, contextual, and buried in threads. Most APIs flatten it into noise.
Generic sentiment APIs score tone but strip the specific complaint language your SEO agent needs to build relevant content.
Wide-net scraping tools pull Reddit data without subreddit scoping, returning irrelevant posts that dilute your research signal.
Raw Reddit JSON dumps require heavy pre-processing before any SEO agent can consume them, adding engineering work with no strategic value.
The fix
CitationBench's discussion research endpoint mines Reddit by subreddit and topic via research.discuss.research, returning structured pain themes, frequency counts, and sentiment scores your SEO agents can consume directly.
From pain-point mining through content creation and indexing, CitationBench composes the full workflow in a single API surface.
Reddit Research
Call research.discuss.research with a subreddit and topic to extract structured pain themes, frequency counts, and sentiment signals. Results are stored and immediately available for downstream content generation steps.
Audience Intel
POST /v1/research/icp generates segmented buyer profiles from a company URL, giving your agent the audience context it needs to interpret Reddit pain points accurately across different buyer segments.
Gap Analysis
After mining Reddit discussions, research.content_gap.find compares your content inventory against extracted pain themes and competitor coverage to surface the topics your audience is asking about that you have not addressed.
Content Production
Feed stored Reddit pain themes directly into produce.blog_post.create to generate long-form SEO content grounded in real user language. Bulk creation from keyword lists keeps pace with the volume agencies need.
Developer Access
Access research.discuss.research and all ~35 CitationBench tools from Claude Code, Cursor, or any MCP client via mcp.citationbench.com/mcp. No self-hosting required and no integration boilerplate to write.
How it works
An `sk_test_*` key lands in your dashboard instantly. No demo gate — start calling real endpoints with shape-complete responses.
`claude mcp add citationbench https://mcp.citationbench.com/mcp` from Claude Code, Cursor, or any MCP client. Or `curl` against `api.citationbench.com/v1/*` directly.
Every tool returns shape-complete demo data without auth, so your agent works before the user signs up. Tools across research, production, indexing, link-building, and agents.
Add `X-Workspace-Id: ws_***` to scope per client. Switch to a live `sk_live_*` key when you're ready. Same API surface, same SDK.
Why CitationBench
Hosted at mcp.citationbench.com/mcp. Works with Claude Code, Cursor, Claude Desktop, Windsurf, and ChatGPT Apps. No self-hosting required.
Every long-running call runs on Cyclonic workers — survives restarts, cancellable, resumable, streams via SSE. Production-safe by default.
One master API key, N client workspaces. Switch with a single `X-Workspace-Id` header. Per-client data isolation, bulk ops across all of them.
Every endpoint responds in shape-complete demo mode without auth, so you can build the agent before the user signs up.
FAQ
Give your SEO agents structured Reddit pain-point data from the API built for the job.
View MCP Docs