← Features

Generate docs

Generate docs from the code

Start from your repo instead of a blank page. Amendary drafts the pages, follows the layout of docs you already have, and shows the cost before anything runs.

Works with

  • Notion: worksAlso product updates
  • GitHub: works
  • Zendesk: worksSaved as drafts
  • Intercom: worksSaved as drafts

What it does

  • Drafts a set of pages from a repo: docs and guides, on-call runbooks, incident playbooks, or architecture decision records.
  • Runbooks and incident playbooks also read the repos your pages map as Background only, such as infrastructure or config repos.
  • 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, a repo’s docs folder or wiki, a Zendesk Guide section, or an Intercom collection.
  • In Zendesk and Intercom, each page becomes a new help article saved as a draft in your source language. Amendary never publishes it. You do, in Zendesk or Intercom.
  • Each engineering page gets one diagram designed from the code, when there is something to draw. You see it in the review and can remove it.
  • Generated pages are watched once they are published (or saved as drafts in Zendesk and Intercom), so daily checks keep them correct. Product updates are history and are not rewritten.

How it works

  1. Pick the repo, the audience, the document type and the destination. Engineering docs can be docs and guides, runbooks, playbooks or decision records. Help center can be docs and guides, or product updates in Notion. Zendesk and Intercom take Help center docs and guides only.
  2. The run writes in the tone and skills of the page it publishes under. Where that page has none, it uses the audience default: Conversational for Help center, Formal for Engineering docs.
  3. 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.
  4. 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.
  5. When you start the run, the credits are held and the run works in the background. If our server restarts, the run picks up where it stopped. Each page waits for your review before it is published.
  6. If a Notion page or docs folder 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 layout.

What it never does

  • It never publishes to a second destination. A Notion run writes to Notion only.
  • It never publishes a Zendesk or Intercom article. New articles are saved as drafts.
  • 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.

Evidence and review

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 Help center review mode, like the entries daily checks write. Pull requests with a label the page skips are left out of a backfill.

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

Limits

  • A page set comes from one repo. A product-updates backfill reads every repo that feeds its page.
  • Product updates go to Notion only.
  • Zendesk and Intercom get Help center docs and guides, with no diagrams.
  • A missing language of a Zendesk or Intercom article is drafted on its own, from the article. See Help-center languages.
  • The free sample is one page per page-set run, taken before you start it.
  • A run that reaches the workspace’s daily usage limit pauses and continues after the daily reset.

Pricing

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 month comes with starting credits (10 on Starter, 20 on Growth and 40 on Scale), granted once, and more credits come in one-time packs: 50 for €39, 150 for €119, 500 for €349.

The free trial has no credits. It includes the free sample page. Details are in Billing & plans.

Where to go next

Try Amendary on your own help center

Connect Notion, GitHub, Zendesk or Intercom and pick the articles to watch. Your first check shows what Amendary would fix, with the change as proof.

Free for 14 days with no card, and every edit waits for your review. Or free forever with your own Anthropic API key. Code is never touched.