Custom Agent pricing

credit
In this Article

Everything you need to know about Notion credits for Custom Agents, including how pricing works, how to monitor usage, and what happens once billing begins.


Notion credits are used to run Custom Agents and are available as an add-on for Business and Enterprise plans. How many credits a Custom Agent uses depends on the task. Simple tasks use fewer credits, while more complex, multi-step workflows use more.

Notion credits are shared across your workspace and reset each month, so unused credits don’t roll over. Admins can buy and manage credits from the Notion credits dashboard, with additional options available through your account team.

There are no changes to Business or Enterprise plan pricing. Existing AI features like Notion Agent, AI Meeting Notes, and Enterprise Search remain included at no extra cost. Notion credits are available as an add-on to Business and Enterprise plans and are billed alongside your existing subscription.

How Notion credits are priced

Notion credits cost $10 per 1,000 Notion credits, with each Custom Agent run using credits based on task complexity. You can purchase pre-set amounts in-product starting in the hundreds and scaling into the thousands based on your team’s needs.

If you have an account team, you can purchase Notion credits through them with additional credit options available to fit your needs.

Now through May 3, 2026:

Custom Agents are free to use on Business and Enterprise plans, including Business trials. During this time, teams can explore how Custom Agents fit into their workflows, and admins can track their team's patterns in the Notion credits dashboard to understand usage and estimate future credit needs.

Admins (Business and Enterprise plans) can manage who can create Custom Agents and disable Agents anytime to guide controlled rollouts.

Starting May 4, 2026:

Starting May 4, 2026, admins can purchase Notion credits. Custom Agents will start using Notion credits when they run.

If you manage billing in-product, you can buy credits directly through the Notion credits dashboard in preset tiers, ranging from hundreds to thousands. If you work with an account team, reach out to them to explore credit options.

What happens if I don’t purchase credits starting May 4, 2026?

If your workspace has live Custom Agents from the free beta, admins will need to purchase Notion credits to keep them running. If there aren’t enough credits, Custom Agents will pause at your next monthly service date.

If there are insufficient credits, Custom Agents will pause automatically so you’re never charged unexpectedly. They’ll only resume running once an admin purchases Notion credits.

Custom Agents run on schedules or triggers and use Notion credits based on the work needed to complete each task. This can include reading information, searching across tools, reasoning through next steps, chatting with the agent, and creating or updating content. In general, the more work an agent does, the more credits it uses.

The amount of Notion credits used depends on these key factors:

  • How much information a Custom Agent works with: Reading longer pages, searching more content, or scanning larger databases generally uses more credits.

  • Connected tools: Each tool a Custom Agent interacts with adds steps, which can increase credit usage.

  • How many steps are involved: More complex, multi-step workflows use more credits than simple tasks.

  • How often a Custom Agent runs: Custom Agents that run on a schedule or are triggered frequently will use more credits over time.

  • Model choice: More advanced models use more credits because they handle more complex reasoning. For most use cases, we recommend Auto, which lets Notion choose the best model for each task.

After each run, admins can see exact usage in the Notion credits dashboard.

Here’s an example that shows why two Custom Agents with similar goals may use different amounts of Notion credits:

Example

Custom Agent type

What happens behind the scenes (typical steps)

Why it uses more / fewer credits per run

Example 1

Simple Task Routing Agent
Routes incoming product feedback to the correct product area

• Reads a message from a Slack channel
• Looks up the right owner in a People database
• Creates a task and assigns it to that owner

Fewer credits per run because it processes a small amount of info and takes only a few steps

Example 2

More complex Task Routing Agent
Routes incoming product feedback, prioritizes follow-ups, and drafts an action plan

• Reads messages from a Slack channel
• Searches across multiple databases for ownership + context
• Evaluates urgency and impact
• Creates a task with multiple fields like priority, category, and owner
• Adds a sub-page with recommended next steps
• Notifies the assigned team in Slack

More credits per run because it reads more, makes more decisions, and completes more steps each time it runs

Key takeaway

Even if two Custom Agents run the same number of times per month, the one that takes more complex steps per run will use more Notion credits.

Use the examples below to get a general sense of potential costs, but keep in mind your actual Custom Agent provides the most accurate estimate of your expected Notion credit needs.

The examples* below show Custom Agents that run approximately 30-60 times per 1,000 Notion credits, based on their tasks. Your usage may be higher or lower depending on how your Custom Agent is set up.

Example 1: Q&A agent

  • What it does: Answers company policy questions in Slack

  • What it typically works with:

    • Searches Notion policy databases

    • Writes a short response

    • Posts the answer in Slack

    • Creates a task for follow-up if the question can’t be answered

