Live · api.qear.ai

Know when your AI is grounded in real sources — or just guessing.

QEAR verifies each claim against the actual source text and returns the exact citation — or honestly abstains when nothing supports it. It never makes up a verdict. Live today for GDPR: paste a legal statement, get each sentence checked against the regulation with the article cited.

Checked against the law.
Cited, or honestly abstained.

QEAR retrieves the actual regulation, verifies each claim against it, and cites the exact provision. When a claim isn't supported by any source, it says so — instead of inventing a verdict.

That honest abstention is the whole point: it's what makes the "supported" answers trustworthy. Live today for GDPR, with more jurisdictions on the way.

POST api.qear.ai/v1/verify
# Check a GDPR claim against the regulation
curl https://api.qear.ai/v1/verify_legal \
  -H "Authorization: Bearer qe_..." \
  -d '{
    "jurisdiction": "EU",
    "answer": "Once consent is given under the
      GDPR, it can never be withdrawn."
  }'
Response — the diagnosis
{
  "verdict": "refuted",
  "claim": "consent can never be withdrawn",
  "citation": "GDPR Art. 7(3)",
  "reasoning": "The regulation grants the
    right to withdraw consent at any time —
    directly contradicting the claim.",
  "url": "https://gdpr-info.eu/art-7-gdpr/"
}

Beyond legal: uncertainty diagnosis for any answer.

For questions outside a grounded corpus, QEAR offers an experimental open-domain check that classifies how an answer is uncertain — returning one of five diagnostic classes and a recommended action. It verifies against a generated reference rather than authoritative source text, so it’s a triage signal, not a citation. For anything you need to stand behind, use grounded verification above.

01none

All candidates agreed

High confidence in the consensus answer. Trust the result and ship it.

02surface_variation

Same fact, different phrasing

Candidates split on wording but agree on substance. Normalization resolved it; trust the result.

03factual_disagreement

Candidates contradict each other

Different dates, names, or values for the same fact. Do not trust — verify externally or escalate to human review.

04knowledge_gap

The model honestly doesn't know

Most candidates refused to answer or said the question is unanswerable. Trust the refusal.

05degenerate_default

The model is hedging, not answering

Candidates returned defaults (0, N/A, none). The model is producing convention rather than knowledge.

Built for factual AI outputs. Honest about the rest.

QEAR is built for
  • Legal / GDPR answers — verify claims against the actual regulation and return the exact provision (live today)
  • RAG outputs — verify answers from retrieval-augmented systems are grounded, not fabricated
  • LLM Q&A in production — chatbots, support agents, knowledge bases
  • AI-generated customer replies — flag low-confidence responses before they reach users
  • Agentic systems — catch uncertain decisions before they compound across steps
  • Short factual answers — works best on focused, single-claim outputs (1–3 sentences)
Not built for (yet)
  • Code correctness — use AST analysis or execution-based testing instead
  • Long-form documents — multi-claim essays need claim-level decomposition (on our roadmap)
  • Mathematical proofs — use symbolic verification tools
  • Image / video / audio — different problem, different tools
  • Real-time streaming — verification adds latency; best for async or pre-send checks

We'd rather tell you the truth than sell you a tool that fails on your use case. Code verification is on our roadmap — join the waitlist.

Confidence scoring is a commodity. Diagnosis is a category.

Feature QEAR Competitor APIs Native logprobs
Numeric confidence score Yes Yes Token-level
Uncertainty classification 5 classes No No
Human-readable diagnosis Yes No No
Grounded legal citation Yes No No
Recommended action per response Yes No No
Adaptive compute routing Yes No No
Model agnostic Groq + OpenAI + Anthropic Varies Proprietary
Peer-reviewed methodology Nature 2024 Proprietary Standard

Not a wrapper.
A method.

QEAR extends the semantic entropy methodology from Farquhar et al. (Nature, 2024) with three original engineering contributions, validated across three model scales:

  • Entropy-gated adaptive compute allocationUncertain queries automatically escalate to more samples or a stronger model.
  • Three-tier NLI cascadeMost comparisons resolve via deterministic string normalization before any model fires.
  • Quality-aware candidate selectionReturns the best representative of the majority cluster, not just any.
Accuracy
86.8%
vs 81.2% baseline (p < 0.005)
GDPR benchmark
0 false-pass
Adversarial legal-claim set
Validated AUC
0.83
325-question benchmark at 32B
Classes
5
Each with a recommended action

Free to start. Honest pricing.

Start free with 1,000 verification claims a month. Pay only when you need more. No surprise fees. No "contact sales" for tiers under enterprise.

Free

$0/mo
  • 1,000 verification claims / month
  • 200 generations / month
  • Groq gpt-oss-120b
  • Full diagnostic output
Start free

Indie

$19/mo
  • 8,000 verification claims / month
  • 1,000 generations / month
  • Groq gpt-oss-120b
  • Email support
Choose Indie

Scale

$299/mo
  • 130,000 verification claims / month
  • 17,500 generations / month
  • Custom NLI endpoints
  • SLA + dedicated support
Choose Scale

Write five lines of code. Or write none.

For developers

The API

Add QEAR to your AI pipeline with a single HTTP call. Works in any language — Python, Node, Go, Ruby, anything that speaks HTTP.

# Add 5 lines to your existing app
r = requests.post(
  "https://api.qear.ai/v1/verify",
  headers={"Authorization": f"Bearer {KEY}"},
  json={"prompt": q, "answer": ai_answer}
).json()
# → r["uncertainty_class"], r["diagnosis"]
Get API key
For everyone else

Try it in the playground

Not a developer? Paste your question and the AI's answer into the playground and get the same diagnosis instantly. No code, no integration. Perfect for double-checking ChatGPT or Claude on important work.

Question: When was the GDPR enacted?
AI's answer: 2018
⚠ verify factual_disagreement — candidates split between 2016 (adopted) and 2018 (enforced)
Open the playground

Two ways to start. Both free.

Sign up for an API key in 30 seconds. Or try QEAR in your browser with no signup at all. Either way — see the diagnosis in action.

1,000 free verification claims / month No credit card Magic-link signup, no password