RefLens compares your developer documentation against best-in-class references — Stripe, Twilio, Adyen — and identifies exactly where a human developer or AI agent would misunderstand your system and build the wrong thing.
Most doc tools measure completeness. RefLens measures correctness.
Paste your API documentation URL and OpenAPI spec. Or upload your spec file directly. RefLens accepts any REST API documentation format.
Choose a reference API to compare against — Stripe (payments), Twilio (onboarding), Adyen (complex flows), Voucherify (loyalty), or a custom competitor. RefLens maps your domain concepts to the reference model.
RefLens scores your docs across orientation clarity, conceptual model coherence, first-call path, error recovery guidance, and AI-agent readiness. Each finding includes evidence, comparison to the benchmark, impact, and a prioritised fix recommendation.
Composite score across 11 dimensions. Know at a glance where your documentation stands against best-in-class.
Explicit assessment of whether a zero-knowledge AI coding agent can integrate without hallucinating. This is the score Stripe's docs pass. Yours probably don't.
The core output. RefLens identifies specific integration paths that will fail because your docs implied the wrong mental model — and shows exactly what needs to change.
Prioritised list of documentation fixes, OpenAPI improvements, and example additions — each with expected impact, effort, and risk if ignored.
Simulated first-call paths for both a human developer and an AI coding agent — where they get stuck, what they misunderstand, where they succeed.
Side-by-side view of your docs against the chosen benchmark — concept coverage, example quality, error handling, and naming consistency.
RefLens evaluates your docs against these reference implementations — chosen because they define the standard in their respective domains.
Your docs are tested against whichever reference matches your domain. Or all five — if you want to know where you stand across the board.
Paste your documentation URL, pick a benchmark, and optionally add an OpenAPI spec. RefLens does the rest.
RefLens catches it before they start. Run your first audit and find out what's costing you integrations.