Docs
Ground Truth
Articles are not conversations. Instead of drafting a reply, EarShots pulls out every claim the article makes about your product and checks each one against your documentation.
When it runs
Posts from GitHub, X and LinkedIn keep the normal reply flow. Anything found on the open web, such as a blog post, tutorial, comparison or newsletter, opens with an accuracy check instead of a reply box.
How a check works
- 1
Open the article
EarShots reads the full article text, not the snippet stored in your queue. - 2
Pull your documentation
Matching passages come from the documentation connected to the workspace, the same source drafts use. - 3
Check each claim
Every statement about your product is marked as matching your docs, out of date, wrong, or not covered, with the quote from the article shown next to it. - 4
Send a correction yourself
When something needs fixing you get a short note for the author. You copy it and send it from your own account.
Evidence or nothing
A claim is only called wrong or out of date when a documentation passage says so, and that passage is linked next to the claim. Anything the docs do not cover is marked as not covered and left for a person to judge. EarShots will not invent a fact to win an argument.
If no documentation is connected, the check returns without a verdict. Add your docs first under Sources.