Billing & usage

Stacklink is priced per workspace, with unlimited members and no seat charges. All projects, Admins, Members and API keys share its allowances and credits. Existing agreements retain their terms. Your Billing page shows the agreement that applies to your workspace, and the Pricing page always shows the current offer, rates and trial.

Plans

Prices are USD before tax. Pro and Growth include email support. Enterprise support, capacity and collection terms are agreed in writing. Talk to us. New subscriptions are monthly; existing annual agreements retain their paid term. Rates beyond an allowance and for Workbench are listed on Pricing and on your Billing page.

Invitations and additional workspaces do not grant the same account owner another trial. Buying a plan starts a fresh paid allowance. Exhausting one resource moves it to credits, if its switch is on and credits are available; other included resources remain available until the trial ends.

Credits

Credits pay for usage beyond what your plan includes, Workbench running time and other paid work. Your Billing page shows your balance, where it came from and what it was spent on.

• Bought credits never expire. Admins buy them on Billing at any time with Stripe, or on your paying store’s Shopify bill. Each purchase has its own receipt.
• If your plan includes credits, Billing shows how many, when they renew and when they end. Plan credits are used before bought credits.
• When credits run out, paid work pauses before it starts. Nothing is billed automatically and included allowances keep working.

Amounts paid are in US dollars.

What counts

• Tool calls: successful toolkit actions, whether called through the API, SDK, MCP or Workbench. Five actions count as five calls. Transport and automatic retries do not add calls. Connection setup, configuration, browsing and status reads do not consume calls. Failed calls are not charged.
• Delivered events: one successful event delivery per configured destination. A trigger followed by webhook delivery is one event. Automatic retries and duplicate source events do not add deliveries.
• Memory: search, context and graph requests use the plan’s Memory allowance, separate from tool calls. Your agreement on Billing states how processing submitted content is counted. Ordinary record get/list, stored-profile browsing, metadata-only changes, history, status, export and erasure are unmetered. Source synchronization skips unchanged content and idempotent replays do not count again. Existing request-size, query and result limits still apply.
• Workbench runtime: active customer workload time by sandbox size. Queueing, approval waits before execution, platform startup, ordinary warm idle and platform cleanup are free. Running customer code remains billable while sleeping or waiting for network responses, including runs that fail or time out. Overlapping work in one sandbox counts once. Separate sandboxes count separately. A toolkit action inside Workbench still counts as a tool call.

There is no fee per Bot or Workflow: they use the allowances and credits their work needs.

Workbench runtime

Runtime is measured in active milliseconds. Stacklink reserves bounded intervals of up to five minutes and renews them while work continues, without restarting customer code. A requested timeout is a maximum, not a guarantee of funding: execution stops predictably if another interval cannot be funded. Each interval retains its original rate and billing period.

When the last workload ends, unused reservations return after settlement; a warm sandbox does not need to stop first. Retained files follow storage rules, without runtime charges.

A saved wait persists the completed step and stops unused compute. It is free; resuming may need startup time. Running code that blocks on a login, OTP or human response remains active until it ends the step.

Optional Keep ready keeps compute available for an explicitly approved, bounded wait at the same rate as that sandbox size. It needs a purchased plan. The ordinary 30-second warm grace is free. Paid ready time excludes overlapping active work and ends at its approved deadline, at most 30 minutes. Provider failure can still require a cold start from the saved continuation.

Spending controls

A switch for each resource decides whether credits can pay for it once its included amount is used. Turning one off stops that resource at its allowance; included allowances keep working. Only an Admin can change them, buy credits or set the low-credit email. Members can view plan status, limits and usage quantities.

A Bot can also have its own monthly budget. It only limits that Bot and never adds credits. Workbench tenant and session limits restrict capacity already available to the workspace; they do not add credits.

Payments and changes

An Admin selects a plan and continues to Stripe, which collects billing details. The plan activates after payment confirmation. An interrupted purchase resumes without creating another subscription. Billing shows invoices, payment recovery and the saved billing identity.

Upgrades start immediately with credit for unused paid time; downgrades begin at renewal and must fit the new project limit. Canceling stops the next renewal; the plan runs to the end of its paid period, and bought credits stay with the workspace. Refunds are not automatic; contact support for disputes and refund requests.

Workspaces billed through Shopify approve every plan change in Shopify. An upgrade starts once the paying store approves it. Shopify decides whether the renewal date stays or a new 30-day period starts, so Billing estimates the extra plan credits for both before you approve and shows the exact amount once Shopify confirms. A downgrade is approved now; your current plan stays until the date Billing shows, and the new plan starts then. The new plan's credits are granted for each full cycle. If Shopify's first period runs a little past the time already paid for, that short interval can get a proportional grant, and Shopify confirms the final amount. While Billing offers to keep your current plan, an Admin can undo the switch there. Once Shopify has replaced the original subscription, the switch can't be undone, but canceling renewal is still available.

Inspect usage

Billing shows each resource's used and reserved quantity, its allowance and rate, and the credits used. Credit activity lists every purchase, grant, use and expiry, newest first. Invoices and credit receipts stay available.

stacklink.billing.getUsage() exposes resources on the new agreement; usage events include resourceKey. Standard/premium compatibility fields describe legacy agreements and are not a second charge on the new offer. API keys with billing:read can inspect usage but cannot approve financial changes.