EarShots.dev
Open navigation

Ground Truth

Every claim about your product, checked against your docs.

Ground Truth collects claims about your product from AI answer engines, tutorials, comparison articles, and round-ups, and checks each claim against your documentation. It shows docs and developer relations teams which claims are wrong, which are stale, and which docs page would fix them.

Read the docs

Article being checked

"Five ways to wire an LLM gateway into a Node service"

3 claims found, 1 not supported

  • The SDK supports streaming out of the box.

    Supported

    source: docs/quickstart.mdx: streaming responses

  • Self hosting requires a enterprise license.

    Not supported

    source: docs/self-hosting.mdx: free tier limits

  • Rate limits are 100 requests a minute.

    Partly supported

    source: docs/limits.mdx: per-plan table

Draft correction note

One detail needs a fix: self hosting does not require an enterprise license. The free tier covers it, with the limits listed here.

Copy noteNothing is sent for you
Ground Truth checks each claim in a public article against your connected documentation, then prepares a correction note for human review.

What you see

Every claim, sourced and checked.

Claims by source

Perplexity, ChatGPT, Google AI Overviews, blogs, and agent-authored pages, listed separately.

Verdict and correction

Accurate, stale, or wrong, with the docs passage that contradicts the claim and a suggested correction.

How it works

How a claim is checked.

EarShots extracts the claim as a single sentence, searches your sources for the matching fact, and grades the gap. Claims from muted round-ups and directories feed in automatically. Corrections are drafts for your docs team, not posts.

A person approves every correction. EarShots never edits your docs.

FAQ

Common questions

Which AI engines are checked?

Perplexity, ChatGPT, and Google AI Overviews, alongside blogs, tutorials, and agent-authored pages.

How often are claims rechecked?

Each sync re-reads connected sources, so a claim's verdict updates as your documentation changes.

Can EarShots fix my docs?

No. It drafts a correction pointing at the passage that is wrong. Your docs team commits the change.

What counts as a stale claim?

A claim that was true and now conflicts with a newer documentation passage, such as an old rate limit or a renamed feature.

Check what AI answers say about your product

Connect your documentation and see every claim checked against it.