> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wibbleai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How humanization works

> What the Wibble humanizer does, how to get the best results, and how to use it responsibly.

Humanization rewrites text so it reads as natural and human while preserving the original meaning and intent. You send a draft, and Wibble returns a version that flows better and sounds less robotic. The API runs the same humanizer as the Wibble dashboard, exposed programmatically.

People bring drafts from tools like ChatGPT, Claude, and Gemini, or from their own pipelines, and use Wibble to make the writing more natural and readable. The rewrite stays faithful to what you wrote: it changes how the text reads, not what it says.

For a running example, the input `The mitochondria is the powerhouse of the cell.` returns `Mitochondria are the cell's powerhouses.` — the meaning holds, the phrasing reads more naturally.

## What to expect

The humanizer returns a rewrite of your input, not a copy with light edits. Expect changes to sentence structure, word choice, and rhythm. It does not add facts, fabricate citations, or change your argument. Output length is close to the input but will not match it exactly.

Treat the result as a strong draft to review, not a finished document. Read it against your own voice and the requirements of where the text will be used, and edit anything that does not fit.

## Get the best results

The quality of the rewrite depends on the quality of the input.

* **Send clear, well-structured text.** Complete sentences and a logical order give the humanizer more to work with than fragments or notes.
* **Prefer shorter paragraphs.** Focused paragraphs refine more reliably than long, multi-topic blocks. Split dense sections before submitting.
* **Review the output.** Compare it to your intended voice and adjust wording where needed. The humanizer makes the text read naturally; matching your style is a quick pass after.
* **Stay within the limits.** A request accepts 1–50,000 characters, up to 2,000 words. Split longer documents into separate requests.

## Request options

Two fields on `POST /humanize` control language behavior. Both have defaults that work for most requests.

<ParamField body="auto_detect_language" type="boolean" default="true">
  Detects the input language automatically. Leave this on unless you have a specific reason to turn it off. The detected language is reported on polling responses as `detected_language`.
</ParamField>

<ParamField body="use_british_spellings" type="boolean" default="false">
  Prefers British (en-GB) spellings in the output, such as `colour` and `organise`. Set this to `true` when you want UK English; leave it off for US English.
</ParamField>

| Option                  | Default | When to set it                                                                             |
| ----------------------- | ------- | ------------------------------------------------------------------------------------------ |
| `auto_detect_language`  | `true`  | Keep the default. Turn off only if you know the input language and want to skip detection. |
| `use_british_spellings` | `false` | Set `true` for UK English output. Leave off for US English.                                |

```bash UK English request theme={null}
curl https://www.wibbleai.com/api/v1/humanize \
  -H "Authorization: Bearer wib_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "text": "The mitochondria is the powerhouse of the cell.",
    "use_british_spellings": true
  }'
```

See [Submit a job](/api-reference/humanize/submit) for every request option, including `webhook_url` and the `Idempotency-Key` header.

## Supported languages

The humanizer supports English today, in both US and UK variants. Use `use_british_spellings` to choose between them. More languages are being explored.

<Note>
  With `auto_detect_language` on, the input language is reported as `detected_language` on `POST` and `GET` job responses. Submit English text for now.
</Note>

## Use cases

<Columns cols={2}>
  <Card title="Academic and research" icon="graduation-cap">
    Refine drafts for clarity and flow, following your institution's AI policies.
  </Card>

  <Card title="SEO and marketing" icon="megaphone">
    Make campaign copy, landing pages, and briefs read naturally.
  </Card>

  <Card title="Professional writing" icon="briefcase">
    Polish resumes, cover letters, emails, reports, and proposals.
  </Card>

  <Card title="Writers and editors" icon="pen-nib">
    Tighten posts, scripts, and long-form content for readability.
  </Card>
</Columns>

## Responsible use

<Warning>
  Humanization is an editing aid. Use it to improve writing you are responsible for, and keep these points in mind:

  * **Follow the rules that apply to you.** Honor your institution's or workplace's AI policies before using the output.
  * **Disclose AI assistance when applicable.** Cite or acknowledge AI help where your context requires it.
  * **Review before you use it.** Read the output and confirm it is accurate and reflects your intent.
  * **Built to pass, not guaranteed.** Wibble humanizes AI text into natural, human-sounding writing designed to pass AI detectors while preserving your meaning. No tool can guarantee outcomes with every third-party AI-detection system, so verify anything that matters in the detector that will be used — and you stay responsible for how you use the output.
</Warning>

## Next steps

<Columns cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Go from an API key to your first humanized result.
  </Card>

  <Card title="Submit a job" icon="paper-plane" href="/api-reference/humanize/submit">
    Every request option for `POST /humanize`.
  </Card>
</Columns>