Skip to main content

Usage & limits

OtoDock tracks what your agents cost and lets admins set budgets, so a busy team — or a runaway task — never produces a surprise. It also keeps an eye on disk space per agent.

Costs are shown at API pricing, for reference

Every cost in OtoDock is estimated at standard API pricing, so figures stay consistent across engines. When work runs on a subscription — Claude Pro/Max or ChatGPT, yours for your own chats and tasks, or the platform's for agent work — that number is only a reference: providers meter subscriptions under their own limits rather than per token, so it isn't what anyone actually pays. The estimate drives budgets only for platform API usage (a borrowed platform API key or the direct engine) — see below.

Usage tracking​

Every chat turn, task run, and meeting records its cost and token counts. You can see your own usage in your settings — daily, weekly, and monthly — broken down by agent. Admins get a platform-wide view: every user's usage, near-limit warnings, and a per-agent breakdown of where spend is going.

Your own subscription vs. the shared pool​

There's an important distinction in how usage is counted:

  • Your own subscription — when work runs on a subscription (yours for your own chats and tasks, the platform's for agent work), the provider meters it under their own limits. OtoDock shows an API-pricing estimate for reference but never caps it here.
  • Platform API usage — when work runs on a borrowed platform API key or the direct engine, that's metered usage OtoDock pays for — and it's what the budgets below cap.

In other words, limits protect the shared, platform-paid resources, not subscription usage.

Setting budgets​

Admins set limits from the admin Usage tab (on the admin pages), weekly and/or monthly:

  • By role — a default for each platform role (admin, creator, member).
  • By user — an override for a specific person.
  • By agent — a cap on a single agent's shared spend (tasks, triggers, meetings).

No limit means unlimited.

What happens at the limit​

  • At 80%, you see a friendly warning — work continues.
  • At 100%, new messages are blocked with a clear banner, and the in-progress turn finishes cleanly. An admin can raise the limit to lift the block.

Storage quotas​

Admins can also cap disk usage per agent, with a separate allowance for the shared folder and for each person's private folder:

  • Warnings are available everywhere — you're notified as an agent approaches its cap (at 90%, 95%, and 100%).
  • Hard enforcement — actually blocking writes past the cap — requires a native install on an XFS volume with project quotas (a Docker Compose install uses warnings only). See Installation.

Quotas never lose your data: reads and deletes always work, and a blocked write fails cleanly with a clear message. Admins configure and adjust quotas under Setup → System Settings → Storage Quotas.

Next steps​