Skip to main content

Plans and quotas

The plan of an organization decides how many applications and agent wallets it can have, how many transactions its agents can make each month, and whether it can use the multisig treasury. A new account starts with a free trial, without verifying its e-mail address or accepting the terms first. This page explains the trial, what must be done before the first payment to Keyban, the monthly transaction quota and what each plan unlocks. The prices of the plans are not on this page: see the plans on keyban.io. Who owns what is explained in Organizations, applications and wallets.

From the dashboard​

Plans and usage are under Billing in the organization menu. Reading them needs the billing right, and changing them needs the right to update billing. Owner and Admin hold both.

The free trial​

A new Wallet for Agents account starts on the Free plan with a trial of 90 days. The trial is never billed: no payment is taken when it ends. Signing up for it needs neither a verified e-mail address nor accepted terms: the organization and the first wallet are created on one screen, and on the free plan the terms are accepted later in the guided setup. See Get started.

  • During the trial, the Billing page shows "Trial until" and the date. Owners and Admins are reminded by e-mail 15 days and 3 days before the end.
  • When the trial ends, Keyban freezes the agent wallets of the organization. A frozen wallet is paused like with the emergency stop: every payment is refused with policy/emergency-stop, and the dashboard shows "Your free trial has ended" with an Upgrade now button. The funds stay in the wallets.
  • To reactivate the wallets, upgrade to a paid plan from Billing, with Change plan, or from the banner. The wallets that the trial froze are reactivated. A wallet that a person had paused by hand stays paused.

Before the first payment​

Two things protect the money that moves, and both can be done after the account exists:

  • A verified e-mail address is required before any payment to Keyban: upgrading to a paid plan, opening the billing portal, and inviting members. Until the address is verified, the dashboard replaces the button with "Verify your e-mail address to continue to payment." and a Resend the e-mail button. The server refuses the action with EMAIL_VERIFICATION_REQUIRED (403) otherwise. Buying USDC by card is a payment to Stripe, not to Keyban, and does not need it.
  • Accepted terms are required before money moves: card top-ups and upgrading to a paid plan are refused with LEGAL_ACCEPTANCE_REQUIRED until the organization has accepted the current General Terms and Conditions. The organization counts as having accepted them when one of its members has accepted the current version. The guided setup asks for them in its Accept our legal documents screen and cannot be skipped until they are accepted.

The monthly transaction quota​

Each plan includes a number of transactions per calendar month, shared by every wallet of the organization. A transaction is a payment that Keyban signed. The quota resets on the 1st of the month, at midnight UTC.

The Usage tab of Billing shows how many transactions were made and the limit, and the agent pages of the dashboard carry a banner with the usage. It also holds two settings, which need the right to update billing:

  • Block my agents when the quota is reached. It is on by default. With it on, every payment is refused once the quota is reached, until the 1st of next month. With it off, payments keep going and the transactions beyond the quota are billed on the monthly invoice. It can be turned off only on a plan that allows billed overage. On the Free plan the switch stays on: the trial stops the agents at the quota.
  • Email alerts. Nobody is e-mailed until you pick recipients, who must be members of the organization. The banner always shows on the dashboard.

When the quota is reached and blocking is on, the plan has to change, or billed overage has to be allowed, before the agents can pay again. Upgrade with Change plan. To allow billed overage, turn off Block my agents when the quota is reached.

What each plan unlocks​

FreeStarterGrowthEnterprise
Applications225Set with Keyban
Agent wallets included2530Set with Keyban
Transactions per month50025,000300,000Set with Keyban
Wallets beyond the included numberNot allowedAllowed, billedAllowed, billedSet with Keyban
Transactions beyond the quotaNot allowedAllowed, billedAllowed, billedSet with Keyban
Multisig treasuryNoNoYesYes

The numbers are those of the plans today. Billing, under Usage, always shows the limits that apply to your organization, and the plans on keyban.io are the reference for what is on sale.

Missions are available on every plan. See Missions.

What the agent can do​

The agent has no tool to read or change its plan. It sees the effect of the quota:

  • When the monthly quota is used up and blocking is on, the payment is refused with policy/transaction-quota-reached. It applies to every wallet of the organization, until the 1st of next month (UTC). The agent does not retry, and tells the user to ask an organization admin to upgrade the plan, or on a plan that allows it, allow billed overage in Billing, under Usage (on the Free plan, only an upgrade). See Refusal reasons.
  • When the trial has ended, the agent sees policy/emergency-stop on every payment, like a paused wallet. It reports it and asks the user to upgrade.
  • When the organization has not accepted the terms and the Keyban welcome offer would have paid, the payment is refused with policy/terms-not-accepted. The agent asks the user to accept the terms in the dashboard, then retries.

An assistant using the admin tools of the Keyban MCP server, after keyban admin login, acts with the rights of the person who signed in. It can read the quota with get_transaction_quota, and with the right to update billing, change the blocking switch and the alert recipients with update_transaction_quota. Changing the plan itself is done in the dashboard. See the Admin tools.

Limits​

  • The trial lasts 90 days and is never billed. When it ends, the wallets are frozen until the organization upgrades.
  • The quota counts the transactions of all the wallets of the organization together, per calendar month in UTC.
  • Turning off blocking is possible only on a plan that allows billed overage.
  • Alert recipients must be members of the organization, and there can be at most 20.
  • Only Owner and Admin can change the plan or the quota settings.
  • A payment to Keyban (upgrade, billing portal) needs a verified e-mail address, and an upgrade or a card top-up needs accepted terms.
  • The multisig treasury needs the Growth plan or above, or a grant from Keyban.