AI Humanizer API

Humanize AI-written text from your app or agent over REST or MCP. Use prepaid credits with no subscription.

5,000 trial credits with your first key (verified, non-disposable email; one trial per address). Then $0.20 per 1,000 billable words on the Starter pack, less on larger packs.

Request
# post.json: {"text": "Coordinating stand-up meetings across multiple time zones...", "mode": "casual"} (43 words)
curl https://aicheckerhumanizer.com/api/v1/humanize \
  -H "Authorization: Bearer $AICH_API_KEY" \
  -H "Content-Type: application/json" \
  -d @post.json
# 202: {"taskId": "...", "status": "queued", ...}

# Replace TASK_ID with the taskId from that response:
curl "https://aicheckerhumanizer.com/api/v1/humanize/TASK_ID" \
  -H "Authorization: Bearer $AICH_API_KEY"
Result (excerpt)
{
  "taskId": "0f92ace1-57c9-4dd1-a675-5c3967295244",
  "status": "completed",
  "output": "Running stand-up meetings across time zones is tough for our distributed team. Engineers in Berlin, Austin, and Manila have to juggle overlapping hours while staying productive—and we need a time that works for everyone without messing with work-life balance.",
  "creditsReserved": 215,
  "creditsCharged": 215,
  "creditsRemaining": 254785,
  "expiresAt": "2026-11-18T19:02:41Z"
}

What the API does

POST /humanize accepts up to 3,000 words and returns a task ID; fetch the rewrite at GET /humanize/{taskId}. On MCP, humanize_text waits up to 50 seconds; if the task is still running, pass its ID to get_humanize_result.

We rewrite eligible paragraphs, splitting long ones into chunks, and return the whole text with each rewritten chunk swapped in. Quotes, citations, URLs and numbers we recognize stay as they were; check names in the result, since some can be missed. Pick a mode (standard, academic, casual, concise) and a strength (light, medium, heavy), the same choices as on our site.

You pay only for the parts that were rewritten. Units the rewrite left unchanged, or that failed, cost nothing.

The same key and credit balance work for both APIs: detection answers in one request, and rewrites use a task ID. See the AI detector API, or try the AI humanizer in the browser before you write any code.

Quick start

  1. Sign in and create a key on your account page. It's shown once, so store it somewhere safe.
  2. Send it as a Bearer token with each request.
  3. Read the response fields in the API documentation.
Request
# post.json: {"text": "Coordinating stand-up meetings across multiple time zones...", "mode": "casual"} (43 words)
curl https://aicheckerhumanizer.com/api/v1/humanize \
  -H "Authorization: Bearer $AICH_API_KEY" \
  -H "Content-Type: application/json" \
  -d @post.json
# 202: {"taskId": "...", "status": "queued", ...}

# Replace TASK_ID with the taskId from that response:
curl "https://aicheckerhumanizer.com/api/v1/humanize/TASK_ID" \
  -H "Authorization: Bearer $AICH_API_KEY"

Use it from an AI agent

The API is also an MCP server, so Claude, Cursor and other MCP clients can call it as tools: detect_ai_text, humanize_text, get_humanize_result and get_balance. Credits and limits are the same as the REST API.

Claude Code
claude mcp add --transport http aicheckerhumanizer \
  https://aicheckerhumanizer.com/api/mcp \
  --header "Authorization: Bearer ach_live_..."
Cursor and other clients that take a URL
{
  "mcpServers": {
    "aicheckerhumanizer": {
      "url": "https://aicheckerhumanizer.com/api/mcp",
      "headers": { "Authorization": "Bearer ach_live_..." }
    }
  }
}

Pricing

Credits are prepaid and last 12 months. Detection uses 1 credit per scored word when there's a verdict. For each chunk that's rewritten (a paragraph, or part of a long one), humanizing uses 5 credits per word of the original; chunks shorter than 10 words are billed as 10. For more than $200 at a time, contact us.

API credit packs
PackPriceCreditsHumanizingDetection
Starter$10250,00050,000 words, $0.20 per 1,000250,000 words, $0.04 per 1,000
Growth$501,500,000 (+20%)300,000 words, $0.167 per 1,0001,500,000 words, $0.033 per 1,000
Scale$2006,500,000 (+30%)1,300,000 words, $0.154 per 1,0006,500,000 words, $0.031 per 1,000
Humanizing word counts assume every rewritten chunk has at least 10 words.

API credit packs: email us within 7 days of payment to ask for a full refund. The credits used and reserved from that pack must add up to 5% or less. One API refund per email address. See the full refund rules.

Limits and languages

  • Detection: up to 10,000 words per request, in English, Spanish, Portuguese and French.
  • Humanizing: up to 3,000 words and 200 chunks per request, in English, Spanish, Portuguese and French.
  • Per hour: 2,000 detections, 600 humanize requests and 20,000 result or balance checks. The response tells you how long to wait when you hit one.
  • At once: before your first credit purchase, 2 detections and 1 rewrite in progress; after it, 10 of each. Queued rewrites count.
  • Up to 5 active keys per account. Revoking a key stops it right away.

Data handling

We don't save the text you send for detection in our database. Passage fingerprints and scores are cached for 24 hours, as on our website. If you send an Idempotency-Key, we also keep the response scores and positions for 24 hours so a retry gets the same result. Humanizing results can be fetched for about 70 minutes after you submit; the text is stored encrypted and deleted at the next cleanup after that, at least 10 minutes after the task finishes. Your usage log keeps dates, word counts and credits for 90 days, never the text. The model providers we send text to have their own retention periods, listed in our privacy policy.

Frequently asked questions

Do I need a subscription?

No. Buy a credit pack once and use it within 12 months. Your first API key gets 5,000 trial credits for 30 days if your email is verified and isn't a disposable address; each address can claim the trial once. Website plans and API credits are separate, so a website subscription doesn't include API use.

Can I use the same credits for detection?

Yes. One balance covers both. Detection uses 1 credit per scored word when there's a verdict; humanizing uses 5 credits per original word of each rewritten chunk, and chunks shorter than 10 words are billed as 10.

What happens if I send the same request twice?

Without an Idempotency-Key, each submission is a new request. With one, retry within 24 hours using the same key, text and options: a completed detection replays without a second charge, one still running returns 409, and a failed one can run again. For an accepted rewrite the key returns the same task, whose text expires about 70 minutes after you submit.

Can I build it into a product I sell?

Yes. You can add it as a feature of your own app or use it on your clients' text. Don't share your key outside your organization or resell credits.

Do you keep the text I send?

We don't save detection text in our database. Humanizing results can be fetched for about 70 minutes after you submit; the encrypted text is deleted at the next cleanup after that, at least 10 minutes after the task finishes. The model providers we send text to keep it for their own retention periods, listed in our privacy policy. We don't use your text to train models.