Skip to content

Integrations

Plug the verification in where your RAG lives.

Status of each integration

An integration only becomes “available” after a successful trial from a clean machine, following the documentation. No install command is given before that.

One API call, in the service that already calls your RAG.

After your retrieval and your model, send the question, the passages and the answer. WYRLO returns its decision: answer, or say “I don’t know”.

Integration methods

  • REST APIany languageavailable
  • Pythonlibraryavailable
  • TypeScriptlibraryavailable
  • LangChainPython integrationcoming soon
  • LlamaIndexPython integrationcoming soon

If WYRLO does not answer in time, your RAG still answers: you lose the check, not the service.

Read the documentation
export WYRLO_API_KEY="wyr_test_…"
curl https://api.wyrlo.io/functions/v1/guard \
  -H "Authorization: Bearer $WYRLO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "x-region: eu-west-3" \
  -d '{
    "question": "What is the return period?",
    "answer": "The return period is 14 days.",
    "passages": [{
      "id": "p1",
      "text": "Items can be returned within 14 days of delivery."
    }]
  }'

Replace wyr_test_… with a key created in your customer workspace.

Your RAG deserves a second reading.

Access to the API is opening gradually.

  • Free to get started
  • Database hosted in Paris
  • Your RAG answers even if WYRLO does not