# EarShots > EarShots is a developer social listening and AI search visibility product. It finds public conversations about a developer product, sorts them into five tracks, checks public claims against the product's documentation, tracks how AI assistants answer buyer prompts, and drafts documentation-grounded replies on X, LinkedIn and Reddit for human approval. EarShots is built for technical go-to-market teams: developer relations, developer marketing, support, product, and sales. It listens across GitHub, X, LinkedIn, Reddit, Hacker News, Dev.to, Hashnode, blogs, and the wider public developer web, and reads the agent networks where coding agents decide what to install. Every mention is sorted into questions, friction, buying signals, praise, or muted. Muted items carry a reason and can be moved into any track in one tap. Posts by the company's own team, executive interviews, and neutral mentions are kept out of customer tracks, because they are not customer feedback. Ears, the EarShots AI agent, prepares reply drafts from documentation the customer connects. Drafts include citations. Drafting is limited to replies on X, LinkedIn and Reddit; for other posts EarShots offers "Open original post" and "Create ticket" instead. EarShots never posts, comments, or sends messages on a customer's behalf. A person reviews every draft and sends it from the original post. Beyond the queue, EarShots includes: - AEO / GEO Prompt Universe: tracks the prompts buyers ask ChatGPT, Gemini, Google AI Overviews and Claude, and records whether the product is mentioned or cited, which competitors are mentioned, which domains are cited instead, and share of voice across branded and unbranded prompts. Search Sync can be run on demand. - Ground Truth Review: one place to review findings, check the facts in public articles against connected documentation, and inspect individual claims with their source and evidence. A claim without documentation backing is marked "Not enough to judge", never "Accurate". High and medium findings can get an independent web check. - Knowledge Hub: the reviewed facts, guardrails, and reference material that ground drafts and fact checks. Proposed facts need human confirmation before they are used. - Context Buzz: public GitHub usage patterns, blockers, and coding agent activity, in one filterable evidence list. - Competitor Signal: evidence-backed reactions to named rivals, on every paid plan. - Launch Planner: a watch window of up to 30 days on a named release. - Stats: volume, channel mix, tracks, and team response over time. - CLI and MCP: the same workspace from a terminal or an AI client, with drafts only. - Teams: shared workspaces with assignments, notes, and a single workspace admin. ## Product - [Full documentation context](/llms-full.txt): Complete product surfaces, industry definitions, and glossary entries in one full markdown payload. - [EarShots homepage](/): Product overview and an interactive example of the listening, classification, drafting, and approval workflow. - [Pricing](/pricing): Starter, Growth, and Enterprise plan details, feature availability, and common billing questions. - [Enterprise](/enterprise): Social listening and AI search visibility across product workspaces and teams. Includes reviewed replies and campaign materials, Listen Enrich contact context for CRM and outbound workflows, saved-contact exports through the app, MCP, CLI and API, plan capacity and rollout requirements. - [Developer social listening](/developer-social-listening): An explanation of developer social listening, the signals it covers, and how it differs from broad social monitoring. - [AEO / GEO platform](/aeo-prompt-universe): The AEO and GEO platform for dev tool companies, B2B SaaS and AI startups. Tracks whether ChatGPT, Claude, Gemini and Google AI Overviews name and cite a product for the prompts buyers and coding agents ask, with use cases per segment. - [Ears Cite](/aeo-citations): Managed citation outreach. EarShots finds the authors of articles AI engines already cite for your prompts and asks them to include your product where it fits. You never write or review an email. ## Listen Enrich - [Listen Enrich](/product/listen-enrich): Professional context from exact LinkedIn personal profiles for sales teams, with separate verified work-email lookup when eligible. Credit packs: 500 credits for $100, 2,500 for $400; profile 1 credit, verified work email 5 credits; no-match lookups free. - [Listen Enrich guide](/docs/listen-enrich): App and MCP estimate, explicit confirmation and status flow. Repository CLI contacts/enrich commands; npm release pending. REST GET /api/v1/contacts requires contacts:read and reads saved contacts only, without paid work. ## Product surfaces - [Product overview](/product/agentic-social-listening): Every EarShots surface on one page. - [Agentic Social Listening](/product/agentic-social-listening): The single sorted feed. Public posts from GitHub, X, LinkedIn, Reddit, Hacker News and the developer web, plus agent decision trails, filed into questions, friction, buying signals, praise, or muted with a reason, with a 180 day lookback. - [AEO / GEO platform and Prompt Universe](/aeo-geo-platform): Tracked AI search prompts with mention rate, citation rate, competitors mentioned, cited domains, excerpts showing where the brand appears, and share of voice. 100 prompts on Starter, 250 on Growth, and credit-based prompts on Enterprise sized with the EarShots team. - [Ground Truth Review](/product/accuracy-maxxing): Findings, fact checks, and claim cards for public articles, checked against connected documentation, with a correction note a person sends. - [Knowledge Hub](/product/knowledge-hub): Reviewed product facts, guardrails, and reference material, with provenance, that ground every draft and fact check. - [Context Buzz](/product/context-buzz): Public GitHub usage patterns, blockers, and coding agent signal in one evidence list with category filters. Reply drafting is disabled for repositories the workspace does not own. - [Competitor Signal](/product/competitor-signal): 3 rivals on Starter, 5 on Growth, 15 on Enterprise, read over a 120 day window, with sentiment, praise, complaints and launch versus production use. - [Stats](/product/stats): Go to market rollup in two tabs, your own performance and competitor insights, over 7, 30 and 90 day windows. - [Agent Signal](/product/agent-signal): What coding agents decide about your product. Which package they install, where your documentation fails them, what they fix, and which agent reviewed which. - [Launch Planner](/product/launch-planner): Track a named release over 7, 14, or 30 days and read developer reaction while the launch is live. Growth and Enterprise plans. - [Ears Cite](/aeo-citations): Managed outreach to the authors of articles AI engines cite, closing the gap Prompt Universe measures. - [CLI and MCP](/product/cli-mcp): The queue from a terminal with @earshotsdev/cli or from an agent session over MCP. Tools read data and store reply drafts; a person sends them. ## Industries - [Industries overview](/industries): The company types where public developer conversation is the main source of truth about a product. - [Developer tools and APIs](/industries/developer-tools): For teams selling tools and application programming interfaces (APIs) to developers. Review integration questions, public repository usage and competing tools with the source behind each finding. - [AI and language-model infrastructure](/industries/ai-infrastructure): For model providers, inference platforms and AI tooling teams. Review what builders are trying to run, the limits they encounter and the alternatives they consider. - [Open source companies](/industries/open-source): For maintainers and companies with a hosted or commercial offering. Read public implementation questions alongside requests for managed operations, team controls and support. - [Cloud and DevOps platforms](/industries/cloud-devops): For hosting, deployment and infrastructure teams. Review migration discussions with the workload, operating costs and deployment constraints that give them meaning. - [Security and DevSecOps](/industries/security): For application security and developer security teams. Review public integration friction and claims about your coverage against the documentation and evidence available. - [Data and analytics platforms](/industries/data-platforms): For data integration, orchestration and analytics teams. Review public reports of connector limits, schema changes and workload trade-offs with their original context. - [Platform engineering](/industries/platform-engineering): For internal developer portal and platform-tool vendors. Review public discussions about service ownership, paved paths and the work required to keep a platform useful. - [Frontend and design systems](/industries/frontend-design-systems): For component libraries, build tools and design-system vendors. Review implementation questions about accessibility, framework compatibility and customization. - [Edge, IoT and hardware](/industries/edge-iot-hardware): For device software development kit (SDK), firmware and connectivity teams. Review public hardware integration reports without losing the board revision, firmware or operating conditions. - [Blockchain infrastructure](/industries/web3-infrastructure): For node, wallet, indexing and blockchain development-tool providers. Review integration friction and provider comparisons in the context of a specific network and application. - [Fintech and payments APIs](/industries/fintech-payments): For payment, ledger and financial integration platforms. Review public developer questions about webhooks, retries and test environments with the documentation behind a possible answer. - [Ecommerce and storefront platforms](/industries/ecommerce-platforms): For commerce, checkout and storefront platform teams. Review what merchants, agencies and integrators need from a migration before deciding which claims or examples to improve. - [Game engines and realtime infrastructure](/industries/gaming-realtime): For engine, multiplayer, voice and game-backend vendors. Review studio integration questions with their engine version, target platforms and multiplayer requirements. - [Video game studios and publishers](/industries/video-games): For studios, publishers and gaming platforms. Review public player feedback and discovery questions by title, platform and release, so community, product and marketing teams can choose what to address. - [B2B software platforms](/industries/b2b-saas-platforms): For business software with integrations and extensible workflows. Review what administrators and integrators need when they compare, configure or replace a platform. - [Identity and authentication](/industries/identity-auth): For authentication, single sign-on (SSO) and identity platform teams. Review public integration questions with the tenant configuration, framework and account requirements attached. - [Communications APIs](/industries/communications-apis): For email, messaging, voice and video platform teams. Review public integration reports with the channel, region and callback behavior that make them actionable. - [Customer support platforms](/industries/customer-support-cx): For help desk, support inbox and customer experience (CX) platform teams. Review how administrators and developers describe routing, integrations and the tools they are replacing. - [Marketing and growth automation](/industries/martech-automation): For marketing automation, analytics and experimentation platforms. Review integration friction and attribution questions with the event definitions and workflow in view. - [Developer marketing and DevRel agencies](/industries/devrel-agencies): For developer relations (DevRel), technical content and developer marketing agencies. Organize listening around each client's product, audience and decision, with separate workspace context. ## Documentation - [Documentation overview](/docs): Product concepts, safety rules, and links to setup and workflow guides. - [Quickstart](/docs/quickstart): Create a workspace, add listening sources and documentation, run a sync, and review the first results. - [Connect sources](/docs/sources): Configure GitHub, X, LinkedIn, and open web sources, choose useful search terms, and understand refresh behavior. - [Connect documentation](/docs/documentation): Add product documentation used to ground factual reply drafts and citations. - [Understand sorting](/docs/sorting): Learn how Ears classifies mentions as questions, friction, buying signals, praise, or muted. - [Draft and approve replies](/docs/replies): Review source content, documentation citations, draft history, edits, and human approval. - [Team collaboration](/docs/team): Assign mentions, leave notes, hand work to teammates, and review decisions together. - [Prompt Universe](/docs/prompt-universe): Add tracked prompts, run Search Sync, and read mention rate, citation rate, cited domains, and share of voice. - [Ground Truth Review](/docs/accuracy): Check claims in tutorials, comparisons, newsletters, and articles against connected documentation. - [Context Buzz](/docs/context-buzz): Group GitHub activity by product usage patterns and developer blockers while preserving source context. - [Agent Signal](/docs/agent-signal): Sources, the six agent decisions, how attribution works, and the question of whether EarShots ever posts on an agent network. - [Competitor Signal](/docs/competitors): Track 3 rivals on Starter, 5 on Growth, or 15 on Enterprise and review likes, dislikes, themes, adoption stages, and GTM implications. - [Stats](/docs/stats): Report listening volume by day, channel, and track, team response, and competitor coverage, over a window of up to 180 days. - [Launch Reactions](/docs/launch-reactions): Record a release with a watch window of up to 30 days and read how developers reacted, sorted into praise, complaint, demand, and question. Growth and Enterprise plans. - [Agents](/docs/skills): How AI agents work with an EarShots workspace and what they are allowed to do. - [Skills](/docs/skills): Writing and review skills agents can use with EarShots. - [Plans and limits](/docs/plans): Compare source, workspace, team, usage, and competitor allowances across plans. ## Agent access - [Workspace API reference](/docs/api): Preview REST API for stored Mentions, Sentiment rollups, Ground Truth findings and claims, verified Brain nodes, AI Search rollups, competitors and source evidence, Context Buzz, reply drafts, campaigns and campaign stages. Keys are workspace-bound, scoped, expiring and revocable, created by owners/admins in Settings > API access. - [OpenAPI 3.1](/openapi.json): Machine-readable operation, filter, response and error reference. Canonical entry /api/v1 redirects with 307 to /api/public/v1 on the same origin. Preserve Authorization: Bearer credentials through redirects. Never put keys in query strings. REST collection reads default to 25 records, accept at most 100 per page and use inclusive UTC windows of at most 180 days. Follow meta.next_cursor with unchanged date filters. Writes to product content, generation, approvals and posting are not implemented, regardless of reserved permission scopes. Signed outbound webhooks support mention.updated, campaign.stage.updated and ground-truth.finding.created, with 10 active subscriptions per workspace, five queued delivery attempts and exact HTTPS Zapier/Make receiver hosts only. Subscriptions stop if their creating key expires, is revoked or loses manager access. Public API production access and receiver delivery remain unverified until publication. Updated October 22, 2026. - [MCP guide](/docs/mcp): Connect an MCP-compatible AI client such as Claude to an EarShots workspace using OAuth. - [CLI guide](/docs/cli): Install and use the EarShots command-line client for workspace, mention, insight, source, and draft workflows. MCP and CLI access follow the same workspace permissions as the web product. Agent-created replies remain drafts. Saving a draft never publishes it. ## Blog - [EarShots blog](/blog): Product notes and practical writing about developer conversations, product context, and careful responses. - [Introducing EarShots.Dev](/blog/social-listening-aeo-platform): Agentic developer social listening and AI visibility in one platform for technical GTM teams. ## Company EarShots was founded by David Zeledon, CEO and Founder. Dave spent 15+ years in marketing and growth for developer platforms. He led social, search, and product-led growth across v0.app at Vercel, including the biggest month in company history. At Google Labs he was a Developer Relations Engineer leading growth for Jules and a project lead on the Situationally Aware Agents experiment. He ran growth for AthenaHQ.ai, a leading AEO and GEO platform, and for HockeyStack as interim CMO. He has worked in AI search since 2019. EarShots exists because developers discuss stacks in public, and go to market teams need one place that reads that conversation and shows how AI assistants judge their product. - [About the team](/about): David Zeledon, founder and CEO of EarShots, and the story behind the product. ## Key product facts - Supported listening surfaces include GitHub issues and discussions, X, LinkedIn, Reddit, Hacker News, Dev.to, Hashnode, blogs, the wider public developer web, and the agent networks where coding agents make decisions. - Every mention is classified as a question, friction, a buying signal, praise, or muted with a reason. - Factual reply drafts are grounded in up to ten customer-provided sources, including documentation URLs and uploaded markdown files, and include citations. - Casual acknowledgements can be drafted without documentation when no factual product claim is needed. - Reply drafting covers replies on X, LinkedIn and Reddit only. Other posts get Open original post and Create ticket. - Posts from the company's own team, executive interviews, and neutral mentions are kept out of customer tracks. - Ground Truth Review checks article claims against connected documentation. Claims without documentation backing read Not enough to judge. - Prompt Universe tracks 100 prompts on Starter, 250 on Growth, and credit-based prompts on Enterprise sized with the EarShots team, across ChatGPT, Gemini, Google AI Overviews and Claude. - Context Buzz summarizes how developers use a product in GitHub projects and where they get blocked. - Competitor Signal is on every paid plan: 3 rivals on Starter, 5 on Growth, 15 on Enterprise. Agent Signal is on Growth and Enterprise. - Launch Reactions is limited to Growth and Enterprise. A watch window defaults to 7 days and can run up to 30. - Human approval is mandatory. EarShots does not auto-post or contact authors. - Plans are billed monthly. Starter begins at $249 per month and Growth at $400 per month. Enterprise pricing is discussed with the EarShots team. ## Resources - [Resources](/resources): Searchable library of whitepapers, published blog posts, eighteen AI Search News Hub guides, developer listening, the glossary, documentation, and the product video. Filter by format and topic. Every card has its own thumbnail. Articles keep their original URLs. The site menu links straight to this page. - [Developer marketing in the age of AI, Fall 2026](/resources/developer-marketing-in-the-age-of-ai): A sourced report on the AI trust gap among developers, community bans on generated content, AI results for marketing teams, the shift of discovery into docs and AI answers, the channels that still work, response time, and a five step playbook. Figures cited to Stack Overflow, Draft.dev, HubSpot, Jasper, GlobalSpec, TREW Marketing, Similarweb, DevTune, daily.dev, Val Town, and Adobe. ## AI search research for agents Agents can use the [EarShots CLI](/docs/cli) or [Model Context Protocol server](/docs/mcp) to read an authorized workspace. After signing in, inspect `earshots tools --json`. Read stored prompts with `earshots call aeo_get_prompt_universe '{"limit":10}' --json`, then read a returned prompt's answers with `earshots answers PROMPT_ID --days 30 --json`. Replace PROMPT_ID with the returned prompt_id. These read commands do not trigger new engine runs or publish content. The [AI search prompt strategy guide](/ai-search/ai-search-prompt-strategy) explains prompt selection, page evidence, fan-out and measurement. Its product images use fictional demo data. Preserve exact prompts, engine names, capture dates and sources in downstream analysis; product illustrations are not observed results. ## AI Search News Hub - [AI Search News Hub](/ai-search): Source-linked guides to AEO, AI citations, Google AI Search, AI crawlers, browser agents and developer listening. Every claim links to a numbered source with a verification date. - [Answer engine optimization and developer social listening](/ai-search/aeo-and-social-listening-guide): Connect answer engine optimization with developer social listening. Compare citation research, review crawler access and measure product visibility accurately. - [How people use ChatGPT in 2026: implications for product discovery and AEO/GEO](/ai-search/chatgpt-usage-2026): OpenAI Signals shows a rising share of product-information research. See what the findings mean for AEO/GEO content, product fit and accurate AI answers. - [How to choose prompts for an AI search strategy](/ai-search/ai-search-prompt-strategy): Choose AI search prompts around customer decisions, map questions to supporting pages, and measure retrieval, citations and recommendations separately. - [Sources cited in AI answers about developer tools](/ai-search/ai-citation-sources-developer-tools): Compare AI search citation studies without confusing total citation share with top-source share. Build a source audit for your developer-tool category. - [Why does AI recommend your competitor? A citation gap audit for SaaS teams](/ai-search/ai-citation-gap-audit): Diagnose why competitors appear in AI answers. Audit eligibility, product facts, cited sources and repeat results with a practical SaaS citation-gap worksheet. - [Where should SaaS teams invest in third-party AI citations?](/ai-search/third-party-ai-citation-strategy): Choose third-party AI citation opportunities from real buyer questions. Use a practical evidence brief for comparisons, reviews and developer communities. - [AI search attribution in GA4: connect referrals to outcomes](/ai-search/ai-search-attribution-ga4): Build a GA4 report for AI Assistant sessions, landing pages and registrations. Includes setup steps, collection checks and a worked attribution report. - [Which AI-search content should SaaS teams create first?](/ai-search/ai-search-content-priorities): Prioritize AI search content around customer decisions. Choose between references, comparisons, tutorials, research and tools with a practical SaaS workflow. - [Google AI Overviews and AI Mode: a site owner’s guide](/ai-search/google-ai-overviews-ai-mode): Learn how Google AI Overviews and AI Mode select supporting links, what makes a page eligible, and which site improvements Google recommends. - [Does Google require special AEO or GEO optimization?](/ai-search/google-aeo-geo): Google requires no special AEO or GEO setup. Check indexing, improve technical answers, and add relevant schema without mistaking it for a citation guarantee. - [How to measure Google AI Search visibility in Search Console](/ai-search/google-ai-search-search-console-report): A practical guide to Google Search Console's Generative AI performance report: its metrics, dimensions, limits, and a repeatable way to use the data. - [Query fan-out, explained for developer questions](/ai-search/query-fan-out): Google can expand one question into related searches. Learn what query fan-out means, how citation studies measure it and where the evidence is limited. - [ChatGPT Search crawler access: a publisher’s guide](/ai-search/chatgpt-search-crawler-access): Understand OpenAI’s published crawler roles and check the robots.txt, CDN, firewall, and analytics settings that affect ChatGPT Search access. - [Claude web crawlers: a site owner’s guide](/ai-search/claude-crawler-access): Learn what ClaudeBot, Claude-SearchBot, and Claude-User do, how Anthropic documents robots.txt controls, and how to check crawler access. - [AI crawler access and referral traffic for documentation](/ai-search/ai-crawler-crawl-to-referral): Measure provider-level crawl requests against referred page requests. Compare reporting methods and review crawler access rules for your documentation. - [How to make a website usable by browser agents](/ai-search/agent-ready-website): Build agent-usable forms with semantic HTML, explicit error states and stable controls. Test task completion separately from Lighthouse audits and WebMCP. - [Where developers talk about your product in 2026](/ai-search/where-developers-talk): Plan developer monitoring across GitHub, Reddit and technical forums. Compare channel data without assuming activity counts prove an audience migration. - [Replying to developers: community rules and disclosure](/ai-search/reply-to-developers): Review developer-community rules on generated content, promotion and affiliation disclosure. Use a technical reply checklist tailored to each platform. ## Optional - [Product demo video](/demo-video): A 73 second walkthrough of listening, classification, the AEO and GEO prompt universe, Ground Truth drafting, Competitor Signal, MCP, CLI, and human approval. The page embeds the video, describes each section, and links to the docs. The raw file also lives at /earshots-demo.mp4.