If your content pipeline produces AI-generated drafts and something downstream — a detector, a reviewer, a publishing checklist — keeps flagging them as AI, the fix usually isn't another manual copy-paste step. It's a single HTTP call. This is the integration pattern for wiring an AI humanizer API into n8n, Zapier, and an MCP-capable agent, with the exact request shapes so you can copy-paste and run them.
Originally published on the as the reference endpoint: a single POST /api/v1/humanizations/sync call for anything under ~2,000 words, an async endpoint with webhook callbacks for longer content, and the exact node/action configuration for n8n, Zapier, and an MCP tool.
What is an AI humanizer API?
An AI humanizer API is an HTTP endpoint that accepts AI-generated text as input and returns a rewritten version designed to bypass AI-detection tools like GPTZero, Turnitin AI, Originality.ai, and Copyleaks. Under the hood it runs a purpose-built model — usually a fine-tuned open-weight LLM such as Mistral 7B or Llama — trained on paired data of AI-written and human-written text. The endpoint's job is one thing: change surface patterns (sentence rhythm, connective tissue, punctuation, entropy signatures) enough that the detector's classifier drops below its "AI-written" threshold, while preserving meaning.
Two things it is not:
It is not a general-purpose LLM. ChatGPT and Claude can be prompted to "rewrite this to sound more human," but they weren't trained against detector signals, so results are inconsistent from call to call.
It is not magic. The best humanizer APIs bypass most detectors most of the time, but no provider hits 100%, and detectors update.
The canonical REST pattern — one endpoint, one JSON body
Every humanizer API in the category follows one of two request shapes: sync (send text, wait, get result) or async (send text, get job ID, receive result later). This guide uses .
Integrating with Zapier — Webhooks by Zapier
Zap configuration:
- Add a trigger — RSS, Google Sheets, Airtable, or an AI generation step.
- Add a Webhooks by Zapier → POST action.
- URL:
https://tohuman.io/api/v1/humanizations/sync
- Payload Type:
json
- Header:
Authorization=Bearer YOUR_API_KEY
- Data fields:
content(mapped from the previous step),intensity(medium/heavy/subtle/minimal)
Full pattern including CMS-publish step: .
Which pattern — sync, async, or MCP?
User-facing request path? → sync.
Content routinely over ~2,000 words? → async + webhooks.
Caller is an agent making its own decisions? → expose as an MCP tool.
Free tier vs paid
ToHuman: free forever, no monthly word quota, no card. Soft ~30 req/sec rate limit.
Undetectable.ai: 250-word trial, then $9.99/mo for 10,000 words.
WriteHuman: no free tier. Cheapest paid: $29/mo for 125,000 words.
Humbot: 250-word trial, then $30/mo for 50,000 words. Best for non-English (50+ languages).
StealthGPT: pay-as-you-go from first request, $0.20/1,000 words. Highest published throughput (3,500 req/min).
Walter Writes: no public API — waitlist only.
Full six-provider breakdown:
SOCIAL SHARE CARD GENERATOR