Natural writing, on purpose
Improve flow, sentence rhythm and word choice. Choose a natural, conversational or professional tone for the context your users work in.
UltraHumanizer / Developer platform
API v1 · Prepaid accessBring UltraHumanizer’s editorial capabilities to your product. Shape the voice, protect the details, and give your users writing they can review.
Create a key, add credits, and make your first request. No subscription required.
{
"request_id": "req_example",
"text": "You can use Acme for $20 per month.",
"usage": {
"billing_unit_version": "2026-10-v1",
"input_units": 8,
"charged_units": 8
},
"detail_changes": [],
"warnings": [],
"engine_version": "uh-editorial-2026-10"
}The editorial layer
The API brings together the rewriting and review capabilities behind UltraHumanizer in a released interface for developers.
Improve flow, sentence rhythm and word choice. Choose a natural, conversational or professional tone for the context your users work in.
Guide length, reading style and rewrite strength. Keep brand names and specialist terms in focus with explicit protected terms.
Pair revised text with structured change warnings for numbers, dates, links, quotations and citation markers. Route changes to a human reviewer.
Use a dedicated slop-removal task for generic introductions, stock phrases, inflated wording and repetitive transitions.
Build workflows around the original language. Evaluate representative samples for your audience before enabling automatic publication.
Plan around JSON requests, explicit controls, usage metadata and consistent errors. Explore the released interface in our API documentation.
From draft to decision
A polished sentence still needs to say the right thing. Use the returned detail changes to decide whether a draft moves forward or needs an editor.
Explore the review response →Built around your use case
Add rewriting and review signals before content reaches your CMS. Keep the source alongside the revision for approval.
CMS workflow →Give customers a focused editing action inside the interface they already use. Keep your own product experience and publishing rules.
Application workflow →Plan an HTTP step in n8n, Make or a custom service. Use explicit usage and warning fields to guide the next action.
Automation workflow →Integration patterns are illustrative. Native connectors and SDKs are not currently available.
Prepaid pricing
Our API uses prepaid input credits, separate from website memberships. No automatic renewal or surprise overage charges .
Explore a focused integration.
Plan a recurring content workflow.
Prepare for a larger publishing pipeline.
Buy credits in the developer dashboard. Credits do not expire while the service remains available. No automatic top-up. Read the billing rules.
Before you integrate
Yes. Sign in to the developer dashboard, create a server-side API key and add prepaid credits. The documentation includes live endpoints and working request examples.
No. API access and credits are a separate product. A website membership does not currently include developer API calls.
Yes. Use the UltraHumanizer web editor to evaluate the current rewriting experience with your own samples. Website limits and sign-in requirements apply.
No. The review fields identify supported text changes. They do not prove factual accuracy, authorship or a detector outcome. Keep a human review step for important content.
Tell us your expected monthly input, peak concurrency, languages and data-handling needs. Capacity, retention terms and any service commitment need to be agreed before a production integration.
Let’s build the right integration
Share your product, languages and expected monthly volume. We’ll use that context to discuss access and the requirements for your workflow.
Need a custom integration? Write to support@ultrahumanizer.ai.