Plan Tiers and Tool Gating

Every StackJack tool has a required plan tier, and every connector you subscribe to has a plan. This page explains how the two interact, what each tier unlocks conceptually, and what happens when a call hits a limit.

Plans are per connector, not per account

StackJack subscriptions are per connector. Your tenant might run HaloPSA on Pro and NinjaRMM on Free at the same time. When the AI calls a halo_* tool, StackJack checks your Halo subscription's plan; when it calls a ninja_* tool, it checks your NinjaRMM subscription. There is no single account-wide tier.

The available plans are Free, Pro, Business, and Enterprise. Current pricing for each is shown in the portal and at checkout.

What each tier unlocks

Every tool is tagged with the minimum plan needed to call it. You can see each tool's tier badge in the portal (on the Permissions page and in the tool selector on Endpoints). Conceptually:

• Free — the core read surface of each connector: listing and fetching tickets, devices, companies, assets, and other day-to-day lookups. Several connectors (for example Pax8, Kaseya Quote Manager, ConnectWise Sell, and Telivy) place their entire tool set in Free — for those, paid tiers differ only in the monthly call allowance.
• Pro — write operations (create, update, delete), actions (run scripts, trigger jobs), and advanced or analytical tools, on top of everything in Free.
• Business — for almost all connectors, Business unlocks the same tool set as Pro with a much higher monthly call allowance. The exception is CIPP, which has a small set of Business-only tools. Business is the "same tools, more volume" tier.
• Enterprise — everything, with no monthly call cap.

Exact per-tier tool listings for each connector are published in the generated connector tool catalogs.

Monthly call allowances

Each connector subscription includes a monthly tool-call allowance, enforced per billing cycle:

Details that matter in practice:

• Only successful calls count. A call that fails — whether blocked by a gate or failed at the vendor API — never consumes your allowance.
• The cycle is your billing cycle, not the calendar month. The counter resets when your connector subscription renews. Your dashboard's per-connector usage bars track the same cycle the enforcement uses.
• StackJack can set a custom limit on a subscription — if you have arranged a custom allowance, the enforced number is the one shown on your dashboard.

There is no per-minute rate limit

StackJack does not impose a per-minute or burst rate limit on your MCP traffic. The monthly plan allowance is the enforcement point. (Responses include informational X-RateLimit-*-Burst headers, but they do not reflect an active limit.)

Two things can still slow down or reject individual calls:

• Vendor API protection. StackJack self-throttles its outbound calls to each vendor API so your API keys are never rate-banned by the vendor. When that throttle engages, your tool call simply takes a little longer — it is delayed, not rejected.
• Vendor rate limits. If the vendor still returns a "too many requests" response, the tool call returns a structured rate_limited error and the AI is told to wait and retry. See Tool errors and troubleshooting.

The gate sequence: what is checked on every call

Every tool call passes through a fixed series of checks before it executes. If a check fails, the AI receives a specific, structured error (never a silent failure):

1. Client tool selection — is the tool enabled for this MCP client and team member? If not: tool_not_allowed.
2. Plan tier — is the tool's required tier within the connector subscription's plan? If not: plan_upgrade_required.
3. Billing health — is the subscription's payment status active? If not: subscription_past_due, subscription_paused, subscription_canceled, or subscription_inactive (for any other non-active state).
4. Billing cycle — has the current period ended without a renewal yet recorded? If so: subscription_period_ended.
5. Monthly allowance — is the cycle counter under the limit? If not: monthly_limit_exceeded (the error includes your current usage, your limit, and the billing-cycle window).
6. Instance version — only for tools that declare a minimum connected-product version. If the connected instance reports an older version: instance_version_unsupported. (Today no tool sets a real version floor, so this check never blocks anything in practice.)

Each error includes plain-language guidance the AI can relay to you. The full error reference is in Tool errors and troubleshooting.

What a downgrade or cancellation looks like

When a connector subscription is downgraded or canceled:

• Tools above the new plan tier (or all of the connector's tools, on cancellation) disappear from the harness's tool list the next time it refreshes its tools.
• Saved tool selections that reference now-unavailable tools behave differently by surface: in the automation tool picker they are flagged as stale with a one-click repair; in the MCP-client and team-member editors they are simply hidden from the checklist and excluded from the selection count (details).
• If the AI calls a no-longer-available tool before its list refreshes, it receives the specific gate error rather than a generic failure.

Checking your own gating live

Ask your connected AI to run:

• stackjack_session_info — shows each active connector, its plan, its monthly call limit, and how many tools are accessible to this client versus the total.
• stackjack_list_tools — lists tools with their required plan and an accessible: true/false flag for your current session.