Example 2: Task routing agent

  • What it does: Routes feature requests or bugs to the right engineering team

  • What it typically works with:

    • Reads messages from connected Slack channel

    • Searches team database and identifies the correct team

    • Creates a task with a few properties like owner, priority, and category

    • Sends a notification

Example 3: Status update agent

  • What it does: Creates a weekly leadership update on progress and risks

  • What it typically works with:

    • Reviews your team’s meeting notes

    • Searches project database from the past week

    • Identifies key updates and blockers

    • Writes a structured update in Notion

*These examples are based on internal data as of February 20, 2026 and are provided as a general reference. Actual Notion credit usage may vary depending on your setup, including how much information a Custom Agent works with and the tools it uses.*

Admins can view Notion credit usage by agent in their dashboard.

Admins on Business and Enterprise plans can monitor usage in the Notion credits dashboard. The dashboard helps admins track Custom Agent usage and Notion credit spend across their workspace.

Tracking credit usage

Admins can track Notion credit usage in real-time using the Notion credits dashboard. Starting Feb 24, 2026, while Custom Agents are free to use, admins can track Custom Agent usage and estimated credit needs to plan ahead.

Purchasing Notion credits

Starting May 4, 2026, admins can purchase Notion credits to keep Custom Agents running.

  • If you manage billing in-product: You can purchase pre-set amounts that range from hundreds to thousands of credits based on your team's needs. Custom Agents will automatically pause if credits are insufficient at your next monthly service date.

  • If you work with an account team: Your Notion account team is here to help you plan and purchase Notion credits, including exploring additional credit options based on your company's needs.

Every Custom Agent is different. Credit usage is impacted by a few factors you can adjust.

Four factors affect efficiency:

  1. Run frequency: Make every run count

  2. Context size: Be intentional about what your agent references

  3. Steps and reasoning: Make every tool call count

  4. Model selection: Let Notion choose for you or customize based on your needs

Getting these right helps your agent run efficiently, delivers better results, and keeps costs predictable.

1) Run frequency: reduce how often your agent runs

Limit runs to reduce costs. Design triggers so the agent runs only when it’s likely to take action.

Start small and scale up

  • Begin with weekly runs instead of daily runs.

  • Start with one channel or workflow and fully automate it before expanding to others.

  • Increase frequency once results are reliable.

Use high-signal triggers so your agent runs only when needed

  • For Slack: Trigger on @mentions or a specific emoji reaction instead of all messages.

  • For Notion: Trigger on specific property changes instead of every database update.

  • For Notion Mail: Trigger on a filtered set of emails instead of every message.

Expect some “No action needed” runs

  • These happen when the agent determines there’s nothing to do. This is normal and efficient: the agent checks the trigger and instructions, then exits.

  • If you see many “No action needed” runs, make your trigger more specific. You can also add a simple qualifying check in your agent instructions (for example, only proceed with X step if the message includes a customer name and a link)

    .

2) Context size: be intentional about what your agent references

Keep the scope tight. The more content an agent reads, the more work each run requires.

  • Point the agent to the smallest possible scope—ideally a single page, or a few pages that link to sub-pages the agent can load only if needed.

  • Avoid asking the agent to search broadly if you already know which database or page should be the source of truth.

3) Tool calls and reasoning: limit the number of steps

Searching across lots of content and reading large pages uses more credits. To reduce usage, narrow where your agent looks and combine related reads when possible.

  • Be clear about what “complete” or a successful result looks like so the agent can finish in fewer steps.

  • It’s more efficient if the agent calls multiple tools at the same time instead of one by one. Encourage parallel tool use in your instructions when possible.

    • Can run at the same time: “Read the Projects database, the Engineering Slack channel, and the latest sprint notes page at the same time.” These sources are independent, so the agent can read them simultaneously instead of one by one.

4) Model choice: Which model it uses

By default, your agent’s AI model is set to Auto, which lets Notion intelligently select the best model for each task. This works well for most agents, but you can choose a specific model at any time.

Model choice affects credits per step. If quality is consistently higher than you need, consider a less expensive model.

Additional controls admins can use to manage credit usage

Admins have extra controls to help manage Agent runs and keep credit usage efficient across the workspace.

For Business and Enterprise admins:

  • Disable Custom Agents at any time to prevent unnecessary runs

  • Control who can create agents by allowing everyone, workspace owners only, or selected members

For Enterprise admins:

  • Review AI analytics regularly to track activity trends and understand where credits are being used

  • Plan credits proactively by working with your account team to explore flexible options as your needs grow

More resources


Give Feedback

Was this resource helpful?


Powered by Fruition