API documentation
GenPolish exposes one deterministic endpoint. You send a draft, it returns the polished text, a token-level diff and a reason for every change — and it applies nothing you have not accepted. The pages below cover authentication, the request and response shapes, every error code, the nine categories a change can fall under, and how a voice profile biases a rewrite towards writing you already published.
Start here
- QuickstartThe legacy deterministic endpoint returns polished text, a token-level diff, and a rationale per change. save: true is currently unavailable.
- Core conceptsThese concepts describe deterministic polishing. AI rewrites instead return operation status, text and usage; they do not invent this engine’s score or explanations.
API
- POST /polishAnalyse a draft deterministically and return the polished text with its diff. This endpoint does not consume words or anonymous trials.
- GET /revisionsList the stored polishes of a document, newest first. Reading revisions never consumes quota.
- ErrorsRequest-level failures return an HTTP status, a stable machine code, a safe message and a request id. An accepted AI rewrite instead carries its pending or terminal state in the operation response.
Guides
No key yet, or nothing to automate? The editor does the same work in the browser, and shows every change before it is applied. Open GenPolish.