Most platforms let content quietly become outdated. Rasepi gives every document a live score that tells readers and AI tools exactly how much they should trust it.
You know the drill. A Confluence page that was last updated 18 months ago. No way to know if it’s still accurate. You read it anyway, because what else are you supposed to do?
It’s not complicated. Every document has an expiration date. The closer it gets to expiring without being reviewed, the lower its score drops.
When you create or update a document, select an expiration period. This could be 30 days for a fast-moving runbook, 6 months for stable policy documents, or anything in between. This is not optional.
Based on when the document was last reviewed, how close it is to expiring, and whether the content has changed, Rasepi assigns a score from 0 to 100. A freshly reviewed document scores 100. A document past its expiration date? Probably closer to 20.
When a document is nearing its expiration date, the owner receives a friendly reminder. Review it and confirm that it’s still accurate, or update it. Either way, the score stays high.
If no one reviews a document in time, its score drops and a visible warning appears. Readers know immediately that this content might be outdated. No guesswork required.
Rasepi monitors more than just the calendar. These real-time signals all contribute to a document’s trust score.
AI tools are excellent at finding documents. They are terrible at knowing whether those documents are still accurate.
When a Copilot or RAG pipeline indexes your knowledge base, it treats a 2-year-old incident playbook exactly the same as one that was reviewed yesterday. That’s a problem.
Rasepi’s trust scores give AI tools a signal they’ve never had before: How up-to-date is this content? An AI that highlights a document with a score of 95 gives you something reliable. One that finds a document with a score of 15? It can warn you or skip it entirely.
This isn’t just about people reading documents. It’s about making your entire knowledge base trustworthy for the tools that increasingly depend on it.
Set different expiration periods for different content types. A rapidly changing API document might need 30 days. For company policies, 12 months might be fine.
Confirming that a document is still accurate takes just one click. You don’t have to rewrite anything. If it’s accurate, just confirm it and the timer resets.
Admins get a workspace-wide overview of freshness scores. Sort by age, filter by team, and identify documents that need attention before they cause problems.
Freshness scores are available via REST API and MCP Server. Integrate them into your own tools, dashboards, and AI pipelines, or connect directly from AI assistants like Claude or Copilot. Go to developer documentation →
Rasepi assigns a Trust Score to every document. Your team knows what’s current. AI tools know what’s current. No one wastes time on content that’s past its expiration date.
Rasepi is in private beta. We’re inviting teams in waves.