Humanization order

A humanization order is one private human-written rewrite commissioned through RentAHuman. It is a different path from machine rewriting: it needs only RentAHuman credentials and never calls Brama or a detector.

Create shape

rentahuman create sends source text plus:

• transformation: paraphrase, tone, clarity, shorten, expand, or general_rewrite;
• optional instructions;
• turnaround minutes, price cents, and USD or EUR;
• optional applicant screening sample, percentage, word limit, and instructions;
• optional paired language and minimum proficiency;
• optional resume requirement.

An 8–128 byte --idempotency-key is required and sent as Idempotency-Key. Repeating the same logical create operation can therefore be retried without deliberately creating a second order.

Lifecycle

1. Read input from a file or stdin.
2. Validate all local bounds and paired options before sending anything.
3. POST v1/humanizations using X-API-Key and the idempotency header.
4. Print Skryba's envelope containing convenience fields and the API's complete JSON under response.
5. Later, rentahuman get <id> validates the id and GETs the one owned humanization.

The CLI does not invent a local state machine. status, document URL, recording URL, and listing URL are extracted from known response locations when present; the complete response remains authoritative.

Local refusal bounds

• source: 1–100,000 characters;
• turnaround: 5–10,080 minutes;
• price: 300–100,000,000 cents;
• idempotency key: 8–128 bytes, no control characters;
• screening percentage: 1–25;
• screening word maximum: 50–500;
• language name must be non-empty and paired with proficiency;
• screening instructions require a screening source file.

The exact messages and executed outputs are in walkthrough-humanization-order. The complete flags and envelope are in CLI reference — rentahuman.