Reference documentation
for teams that write.

A knowledge base built around permanent references, version history, and typographic clarity. Every document gets a unique identifier that never changes. Every edit is tracked with full attribution. Every word is rendered with care. RFRNT (pronounced "referent") is for teams who understand that good documentation is a competitive advantage.

How it works

Permanent references

Every document receives a unique identifier like DOC-1 or SPEC-42. These references never change, even if the document is renamed or moved. Link to any document unambiguously in emails, tickets, or other systems. Prefixes are centrally configurable, so you can organize by department, project, or document type without ballooning complexity.

Quick shortcodes

Inspired by Wikipedia, important documents can be assigned memorable shortcodes like DOC:API or SPEC:AUTH for instant access. These are canonical names for your most-referenced pages. Shortcodes are unique across your entire knowledge base and resolve instantly.

Full version history

Every edit is preserved with author attribution and change summaries. Compare any two versions side-by-side and see additions, deletions, and modifications highlighted clearly. See exactly what changed, when it changed, and why. Restore previous versions with a single click. Nothing is ever lost—your documentation has a complete audit trail.

Review workflows

Propose changes that require approval before merging into the canonical version. Document owners and administrators can review, comment on, and approve or reject proposed edits. Maintain document integrity with clear ownership and editorial oversight for your most important reference materials.

AI-ready

RFRNT includes an MCP server, allowing AI agents to read and update your documentation. Keep your knowledge base current with assistance from tools like Claude.

Two document modes

Technical documentation and reference materials are visually distinct. You know what you're reading at a glance—no guesswork, no confusion. Both feature sidenotes, backlinks, and a reading experience designed for comprehension.

Technical

Authentication

All API requests require a bearer token in the Authorization header.

1
2
3

curl -X POST https://api.example.com/v1/docs \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"content": "# New Document"}'

Parameters:

content — Markdown string (required)
prefix — Document prefix (optional)

Reference

1.2 Document Approval Process

All substantive changes to policy documents must be reviewed by the document owner prior to publication. Minor corrections—typographical errors, formatting adjustments—may be approved by any editor with write access.

"The goal of documentation is not merely to record, but to clarify."

Reference documentationfor teams that write.