AI Humanizer API
Humanize AI text inside your own product with a single REST call. The AI humanizer API exposes the engine that powers TextPulse to your backend: JSON goes in, rewritten prose comes back, across more than 60 languages.
Making your first request
Authenticate with an Authorization: Bearer header and post your text. The rewritten version returns as outputText alongside the metering figures for that call.
curl https://textpulse.ai/api/v1/humanize \ -H "Authorization: Bearer tp_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "text": "Our analysis indicates the intervention produced gains...", "writingMode": "Academic", "intensityScalar": 0.5 }'{ "outputText": "Our analysis points to measurable gains from the...", "metrics": { "inputWords": 128, "outputWords": 134, "wordsCharged": 128, "balanceRemaining": 99872, "modelLatencyMs": 4310, "route": "v1/humanize" }}What the AI humanizer API handles for you
Language routing, register control, metering and retry safety are part of the endpoint, so your integration stays a single function.
One route covers 60+ languages
English runs on the fine-tuned humanizer engine. Pass a language value and the request is routed to the multilingual path instead, so a non-English product page reaches the same endpoint without a second integration.
Register and strength are parameters
Five writing modes cover the Academic, Corporate, Creative, Blog/SEO and General registers. The intensityScalar value sets how different the rewrite is from the source and takes one of 0, 0.25, 0.5, 0.75 or 1, running from Mild through the Balanced default at 0.5 up to Aggressive.
One POST per document
There is no job queue to poll and no webhook to register. The humanize call holds the connection until the model returns and answers with the rewritten text, so a single request completes the work.
Retries do not charge twice
Send a requestId and the result is cached against it for about ten minutes. A repeat of the same identifier inside that window replays the stored response rather than running the model again, and any request the engine fails to complete returns its words to your balance automatically.
Endpoint reference
Authorization: Bearer header. Keys begin tp_live_ and are issued per project./api/v1/humanize/api/v1/balanceA single humanize call accepts up to 1,000 words within a 10,000 character ceiling, and each key may issue 60 requests per minute. Longer documents are sent as a sequence of calls.
AI humanizer API pricing
Credits are prepaid and drawn down by the word. Billing counts what you send rather than what the engine returns, and any call that fails to produce a rewrite is credited back to the key.
Credits are valid for 12 months from purchase, and cover every language, writing mode and English variant the endpoint supports. For sustained volume or a white-label arrangement inside your own product, request access and we will quote against your monthly figure.
AI humanizer API questions
Get your API key
Keys are issued per project. Describe what you are building and we will reply within 24 hours.