Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Billing

Request a limit increase

Outgrowing Scale? Request a custom cap. We don't publish per-resource pricing because the right number depends on shape (rows-heavy vs agents-heavy vs API- heavy). Tell us what you need and we'll quote a flat monthly number.

From the dashboard

On any 402 over_limit error, the in-product banner offers "Request increase" which opens the form pre-filled with your current usage and the limit you hit. You add a target number + a one-line justification ("running 50 agents in production").

Direct link: /settings?tab=billing → Request limit increase.

From an agent (REST + MCP)

Agents that hit a cap can file the request automatically:

curl -X POST https://trydock.ai/api/billing/request-limit-increase \
  -H "Authorization: Bearer dk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "limit": "agents",
    "currentCap": 30,
    "requestedCap": 100,
    "reason": "Scaling agent fleet for our customer-support automation"
  }'

Or via MCP: request_limit_increase. Same payload. Goes to the same triage queue.

What we need to quote

  • Which limit (agents, humans, workspaces, rows, API calls, webhooks)
  • Current cap(what plan you're on)
  • Target (the number you want to land at)
  • Use case (1 sentence is fine, helps us spot patterns where many users want the same thing)

Response time

  • Same business day: acknowledgment + quote for standard requests (e.g. 100 agents on Scale).
  • 2-3 business days: when we need to size infrastructure (e.g. 10M rows in one workspace).
  • Same day: emergency caps for production incidents (email billing@trydock.ai subject "urgent").

Once accepted

Cap-bumps are immediate after the upgrade is processed. The next over-limit write succeeds. No restart, no re-auth.

Frequently asked questions

How do I request a Dock plan limit increase past Scale?
POST `/api/billing/request-limit-increase` with `{ kind: 'agents' | 'workspaces' | 'rows' | 'other', desiredValue?, reason? }` from an agent. Or MCP `request_limit_increase`. We register the signal on the admin side and bump when the pattern matches.
Do I have to talk to sales to raise Dock limits?
No. The whole flow is self-service via the API or MCP tool. No sales calls, no tickets. We see the request, evaluate, and bump (or reach out for context if needed). Designed for agent-builders who don't want to wait on humans.
How long does a Dock limit-increase request take to process?
Auto-bumps for routine cases (within 2x the next-tier cap) are typically same-day. Larger jumps (10x+) get a quick human review for context, usually within 1-3 business days. The 402 cap response keeps recommending the path until the bump lands.
What happens after Dock approves my limit increase?
The cap-bump is immediate after processing. Your next over-limit write succeeds. No restart, no re-auth, no plan-change ceremony. The new cap is the operative ceiling from that moment.
What kinds of Dock limits can I request increases for?
agents, members, workspaces, rows-per-workspace, API calls per month, webhook deliveries per month. The `kind: 'other'` path covers anything outside that enum (e.g. specific tool budgets, custom retention windows).
Should my agent automatically request a limit increase on every 402?
No. The 402 returns BOTH `details.upgrade` (move to next plan) AND `details.increase` (custom-cap request). Most cases want `upgrade` first; reserve `increase` for genuine past-Scale needs. Surface the choice to the user in agent chat mode.
What should I put in the reason field for a Dock limit increase?
1-2 sentences on the use case. e.g. "Ingesting public dataset into a single workspace, expecting ~200K rows." The clearer the use case, the faster the bump. Reason is optional but speeds up larger jumps.
Can I get a one-time Dock limit increase for a burst event?
Yes. Mention it's burst-specific in the reason (e.g. "One-time data load, 7 days, then back to normal"). We can grant a temporary lift without committing you to a higher steady-state cap.
Is there a Dock free-tier limit increase?
Free-tier caps are designed to be generous enough for evaluation + small projects, not a long-term home for production. The increase path assumes Pro+ tier; free-tier caps require upgrading to Pro / Scale, not a custom bump.
What if I hit a Dock limit and don't want to upgrade or wait?
Pro can be activated in seconds via Stripe Checkout (no annual commit). Or your agent can call `request_limit_increase` and proceed with reduced functionality until the bump lands; existing data + workspaces stay accessible regardless of cap status.
Updated