Skip to content

Your RAG answers.WYRLO proves it’s right.

The reliability layer that plugs into your existing RAG, measures every answer and makes it better every week.

Illustrative example, two cases: an answer backed by two sources, then missing information for which WYRLO answers “I don’t know”.

QuestionHow long do I have to get a refund+ withdrawallearned vocabulary for an online order?+ withdrawallearned vocabulary

  1. 1Vocabulary1 term added
  2. your search4 passages received
  3. 2Reranking2 of 4 kept
  4. 3Injectionsnone detected
  5. your modelanswer generated
  6. 4Verification2 of 2 supported
  7. 5Decisionanswer

5 checks passed · 2 passages kept

Passages from your RAG, reranked

« …you have 14 days to exercise your right of withdrawal… »

Terms, art. 7rank 31

« …the refund is issued no later than 14 days after your request… »

Returns FAQrank 42

2 passages kept · settings v15

2 dropped: Shipping, conditions (was 1st) · Legal warranty (was 2nd)

Your model’s answer, verified

You have 14 days to withdraw.1supported

The refund is issued within 14 days.2supported

2 of 2 sentences supported

Certain · 2 matching sources
npm install @wyrlo/sdk
import { Wyrlo } from "@wyrlo/sdk";
const wyrlo = new Wyrlo({ apiKey: process.env.WYRLO_API_KEY });
const res = await wyrlo.guard({ question, passages, generate });

Package and method names: [TO BE CONFIRMED]

A RAG in production degrades silently.

Documents change, your users’ vocabulary drifts, retrieved passages lose relevance. Nothing breaks, and no alert fires.

The worst part isn’t the error, it’s the confident error. A wrong, well-phrased answer costs more than an honest “I don’t know”.

And every fix is manual: read traces, guess the cause, tweak a setting, hope nothing breaks.

Four steps, then the loop runs on its own.

  1. Once

    1Install the library

    A few lines between your search and your answer. Your RAG, your documents and your model stay the same.

  2. On every question

    2WYRLO measures every answer

    Sources checked sentence by sentence, confidence level, decision: answer or say “I don’t know”.

  3. Every night

    3The loop adjusts the settings

    It applies a change only if the score goes up without breaking anything.

    1. Analyze failures
    2. Test
    3. Apply
    settings v14 → v15
  4. Every week

    4The report proves it

    “91% correct answers, up from 84% last week”

    Numeric example, demo data.

Five checks between your search and your answer.

  1. 1Vocabulary

    “refund” is also searched as “withdrawal”.

  2. your search
  3. 2Reranking

    Retrieved passages are reordered; only the most useful ones remain.

  4. 3Injections

    Instructions hidden in the question or the passages are blocked.

  5. your model
  6. 4Verification

    Each sentence of the answer is matched to the passage that supports it.

  7. 5Decision

    Certain, probable or uncertain: answer, or say “I don’t know”.

WYRLO checkyour components, outlined, unchangedIllustrative examples.

Every week, the proof in numbers.

Weekly report · week 38 · Sep 14–20, 2026

Demo data

91.2%correct answers

+7.1 pts compared with week 37 (84.1%)

n = 1,204 answers evaluated out of 2,318 questions analyzed

Correct answers over 8 weeks, in %

settings version applied by the loop

Correct answers per week
WeekCorrect answersVersion
S3176.4%—
S3278.0%—
S3379.5%—
S3480.1%v12
S3581.8%—
S3682.6%v13
S3784.1%v14
S3891.2%v15

Fixes applied this week (settings v15)

Fixes applied this week (settings v15)
Vocabulary+ “credit note” = “voucher”41 questions with no passage+3.9 pts
Passages kept8 → 6diluted answers+2.1 pts

3 fixes are waiting for your approval.

Most requested missing topics

  • Shipping to Switzerland23 questions
  • Enterprise pricing17 questions
  • After-sales times for overseas territories11 questions

To fix on your side

Re-split “terms.pdf” by article: some articles are cut in two, causing 9 failures this week.

WYRLO fits your stack, not the other way around.

  • TypeScriptnpm
  • Pythonpip
  • LangChainintegration
  • LlamaIndexintegration
  • REST APIany other language

Package names and minimum versions: [TO BE CONFIRMED]See integrations

Your documents stay with you.

Your RAG

your documents stay there; WYRLO never stores them

question, passages, answer

WYRLO, hosted in the EU (Paris)

masking

Masked trace30 days by defaultdeleted

Hosting
European Union, Paris (eu-west-3 region)
Documents
Never stored
Traces
Masked, kept 30 days by default (retention set by your organization)
Encryption
Yes; scope and algorithms [TO BE CONFIRMED]
Isolation
Strict between organizations
Data processing agreement
Available · Request the data processing agreement

Pricing follows the number of questions analyzed.

Free

Price
€0 per month
Availability
available
Questions analyzed per month
[TO BE CONFIRMED]
Extra credits
[TO BE CONFIRMED]
Nightly loop
[TO BE CONFIRMED]
Weekly report
[TO BE CONFIRMED]
Start for free

Pro

Price
€49 per month, proposed [TO BE CONFIRMED]
Availability
coming soon
Questions analyzed per month
[TO BE CONFIRMED]
Extra credits
[TO BE CONFIRMED]
Nightly loop
[TO BE CONFIRMED]
Weekly report
[TO BE CONFIRMED]

This plan isn’t open yet.

Team

Price
€149 per month, proposed [TO BE CONFIRMED]
Availability
coming soon
Questions analyzed per month
[TO BE CONFIRMED]
Extra credits
[TO BE CONFIRMED]
Nightly loop
[TO BE CONFIRMED]
Weekly report
[TO BE CONFIRMED]

This plan isn’t open yet.

A monthly plan, then extra credits per unit based on questions analyzed.

FAQ

Do we need to change our RAG?

No. WYRLO sits between your search and your answer. Your index, your model and your documents stay with you; you add a few lines of code.

Do you store our documents?

No. WYRLO receives the question, the passage excerpts retrieved by your RAG and the answer. These traces are masked and kept 30 days by default, a retention period your organization can adjust. Your documents are never copied to our systems.

Where is our data hosted?

In the European Union: the database and trace processing are in Paris (eu-west-3 region). The list of subprocessors is in the data processing agreement [TO BE CONFIRMED].

What happens if WYRLO is unavailable?

Your RAG keeps answering. If WYRLO doesn’t respond in time, the library lets your RAG’s answer through without analyzing it [timeout TO BE CONFIRMED]. During the incident, you lose verification, not service.

How much latency does WYRLO add to each question?

[TO BE CONFIRMED: measured p50 and p95 latency]

How does the nightly loop avoid breaking what works?

It tests each settings change before applying it and keeps only those that improve the score without making a previously passing question fail [non-regression method TO BE CONFIRMED]. You can also approve each change yourself and roll back to a previous version.

How is the correct answer rate calculated?

[TO BE CONFIRMED: evaluation method]. The report always shows its base: the number of answers evaluated out of the number of questions analyzed.

What if a failure is caused by how our documents are chunked?

WYRLO doesn’t modify your documents. It tells you the exact fix to apply, for example re-splitting a file by article, along with the affected questions.

Measure your RAG’s reliability.

A few lines of code, then your first measured answers today.