Deterministic clinical text correction API.

Send clinical text to POST /check with a response mode. Production integrations should include an API key using the Authorization header.

curl -X POST "https://rerande.nextnlp.com/check" \
  -H "Authorization: Bearer $RERANDE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "text": "The patient developed tachycarda and chest discomfrt.",
    "mode": "text",
    "language": "en",
    "options": {
      "include_original": true,
      "include_billing": true
    }
  }'

Use bearer-token authentication for production API access. Keep keys server-side and never expose them in browser JavaScript, mobile binaries, client logs, or public repositories.

export RERANDE_API_KEY="rerande_live_xxxxxxxxxxxxx"

curl -X POST "https://rerande.nextnlp.com/check" \
  -H "Authorization: Bearer $RERANDE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Patient admited with dyspniya.","mode":"elite"}'

The endpoint accepts a JSON body and returns a JSON response shaped by the selected mode. ReRanDE does not diagnose, recommend treatment, or generate new clinical meaning.

Use the smallest response contract that gives your workflow enough evidence. Start with text or elite; move to full, audit, or debug when traceability or diagnostics are required.

Python with API authentication

import os
import requests

url = "https://rerande.nextnlp.com/check"
headers = {
    "Authorization": f"Bearer {os.environ['RERANDE_API_KEY']}",
    "Content-Type": "application/json",
    "Accept": "application/json",
}
payload = {
    "text": "The patient developed tachycarda and chest discomfrt.",
    "mode": "text",
    "language": "en",
    "options": {"include_original": True, "include_billing": True},
}

response = requests.post(url, headers=headers, json=payload, timeout=30)
response.raise_for_status()
data = response.json()
print(data["corrected_text"])
print(data["corrections"])

Node.js server-side fetch

const response = await fetch("https://rerande.nextnlp.com/check", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.RERANDE_API_KEY}`,
    "Content-Type": "application/json",
    "Accept": "application/json"
  },
  body: JSON.stringify({
    text: "Initial electrocardiogrm showed ST elevaton.",
    mode: "elite",
    language: "en",
    options: { include_original: true, include_billing: true }
  })
});

if (!response.ok) {
  throw new Error(`ReRanDE request failed: ${response.status}`);
}

const data = await response.json();
console.log(data.domain, data.summary);

Domain-only routing

curl -X POST "https://rerande.nextnlp.com/check" \
  -H "Authorization: Bearer $RERANDE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Clinical features include wheezing, bronchospasm, and inhaler response.",
    "mode": "domain",
    "options": {"top_k_domains": 3}
  }'

text response

{
  "mode": "text",
  "request_id": "67a441b9-95fe-41ff-b0e2-f585f36c8f15",
  "original_text": "The patient developed tachycarda and chest discomfrt.",
  "corrected_text": "The patient developed tachycardia and chest discomfort.",
  "corrections": {
    "tachycarda": "tachycardia",
    "discomfrt": "discomfort"
  },
  "billing": {
    "unit": "SmartCredit",
    "credits_used": 57
  }
}

audit response

{
  "mode": "audit",
  "request_id": "req_...",
  "engine": {
    "version": "gold-v...",
    "lexicon_version": "pkl-live",
    "timestamp": "2026-06-29T..."
  },
  "domain": "CARDIOLOGY",
  "text": {
    "original_hash": "sha256:...",
    "corrected_text": "The patient developed tachycardia."
  },
  "corrections": [
    {"original": "tachycarda", "corrected": "tachycardia", "confidence": 0.96}
  ],
  "performance": {"execution_time_ms": 18},
  "billing": {"unit": "SmartCredit", "credits_used": 241}
}

ReRanDE uses SmartCredits to meter API usage. Input-only contracts are priced by submitted characters. Explainability-heavy contracts include response size because they return additional structured metadata.

HIPAA-regulated organizations should use ReRanDE only under an appropriate enterprise agreement and deployment model.

• Use server-side calls for authenticated production traffic.
• Choose the smallest response mode that satisfies the workflow.
• Use request_id for support and operational tracing.
• Use timeout and retry logic with exponential backoff for 5xx responses.
• Do not send PHI unless your organization has the required agreement and deployment model.

For production access, enterprise deployment review, or private rollout planning, contact the ReRanDE team.