EarShots.dev
Open navigation

Agentic developer social listening and AI search visibility

EarShots turns developer mentions across GitHub, X, LinkedIn, and the web into grounded replies, product signals, and an AEO/GEO prompt universe that tracks AI search visibility.

See how it works

Works with

  • Claude
  • ChatGPT
  • Codex
  • Grok Bot
  • GitHub
  • X
  • LinkedIn
  • Reddit
  • Dev.to
  • Hashnode
Insights/ Queue
MK
Last synced 4 min ago · 6 sources connected
MentionTrackStatus

Dev Marrow

github · 26m

QuestionDraft

Tomás Lind

x · 3h

FrictionOpen

Amara Osei

linkedin · 5h

Buying signalDraft

Ruth Alvarez

linkedin · 5h

PraiseDraft

From a scattered mention to a reply ready to send.

  1. 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 Relations

    Drafted 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, guardrails
    send from the original post
  2. Triage

    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 Relations

    Drafted 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, guardrails
    send from the original post
  3. Draft

    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 say

    Kay Du

    @kaydu

    Anyone gotten the streaming API to work behind a proxy? Docs are not clear.

    Questionrouted to Developer Relations

    Drafted 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, guardrails
    send from the original post
  4. Approve

    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 Relations

    Drafted 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, guardrails
    send from the original post

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 visibility

Illustrative product view with fictional posts, brands, and figures.

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.

Mentions/ DevRel
MK
Last synced 4 min ago · 6 sources connected

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.

See all integrations

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.