TOOL PROFILE · humaniser.com

Humaniser

The Standard rewrite kept most of the library report, but weakened the productivity wording and dropped the reason for testing in winter. The advertised API remains a developer preview.

Website screenshot

Humaniser page captured during research

Original and rewritten result

Standard / guest / English. Same benchmark; first complete output. Open any screenshot to inspect the original capture.

Humaniser input captured during the shared benchmark
The unchanged 93-word input.
Humaniser result captured during the shared benchmark
The first complete captured output. Vendor detector labels are not our editorial score.

Original · 93 words

A local library tested a four-day schedule for six weeks. It kept the same 40 weekly opening hours, closing Wednesdays and extending Monday and Thursday evenings. Visits rose from 1,200 to 1,320 a week, although Wednesday visitors had to change plans. Staff reported fewer interruptions, but productivity was not measured. Longer evenings may help people who work during the day; this does not prove every library should open fewer days. Before making the change permanent, the team will survey residents, compare costs and repeat the trial in winter, when travel habits may differ.

First rewrite

For a period of six weeks a local library trialled a four-day schedule. The same 40 weekly opening hours were kept, with a closure of Wednesdays and extension on Mondays and Thursdays evening. Visits rose to 1,320 from 1200 a week with Wednesday visitors forced to alter plans. Staff wrote there were fewer interruptions although this was never measured against productivity. Extended evening hours might be beneficial for daytime workers, but this does not imply that every library should reduce their daily operations. The team will conduct a survey of residents, look into costs and repeat the trial in winter before making it permanent.

Parameters and feature comparison

Observed features refer to the tested plan. “Not verified” is different from “not supported.”

ParameterHumaniser
Free accessThree daily humanizations, 200 words per input, English Standard, no signup.
Account requiredNo, for this completed guest run.
One-click rewriteYes, the complete sample produced a full output.
Word highlightingNo word-by-word change display verified in this workflow.
Line / sentence highlightingNo separate line or sentence change diff verified.
Selective rewritingNot verified in the tested workflow.
API / MCP / Agent SkillsDeveloper API is explicitly a preview/waitlist, not a verified publicly available service. MCP and skills not verified.
Paid plansAnnual view: Basic $60/year, shown as $5/month, 15 daily uses and 500 words/input; Pro $120/year, 50/day and 1,000/input; Max $240/year advertises unlimited. Monthly checkout not verified.
Billing unitDaily runs and per-input words; quoted paid prices are annual charges.

Score breakdown

DimensionWeightScoreWhat we found
Meaning & facts30%8/10Kept most facts, but changed the productivity caveat and omitted seasonal-travel uncertainty.
Readability25%6/10Monday and Thursday evening phrasing and some constructions need grammatical cleanup.
Natural voice15%6/10Understandable prose with a few formal or unnatural substitutions.
Editing experience15%5/10Complete rewrite in one editor; no word diff or selective sentence replacement verified.
Access & value10%8/10Free three runs per day at 200 words per input; paid daily-run and input limits are disclosed.
Integrations5%0/10Official API page explicitly says developer preview and not publicly available; waitlist does not earn an API availability score.

Overall 6.4/10 · weighted editorial judgment of the shown workflow. Read the method.

THE FULL REVIEW

Humaniser review: a workable free draft with a few loose phrases

The Standard rewrite kept most of the library report, but weakened the productivity wording and dropped the reason for testing in winter. The advertised API remains a developer preview.

Read the analysis and recommendation

Sources and limits

One short English sample and the first captured output in the stated mode. Paid models, long documents, external detectors and live integrations were not tested. Pricing is a dated snapshot; documentation is not an end-to-end integration test.