Agentic developer social listening and AI search visibility
Built for B2B SaaS, AI, and DevTools, EarShots.dev powers your Agentic GTM. Our agentic social listening captures sentiment, friction, and buying signals across LinkedIn, X, Reddit, community threads, and coding agents, turning them into grounded replies, an AEO prompt universe, and citations where they matter most.
Works with
- Claude
- ChatGPT
- Codex
- Grok Bot
- GitHub
- X
- Dev.to
- Hashnode
From a scattered mention to a reply ready to send.
Listen
Pull conversations from GitHub, X, LinkedIn, Reddit, Hacker News, the developer web, and the networks where coding agents decide.
Kay Du
@kaydu
Anyone gotten the streaming API to work behind a proxy? Docs are not clear.
Questionrouted to Developer RelationsDrafted reply
Yes. Set STREAMING_TRANSPORT=sse and the client falls back behind proxies. Details are in the streaming doc.
docs/streaming.mdCHANGELOG v2.4Brain: voice, guardrailssend from the original postTriage
Every mention is sorted into a question, friction, a buying signal, praise, or muted with a reason.
Kay Du
@kaydu
Anyone gotten the streaming API to work behind a proxy? Docs are not clear.
Questionrouted to Developer RelationsDrafted reply
Yes. Set STREAMING_TRANSPORT=sse and the client falls back behind proxies. Details are in the streaming doc.
docs/streaming.mdCHANGELOG v2.4Brain: voice, guardrailssend from the original postDraft
AI drafts answers from up to ten grounding sources you control, with the sources attached.
Follows your Knowledge Hub: who you sell to, your voice, what you never sayKay Du
@kaydu
Anyone gotten the streaming API to work behind a proxy? Docs are not clear.
Questionrouted to Developer RelationsDrafted reply
Yes. Set STREAMING_TRANSPORT=sse and the client falls back behind proxies. Details are in the streaming doc.
docs/streaming.mdCHANGELOG v2.4Brain: voice, guardrailssend from the original postApprove
A person reviews it, then copies the reply and sends it from the original post.
Kay Du
@kaydu
Anyone gotten the streaming API to work behind a proxy? Docs are not clear.
Questionrouted to Developer RelationsDrafted reply
Yes. Set STREAMING_TRANSPORT=sse and the client falls back behind proxies. Details are in the streaming doc.
docs/streaming.mdCHANGELOG v2.4Brain: voice, guardrailssend from the original post
EarShots MCP
Did the agent choose your product? Find out why.
Ask your agent what helped, what got in the way, and which content and tracked prompts to prioritize next.
~/earshots
EarShots MCP connected
Did agents choose our product, and why? Show where they chose an alternative or got stuck. Draft an agentic content plan based on agent friction and agent praise, with the sources behind each recommendation.
● earshots - get_context_buzz (MCP)
└ Read product usage and blockers
● earshots - list_mentions (MCP)
└ Read friction and praise
● earshots - get_brain (MCP)
└ Check product facts and documentation
Agent Output
Turn agent decisions into useful content.
1. Chose your product
Why: The documented integration matched the task.
Content plan: Publish a working integration walkthrough with a copyable example.
2. Chose an alternative
Why: The agent could not confirm a required capability in the docs.
Content plan: Explain supported deployments, prerequisites and limits on one page.
3. Choice not recorded
Why: A setup blocker appears in the source, but the final choice is unknown.
Content plan: Add a troubleshooting guide with an expected result for each fix.
AEO / GEO Prompt Universe
Solve the cold start problem in AEO / GEO.
EarShots builds a prompt universe from real user questions, product friction, and buying signals. It then tracks AI search visibility, mention rate, and citation rate across the prompts your market actually asks.
Explore AI search visibilityAI search visibility
Rank score
61/100
Mentioned and cited
Mentioned in
53%
of answers mention you
Cited in
33%
link to your site
Average position
#2.1
152 answers read
| 1 | Acme | 53% | 2.1 |
| 2 | Competitor A | 46% | 2.8 |
| 3 | Competitor B | 38% | 3.4 |
| 4 | Competitor C | 31% | 4.1 |
AI search visibility
Rank score
61/100
Mentioned and cited across tracked prompts
Mentioned in
53%
of answers mention you
Cited in
33%
link to your site
Average position
#2.1
152 answers read
Visibility · Mention rate by AI engine
Brands · Highest visibility
| # | Brand | Visibility | Position |
|---|---|---|---|
| 1 | AcmeYou | 53% | 2.1 |
| 2 | Competitor ACompetitor | 46% | 2.8 |
| 3 | Competitor BCompetitor | 38% | 3.4 |
| 4 | Competitor CCompetitor | 31% | 4.1 |
Built for every role.
Same queue, different job. Pick a role to see what changes for them.
DevRel
DevRel command center
Every public developer question, answered from your own docs.
- Every real question in one queue, with the rest set aside
- Replies drafted from your documentation with citations attached
- Repeat questions flagged as documentation fixes
- A person approves before anything is sent
Before
Manually scanning GitHub, X, and Hacker News across every repo and handle, hoping to catch the question before someone else answers it wrong.
After
Every real question lands in one queue with a reply already drafted from the docs. Approve it, or fix the docs when the same question keeps coming back.
Dev Marrow @devmarrow
github · 26m ago
Still can't figure out the OAuth callback. The docs say auto-redirect, but it 404s every time. Am I missing a setting?
Draft grounded in your docs
Check that the registered redirect URI exactly matches the URL your app sends, including the scheme, host, port, and trailing slash. The callback should point to your app's /auth/callback path, not the site root.
EarShots allows you to understand and take action on product conversations.
Integrations
Plugs into the tools your team already reports from.
Start with the conversations happening now.
Connect your sources and documentation, then give your team one place to listen and act.
Always human-approved. No auto-replies, ever.
EarShots was built from the start around an agent that reads, sorts, and drafts.