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.