> ## Documentation Index
> Fetch the complete documentation index at: https://www.usenotra.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Limits and credits

> What Autopilot charges for, where the credits come from, and every limit and cooldown that paces its work.

## What Autopilot charges for

Autopilot charges when it opens a pull request. You pay what the model calls for that pull request cost, at least 1 credit, the same way [mentions on GitHub](https://www.usenotra.com/docs/integrations/github.md#what-a-mention-costs) are charged.

| Charged | Free |
| - | - |
| A post or fix that opens a pull request, from the daily run, a single automation, an idea you write or `@notra write a post` | Planning, rules checks, readiness rescans, measuring results, following pages until indexed, learning from edits and the daily brief |
| **Ask the agent** and **Let the agent decide** steps in [workflows](https://www.usenotra.com/docs/autopilot/workflows.md), from AI credits | Runs that find nothing to change, writes that fail, and pull requests that don't open |
| Changes you ask for on a pull request, like a GitHub mention | |

Pull request work uses your plan's **pull request credits** first, then your AI credits. The GitHub bot and Autopilot share the same pull request credit balance. The two agent workflow steps use AI credits only.

| Plan | Pull request credits | Autopilot |
| - | - | - |
| Free | 100 credits, once | Not included |
| Starter | 1,000 credits per month | Not included |
| Growth | 3,000 credits per month | Included |
| Scale | 5,000 credits per month | Included |

Your remaining budget is under **Settings → Billing → Usage** (see [Billing](https://www.usenotra.com/docs/organization/billing.md)). What each automation costs per run is on its page and on the **Automations** tab.

When both balances are empty, Autopilot skips scheduled runs until credits reset or you top up. If credits run out during a run, Autopilot can save a post as an idea or retry a fix without counting it as a failed write. An agent workflow step stops if AI credits are unavailable, even if pull request credits remain.

## Limits

| Limit | Value |
| - | - |
| Open Autopilot pull requests | 3 per workspace for pull requests Autopilot opens on its own. Ideas don't count, and posts you ask for (**Write now**, `@notra write a post`) always open |
| Open pull requests per fix, update or comparison automation | 1. The next waits until it's merged or closed. Content gap and release posts are limited per topic instead |
| Automatic post pull requests | 3 per 7 days to start, between 1 and 7 depending on how many you merge |
| Posts or ideas from the planner | 1 per run |
| Full runs | 1 at a time, up to 3 scheduled attempts a day |
| Run length | Ended after 2 hours without progress |
| Failed writes | Tried up to 3 times, then given up |
| Internal links | 1 pull request per 7 days, at most 3 new links per post |
| Landing page copy | 1 pull request per 14 days |
| Release post sources | Up to 15 repositories, 7 days back (up to 30 after a release post) |
| Reviewers | 10 |
| Rules | 50, of up to 300 characters |
| Workflows | 50 per workspace |

## Cooldowns

| What | Comes back after |
| - | - |
| Closed content gap post or comparison page | 90 days, or sooner for a comparison page when the competitor keeps winning |
| Closed readiness fix | 30 days |
| Merged readiness fix | Its issues are left alone for 14 days while it deploys |
| Auto-closed draft | 30 days |
| Idea nobody wrote | Expires after 21 days, can come back |
| Closed release post, refresh, links, landing copy or AI-readable fix | Never for the same item |
| Pages followed after a merge | 30 days |
| Before and after window | The last 14 days since the merge |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.