Before your AI writes a response, Rasepi checks every source it finds. Is it up to date? Verified? Approved for this purpose? Only what passes muster makes it through.
It happens in every company that relies on an AI assistant for its own knowledge. A customer asks the support bot about API setup. The search finds twelve relevant documents. Three of them are outdated. One was never intended for customers. The AI cannot tell the difference. It constructs a fluid, convincing answer from everything.
Relevant is not the same as reliable. This is exactly where the Trust Gate comes in.
You don’t change anything about your AI. Just a single verification step before the answer is generated. Rasepi doesn’t read any prompts and doesn’t sit between you and your model.
A person, a chatbot, or an agent needs information. Your AI searches as usual and finds, say, 20 sources.
Timeliness, verification status, ownership, origin, approvals, and the context of the request: Who is asking, why, and through which channel? This results in a decision for each source: ALLOW, WARN, BLOCK, or ESCALATE. Always with a justification.
Blocked sources never receive the response. Warnings may trigger citation requirements or notifications. The response is based on knowledge you can trust.
Which sources were verified, which were approved, which were blocked, and why. The provenance ledger records it all, for audits and troubleshooting.
For the technology behind it: The Trust Gate can be integrated at three points in your pipeline.
Your application first asks: Which sources are even permitted for this use case? Strict, good for regulated environments.
The retriever finds candidates, Rasepi filters them. The easiest way to get started and our recommendation. A single API call in your existing pipeline.
Rasepi checks whether the cited sources were permissible. Useful as a second line of defense, weaker than the gating step before it.
Trust is not a property of a document. It is a decision made in context: Who is asking, for what purpose, and through which channel? A score alone cannot do that.
The Trust Gate does not require migration. Rasepi connects to the systems where your knowledge resides today, catalogs the content, and calculates trust based on it. It doesn’t matter which systems they are.
Which sources were reviewed? Which were approved, which were blocked, and why? Which version was valid at the time of the response? The Provenance Ledger answers the question that arises after every incident and in every audit.
Blocked sources automatically trigger review requests to the owners. The Gate not only prevents damage, it drives the maintenance of your knowledge.
The Trust Gate uses a simple HTTP API: sources in, decisions out. Machine authentication via API key or client credentials. Works with any RAG framework, any chatbot platform, and in CI/CD pipelines. All endpoints, request examples, and SDKs can be found in the API documentation.
Trust Gate is part of the private beta. Sign up and tell us about your pipeline.
We invite teams in waves.