AI Rewriter API — a REST endpoint for production authenticity.

Embedded authenticity inside your product

If your CMS asks the user to leave for a separate AI rewriter site and paste output back, you have lost the workflow. The Rewrite button has to live inside your editor, calling your backend, which calls the AI rewriter endpoint. The user never sees the dependency. TextSight's REST API is what makes that integration shape possible without rebuilding the model yourself.

Pipeline automation

Programmatic SEO platforms and content factories generate batches of drafts and need every piece rewritten and detector-checked before publish. That is a script, not a sequence of browser tabs. The API is the only way to wire detect, rewrite, re-detect, publish into a single automated flow. Run it nightly, run it on demand, run it from your CI pipeline.

Multi-tenant economics

If you are reselling authenticity to your own users, you need one upstream subscription, one set of credentials, and a pricing model that does not punish growth. Per-word credit packs do exactly that: every active customer eats your margin. A flat monthly subscription with a generous word quota on Business scales more predictably as your user base grows.

cURL

curl -X POST https://api.textsight.ai/v2/rewrite \
  -H "Authorization: Bearer $TEXTSIGHT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "The draft to rewrite.",
    "tone": "conversational",
    "strength": 3
  }'

Node.js (fetch)

const res = await fetch("https://api.textsight.ai/v2/rewrite", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TEXTSIGHT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    text: draft,
    tone: "conversational",
    strength: 3,
  }),
});
const data = await res.json();
console.log(data.rewritten, data.humanization_score);

Python (requests)

import os, requests

resp = requests.post(
    "https://api.textsight.ai/v2/rewrite",
    headers={"Authorization": f"Bearer {os.environ['TEXTSIGHT_API_KEY']}"},
    json={
        "text": draft,
        "tone": "conversational",
        "strength": 3,
    },
    timeout=60,
)
data = resp.json()
print(data["rewritten"], data["humanization_score"])

Response shape

{
  "rewritten": "The rewritten, human-feeling version of the draft.",
  "humanization_score": 87,
  "ai_probability": 0.13,
  "score_reliable": true,
  "request_id": "req_01HX..."
}

An OpenAPI specification for the public endpoints is on the roadmap. Until it lands, the contract on this page and the /api-docs page is the source of truth.

CMS pre-publish hook

A pre-publish hook in your CMS calls the AI rewriter endpoint with the draft, waits on the response, and replaces the draft body with the rewritten version before the editor sees the publish-ready preview. Editors land on human-feeling prose without copy-pasting into a separate tool, and your platform looks like a single integrated workflow.

Agency batch processing

Content agencies queue client articles overnight and rewrite the batch in bulk. The script reads articles from a queue, calls the AI rewriter endpoint per article, and writes the rewrite back the next morning. The 10,000 monthly calls on Business cover most mid-sized agency volumes; loop within the per-minute rate limit (120/min on Business) to pace the overnight batch.

Content platform AI moderation

Platforms that accept user-submitted content (forums, marketplaces, knowledge bases) increasingly auto-rewrite AI-generated drafts to keep platform quality consistent. Detect first with /v2/detect to flag AI-heavy submissions, route flagged drafts through /v2/rewrite, then publish the rewrite with an audit trail.