If your team already pays a model provider, you can point TaskGoblin at that account instead of ours. The platform behaves exactly the same — same goblins, same cloud sandboxes, same integrations — but the model spend goes to your provider and your rate drops from $0.40 to $0.20 a minute.
Adding an account
An organisation Owner or Admin adds LLM accounts in the organisation's settings. You provide the provider and its credential — an API key, or the authentication a provider subscription uses — and the account becomes available to that organisation's runs immediately.
A few properties are worth stating plainly:
- The account belongs to one organisation. It is never shared with, visible to, or selectable by any other organisation on the platform.
- Credentials are encrypted at rest and are never sent back to your browser after saving. Editing an account shows you that a credential is set, not what it is.
- Removing an account stops it being chosen for new runs while keeping the history of the runs that used it, so past charges stay explainable.
Members who are not an Owner or Admin cannot see or manage these accounts.
How a run picks an account
When a run starts, TaskGoblin prefers your organisation's own LLM account whenever it is usable — active, healthy, and not rate-limited by the provider. That single decision fixes the run's rate at $0.20 a minute (or $0.10 if the run also lands on your own sandbox server).
If your account is unavailable — the key was revoked, the provider is rate-limiting you, the account was removed — the run does not fail. It falls back to a TaskGoblin account and is billed at the standard $0.40 rate. The choice is made once per run and recorded on it, so a run never changes rate halfway through.
What you still pay us for
The per-minute rate covers the platform: the sandbox your code runs in, the integrations, the scheduling, the review loop, the run history, and the support behind them. What it no longer covers, on this rate, is the model usage itself — that lands on your provider's bill, under your own quota, spend controls, and data-processing agreement.
That last part is the reason many teams choose this path: model traffic runs under the contract their organisation already reviewed.
Where to go next
- Pricing and credits — how metering and the three rates work.
- Bring your own sandbox server — pair this with your own infrastructure for $0.10 a minute.
- The cloud sandbox — where runs execute, and how credentials stay outside the agent.