Build with Overwride

The web app is one way in. On the Pro and API plans you can also rewrite from an AI assistant, from your own app, or from the terminal. Every route makes the same rewrite, stores the same Overwride record and returns the same footer.

Get a key

Sign in at overwride.com/app, open API keys and create one. Keys start with ow_live_ and are shown once, so put it straight into a password manager or a secret store, never in chat or a repository. You can revoke a key from the same page.

Keys work on the Pro and API plans. Starter is web app only; a key on a Starter account gets plan_channel_not_allowed.

What it costs

A rewrite through MCP, the API or the CLI counts exactly like one in the web app. Pro spends its 1,000 monthly rewrites first, then credits. The API plan has no monthly cap and spends credits at €0.018 per rewrite from the first call. A rewrite that fails is never charged. Checking a post and reading a record are always free. See pricing.

Rules that keep a post matching its record

• Publish the rewrite exactly as returned. The checker matches exact text. Do any platform fitting, such as length or hashtags, on the draft before the rewrite, and rewrite again if the text changes afterwards.
• The footer is optional. A post matches with or without it, because the checker ignores a trailing footer. When you use it, keep the wording as returned. It carries the record id.
• Describe the result accurately. Call it an “Overwride rewrite” or an “Overwride record”, and don’t present it as proof of who wrote the draft. Overwride makes no claim about that.