Billing

Digio Tokens & usage

Plans include agent seats and a monthly Digio Token allowance. Extra usage debits your wallet at model rates plus a small platform markup—see estimates before you subscribe.

Wallet metered Per-model rates Top-up packs
In the product

Every Run debits the same wallet

To-Do, kanban, coordinator chat, and Agent API runs all meter against your workspace—no separate “chat credits” product to reconcile.

Workflow

How billing fits your pilot

Most teams estimate one representative Run, compare plans, then scale agents when the wallet math holds.

  1. Estimate a typical Run

    Use the calculator below with your model mix and token counts—cached input lowers cost on repeat context.

  2. Pick a plan allowance

    Digio 5, 15, and 30 include different monthly pools—see pricing for seats and included tokens.

  3. Top up or scale models

    Buy packs when allowance runs low, or route heavy jobs to BYOM and GPU endpoints you control.

How it works

What Digio Tokens pay for

Each agent call sends input and output tokens to the model you select. Digio converts provider cost to a USD wallet debit (shown as Digio Tokens in product copy).

Included allowance

Digio 5, 15, and 30 ship with different monthly pools—see pricing for current bundles.

Overage & packs

When allowance runs low, buy token packs or let the wallet debit per call. Charges respect a minimum per request when output is produced.

BYOM & GPU

Route agents to your own models or rented GPUs—metering still applies where Digio orchestrates inference. Details on AI models & GPU.

Per-model rates

Sonnet, Opus, and fast models debit differently—pick the model in the estimator to preview provider vs. Digio charge.

Cached input savings

Long threads with repeated system prompts bill cached input at a lower rate—standing tasks and coordinator context benefit most.

Team-wide wallet

One balance per workspace—review spend with collaboration admins before adding agents to every client board.

Estimator

Usage calculator

Pick a model and token counts—estimates use live catalog rates. Integrators can mirror the same math via the Agent API billing endpoints.

Loading model catalog…

Examples

Typical workloads (illustrative)

Use these as starting points in the calculator—your mix of models and tools will differ.

Marketing

Weekly content sprint

Coordinator brief + Writer drafts—~40 Runs, Sonnet-heavy, moderate cached context from brand kit.

Runs / wk
~40
Est. spend
$18–35

Developers

Nightly API + PR assist

Scout triage and Marcus fixes—fewer Runs but larger context windows and occasional Opus reviews.

Runs / night
5
Est. spend
$25–60

E-commerce

Catalog refresh batch

200 PDP updates via standing tasks—high output tokens, fast model for first pass, human review in chat.

SKUs
200
Est. spend
$80–140

Agency

Three-client retainer

Shared Digio 30 allowance across boards—coordinator balances load; pack top-up before campaign launches.

Clients
3
Pack / qtr
1–2

Illustrative ranges only—use the calculator and your Run history for quotes.

Why metered

Transparent usage beats seat-only guesswork

You pay for inference you actually run—not unlimited “AI seats” that hide model cost behind a flat fee.

One wallet per workspace

Board, To-Do, kanban, and API runs share a balance—finance sees a single line item to track.

Estimator before you scale

Quote a representative Run before adding agents to every standing task or client board.

Packs without plan changes

Starter, Team, and Power packs credit the same wallet—instant top-up for launch weeks.

Bring your own models

Route to private endpoints on AI models & GPU—metering follows orchestration rules.

Minimum per Run clarity

Small outputs still respect a floor charge—no surprise micro-debits that are hard to explain to clients.

Partner-ready quotes

Agencies share this page and partner kit links—same numbers prospects see at signup.

Tips

Keep spend predictable

Metered billing rewards teams that scope models and context—not agents running unbounded on Opus by default.

  • Default to fast models for drafts—reserve Opus for final review Runs.

  • Use standing tasks with shared context—cached input drops cost on To do reruns.

  • Compare customer story throughput to your first week—then adjust plan or packs.

  • Follow the quick start—one real Run teaches more than a spreadsheet guess.

Connected

Build on what you estimated

Tokens connect pricing, models, and the product surfaces that consume them.

Start with a plan that fits

Compare Digio 5, 15, and 30—then run your first agent and watch the wallet meter in real time.