ForHosting KIT · Text & AI

Make text sound human

Text generated by templates, translated by machine, or drafted under legal caution tends to read stiff, over-hedged and oddly repetitive, even when every fact in it is correct. The Conversational Rewrite API loosens that stiffness, adjusting rhythm, connective phrasing and word choice so the same content sounds like a person wrote it, without inventing anything that was not already there. It is a rewrite tool, not a content generator.

● StablePer request + per 1,000 words$0.003

Run — $0.003 + $0.0135/1,000 words How it works & API

Use it from WebAPIEmailApp soonTelegram soon

Run it online

Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.

The specific problem of stiff text

Stiff writing usually comes from one of three sources: it was assembled from templated fragments, it was translated too literally, or it was drafted defensively with every claim hedged and qualified until the voice disappeared. Readers notice the stiffness even when they cannot name it, and it quietly erodes trust in onboarding emails, product descriptions and support replies alike. This endpoint targets exactly that texture problem, leaving the underlying content alone.

What changes, and what does not

The rewrite varies sentence length instead of marching in uniform units, replaces mechanical connectors with natural transitions, and trims redundant hedging that no one actually speaks with. It does not add opinions, invent examples or soften factual claims into vagueness; a stiff but accurate sentence becomes a natural but equally accurate one, nothing is fabricated in the process.

How the pipeline runs

Post your text to POST /text/humanize and the task queues immediately, returning a task_id so your application never blocks on the rewrite. The engine scores the input for markers of stiffness, template residue, over-hedging, unnatural connectors, then reworks those spots specifically rather than rewriting the whole passage indiscriminately. Delivery is a signed webhook when the task completes, or a signed link that stays retrievable for 24 hours.

Why this differs from plain paraphrasing

Generic paraphrasing tools often just swap synonyms, which can make stiff text more stiff, not less, by adding unfamiliar words on top of an already awkward structure. This endpoint targets structural stiffness specifically, sentence rhythm, connective tissue, hedging density, which is what actually reads as robotic to a human, and leaves vocabulary changes as a secondary effect rather than the whole strategy.

Fits where copy meets scale

Marketing automation platforms run generated product blurbs through it before publishing, chatbot response libraries get a pass to sound less scripted, and localization pipelines use it after machine translation to smooth phrasing that is accurate but awkward. Three automatic retries absorb transient errors, failed tasks are never billed, and there is no free tier, keeping the queue clear for paying, production traffic.

What you can do with it

Post-translation polish

A localization team runs machine-translated product copy through the API to smooth phrasing that is accurate but reads awkwardly to native speakers.

Templated email warm-up

A marketing platform humanizes merge-tag-heavy email templates so the final send does not read like an obvious mail-merge.

Chatbot scripts that do not sound scripted

A conversational AI team runs canned chatbot responses through the endpoint to reduce the robotic cadence users notice after a few exchanges.

Legal-safe copy that still reads naturally

A fintech product team humanizes disclosure text that legal has hedged heavily, keeping every qualifier but softening the delivery.

FAQ

How do I make AI or template text sound human?

Send it to POST /text/humanize; the endpoint rewrites rhythm, connectors and hedging asynchronously and returns the result by webhook or signed link.

Does humanizing add false claims or made-up details?

No, it rewrites phrasing and rhythm only; it does not invent examples, opinions or facts that were not in the source text.

Is there a free trial for the humanize endpoint?

There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.

What does the humanize API cost?

$0.003 per request plus $0.0135 per 1,000 words, charged only for tasks that complete successfully.

How is this different from a paraphrasing tool?

Paraphrasing mainly swaps words; this endpoint targets sentence rhythm, connective phrasing and hedging density, the structural traits that actually read as stiff or robotic.

Can it fix text produced by machine translation?

Yes, it is commonly used after machine translation to smooth phrasing that is technically correct but unnatural in the target language.

How do I retrieve the result?

By a signed webhook call when the task finishes, or a signed link valid for 24 hours, after which the data is deleted.

What happens on a failed request?

The task retries automatically up to three times; a task that ultimately fails returns a clear error and is never charged.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/text/humanize

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/text/humanize \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"text":"…"}'

const res = await fetch("https://api.kit.forhosting.com/text/humanize", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "text": "…"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/text/humanize",
    headers={"Authorization": f"Bearer {os.environ[&#39;KIT_KEY']}"},
    json={
    "text": "…"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/text/humanize", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => &#39;{"text":"…"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"text":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/text/humanize", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "text": "…"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "text.humanize",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.003

Per 1,000 words$0.0135

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

max_tokens 20000

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.
`422`	`task_failed`	The task failed after 3 retries. You are never charged for it.

Read the full KIT documentation →