Rule Studio is a paid workspace add-on. It builds on Your policy documents:
first parse and structure a PDF, then extract structured rules from its sections. Free
workspaces get
402 upgrade_required on every Rule Studio endpoint.What it does
The document lane turns a payer PDF into a folder tree of cited prose. Rule Studio takes the next step: it sends each section’s prose to an extraction pass and produces structured rule candidates — landing asdraft for staff review. Nothing is trusted until a reviewer
approves it, and only approved payment algorithms can be run.
Every candidate carries two orthogonal dimensions:
kind— the structural shape:rule,decision_table, oralgorithm.rule_type— the semantic category:coding_edit,billing_edit,post_adjudication(denials & appeals, recoupment, adjustments),reimbursement(payment math),medical_necessity,authorization,timely_filing(initial filing deadlines only),clinical_documentation,charge,benefits,edi_formatting,general.
kind=algorithm,
rule_type=reimbursement.
Prerequisites
POST /v1/policy/parse— parse the PDF into chunks.POST /v1/policy/structure— build the folder tree (Rule Studio will build it on demand if missing).- A workspace on a paid plan (Pro or Enterprise).
Endpoints
API-key callers are scoped to their own tenant’s documents. Review is staff-only.
The lock
A FREE-tier workspace receives:402. Front-ends render the “Turn documents into rules” button locked when the
workspace plan is FREE, and fall back to this response if the plan changes mid-session.
Review workflow
Candidates landstatus="draft" with extracted_by="llm:<model>", a confidence, and
citations back to source page ranges. A reviewer approves, edits, or rejects each one; the
review status survives re-extraction (re-running extract refreshes draft rows but never
overwrites an approved or rejected decision). Only approved algorithms can be evaluated or
self-tested via the API.