Generate docs from the code

• Drafts a set of pages from a repo: docs and guides, on-call runbooks, incident playbooks, or architecture decision records.
• Backfills a product-updates changelog in Notion from the releases, tags or commits of the repos that feed it.
• Publishes to the one destination you pick: under a Notion page, or to a repo’s docs folder or wiki.
• Generated pages join daily checks when they are published, so they stay correct afterwards. Product updates are history and are not rewritten.

1. Pick the repo, the document type and the destination.
2. For a page set, Amendary reads the repo (README, file tree and key source files) and proposes an outline over the whole codebase, with no cap on pages. For product updates and decision records it counts the history instead.
3. You see the estimate in credits next to your balance. Nothing is charged yet. For a page set you can take one free sample page to judge the quality first.
4. When you start the run, the credits are held and the run works in the background. Each page waits for your review before it is published.
5. If the destination already holds docs, the run follows them: it reuses their heading layout and appends to a changelog page you keep. Only an empty destination gets our default page set and index.

• It never publishes to a second destination. A Notion run writes to Notion only.
• It never invents a decision. A pull request that decided nothing gets no record, and a reason that was never stated is written as not stated.
• It never guesses a runbook command. Commands, paths and defaults come from the repo word for word, and a step whose exact command is not there gets a “Needs verification” note instead.
• It never charges more than the estimate. A run that stops early refunds what it did not use.
• It never writes a product update for docs, website or internal-only changes.

A page set is drafted from the repo context Amendary read, and you review each page before it is published. Each decision record is written from one pull request or commit. Product-update entries follow your review mode, like the entries daily checks write.

What each type contains and how it is kept current afterwards is in Document types.

• A page set comes from one repo. A product-updates backfill reads every repo that feeds its page.
• Product updates go to Notion only.
• The free sample is one page per run, taken before you start it.
• A run that reaches the workspace’s daily model budget pauses and continues after the daily reset.

Generation spends credits. A credit is a fixed amount of model usage. The estimate is rounded up, held when you start, and settled to what the run used. Your first paid plan comes with a starting grant, and more credits come in one-time packs: 50 for €39, 150 for €99, 500 for €279.

The free trial includes the free sample page, not a credit grant. Details are in Billing & plans.