Analyze. Rewrite. Re-analyze.
Prove it or say so.

Every humanizer runs your text through a model. Offbeat is different in what happens before and after that call.

1. The analyzer reads first, on your device

Before anything is sent anywhere, a deterministic engine measures the draft: sentence-rhythm variance and its distribution, inflation vocabulary, stock phrases, punctuation habits, structural fingerprints. Twenty-plus checks per language, each with named evidence. Deterministic means the same text always gets the same score, so a number you saw yesterday still means something today.

The English rules descend from a scanner that is byte-for-byte verified against its reference implementation. The Arabic rules were derived from real corpora: three million words of human Arabic against eight million words of machine Arabic, with every rule surviving a false-positive audit before it shipped. Rules that failed the audit are recorded as killed, not quietly kept.

2. The brief targets what the analyzer found

The rewrite instructions are built from the findings: these exact phrases, this rhythm problem, those punctuation restores. Fix these, leave the rest. The model never gets a vague "make it sound human". Arabic gets its own brief, written in Arabic, that tells the model to chain clauses with simple wa- the way human Arabic actually does, and to leave the writer's dialect alone.

3. Several drafts compete, the analyzer judges

The loop asks for multiple candidates at different temperatures, then scores every one with the same analyzer you saw in step one. Candidates that dropped a number, damaged protected content, or drifted in length are disqualified before scoring. The best faithful draft wins. In our committed evaluation this beats a single rewrite by three and a half points of final score, which is why it is the default and not an option.

4. Protected content never enters the model

Code blocks, inline code, URLs, and front matter are replaced by placeholder tokens before the rewrite and verified back into place after it, byte for byte. A rewrite that loses a placeholder is rejected automatically.

5. The gate, the retry, and the honest answer

The winning draft is compared to your original: fewer hard failures, no regressions, sane length. If it fails the gate, the loop retries once with the residual findings spelled out. And if nothing beats your original, the result says so. A tool that can never say "your version was better" is advertising, not measurement.

The scorecard is the product

What you get back is the before-and-after table, check by check, plus a word-level diff of every change. You can verify the improvement, disagree with a specific check, or download the full report as JSON. That artifact is the whole argument for Offbeat: here are real ones.

Also speaks editor

The same engine ships as a CLI (offbeat scan exits nonzero on failing prose, so it works as a CI gate) and as an MCP server for agent hosts like Claude Code, where your editor's own model does the rewriting and your text never touches our servers at all. Install steps for every surface live in the guides.