Billing and usage

Plans, credits, and how to upgrade

Agent Handler bills on credits. Every call against the MCP endpoint spends credits, successful or not, and tool calls made with test API keys count the same as production usage.

This page is a quick orientation. The dashboard at Settings → Billing is the source of truth for your current plan, usage, and limits.

What a credit is

One tool call spends one credit. Agent Handler once charged more for some calls than others, and no longer does, so your credit usage and your tool call count are the same number unless your contract sets a different rate.

Plans

PlanWhat you are metered onBehavior at the limit
Free2,000 credits per monthTool execution blocks until the next cycle
ProA monthly allowance you pick, from 25,000 credits upward, with 2,000 bonus credits on topOverage is billed rather than blocked
EnterpriseWhatever your contract saysPer contract, and the billing page shows three months of usage history instead of a single figure
Employees ProEmployees provisioned through your identity provider, per user per monthNo credit limit to reach

Prices live on the pricing page, which is the source of truth for what each plan costs. The mechanics below are what does not change when a price does.

Only the Free plan blocks. Spend 2,000 credits in a month and every tool call returns 402 with billing_limit_reached until the cycle rolls over or you upgrade; the dashboard stays accessible, and only tool execution stops. On Pro, credits past your allowance are overage and appear on the end-of-month invoice alongside the base charge. On Enterprise, overage against the annual allotment is handled by your contract rather than cut off.

Provisioning employees changes your plan

If you provision employees through SCIM, your organization moves onto the Employees Pro plan as soon as the first user syncs. There is no button to press: the first IdP-provisioned user landing in Agent Handler is what moves you, from Free or from any paid plan.

Two things follow from that:

  • Add a payment method before you turn provisioning on. The dashboard asks for a card before it will generate the SCIM token, so an organization on Free hits that wall on its first attempt rather than at its first employee.
  • Organizations on an Enterprise contract stay on their contract. The contract already covers IdP-provisioned employees, so provisioning does not switch the plan.

The switch is recorded in the Audit Trail as ORG_SWITCHED_TO_EMPLOYEES_PRO, so you can see exactly when it happened. Employees Pro is priced per IdP-provisioned user rather than per credit, and that price is not on the pricing page, so confirm it with your account team before you turn provisioning on.

If the people using AI are your own employees and you want models, skills, and device rollout governed alongside tool access, Merge for Workforce is the product built for that, and it prices per seat. Agent Handler for Employees covers the tool half on its own.

Where to see your usage

Settings → Billing shows the current month’s usage against your limit, the cycle reset date, and a daily-volume graph. Logs → Tool calls drills into individual calls - useful when a spike on the billing page needs explaining. For per-user or per-Company breakdowns, the Registered Users page has a usage column on each user’s detail. To query usage programmatically, see Usage API.

Upgrading

From the billing page, click Upgrade, pick a plan, add a payment method. The new allotment applies immediately: the current month’s credits lift to the new plan the moment the upgrade processes. There is no proration, so the month carries the new plan’s full fee whichever day you upgraded on, and it is charged at the end of the month.

For Enterprise, contact sales. Custom contracts cover scoped quotas, dedicated support, and any non-default terms (data retention, region pinning, custom security review).

Payment methods

Stripe handles payments. Add a card at Settings → Billing → Payment method. Updates are immediate; the next charge runs against the new card.

For SEPA, ACH, or invoice-based billing, talk to sales. Self-serve cards cover Free and Pro; Enterprise contracts often run on invoice.

Approaching the limit

Two options:

  1. Upgrade. Fastest path. Takes effect immediately.
  2. Audit usage. A misconfigured agent or a runaway user can dominate spend. The Logs and Registered Users pages show where calls are going, and a spike that traces to one Registered User retrying the same tool is a bug to fix rather than an allotment to buy.

Agent Handler already rate limits MCP tool calls per Registered User as well as per organization, so no single user can saturate your throughput. That is a per-minute rate, not a monthly cap: it does not stop one user from spending the month’s credits.

Cancelling

Settings → Billing → Cancel subscription downgrades you to Free at the end of your current billing cycle. Existing data is retained - you can resume on the same plan anytime by upgrading again.

For full data deletion (account closure with no resume path), contact support. The account closure is recorded in the Audit Trail and triggers a 30-day grace period before data is permanently purged.

Next

If you hit a specific error, see Troubleshooting. Otherwise pick a topic from the sidebar.