Billing & plans

Yes, 14 days with no card: 1 repo, 1 help center in up to 2 languages, 50 help articles (translations included) and 10 docs pages, and daily checks. The trial is review-only, so you approve every change before it touches a page. During setup you can check a repo’s recent changes to see what Amendary would draft.

The trial comes with no credits. You can still take one free sample page from a docs generate run (not a product-updates backfill) to judge the quality.

When the trial ends, scheduled checks pause. Your dashboard, history and manual “Check now” stay available. Subscribing restarts daily checks and lets owners set an audience to Apply automatically (see Queue & reviews).

The subscription covers the always-on service: daily checks and the corrections that keep your mapped pages in sync. It is a flat price per workspace, not per seat, and it is not billed per correction. Whether a check drafts one correction or twenty, the subscription price is the same. A daily usage limit, set by Amendary to stop abuse and larger on bigger plans, pauses checks until the next day in your team’s timezone when it is reached. Settings > Usage shows your usage.

The plans, prices and their limits (help articles with translations counted, help centers, repos and docs pages) are on the pricing page. Settings > Plan & billing shows your usage against the limits. A limit never deletes anything; reaching one only stops you adding more.

Exactly two kinds of run spend credits:

• Generation: drafting a documentation set from a repo, backfilling a product-updates changelog, and suggesting a diagram for a page, and drafting a missing language of a Zendesk or Intercom article.
• Cleanup: checking pages against your code and its history. Searching the history costs nothing; the credits pay for reading the pages and giving each one its outcome.

The daily checks and corrections you pay for with the subscription never touch your credit balance, and neither does watching a page after a cleanup or a new page a check proposes.

A credit is a fixed amount of model usage. Your first paid month comes with starting credits (10 on Starter, 20 on Growth and 40 on Scale), granted once: cancelling and subscribing again does not grant them again. The trial has none. Running out of credits only blocks new runs of these kinds; it never stops the daily checks the subscription covers.

A generate run reads a repo’s whole history, so before you commit Amendary shows a concrete estimate of the scope, for example “about 40 pages” or “up to 340 changelog entries”, with the credit cost and your current balance.

Nothing is charged while you set the run up. Credits are held only when you start it, and the estimate is rounded up so a run never costs more than shown. If your balance is short, Amendary tells you exactly how many more credits to buy. For a docs set you can also generate one free sample page first. A diagram designed during the run is part of the estimate. If a run stops early, unspent credits are returned to your balance. A restart on our side does not lose a run: it resumes where it stopped, with its credits still held.

The same way as a generate run. A diagram suggestion holds its estimate when it starts, settles to what it used when the proposal is filed, and refunds everything when no diagram fits. A cleanup shows a line for the pages and one per repo before it starts, holds that, and refunds the unused part when it ends or is cancelled.

Neither starts when your team has reached its daily usage limit. A cleanup that reaches the limit pauses and continues after the daily reset.

An owner buys credits as one-time packs on Settings > Plan & billing. Larger packs cost less per credit:

• Small: 50 credits, €39.
• Medium: 150 credits, €119.
• Large: 500 credits, €349.

A pack is a one-time purchase, not a recurring charge. Credits do not expire, and a pack adds to whatever balance you already have.