Credits and consumption

Aidoo AI is billed per user licence. Agents are not: they consume credits, because an agent running every hour does not cost the same as a weekly one.

The credit pool

Your workspace holds a single pool, fed from three sources:

Monthly credits reset at renewal. Packs do not: they stay available and are only consumed after the monthly allowance runs out.

The tiers

The trial is capped at 500 credits or 30 days, whichever comes first, and limited to economical models.

Event watching, in detail

The last column of the table is the rhythm at which Aidoo goes and looks inside Odoo for something new. It only concerns agents fired by an event.

There is no webhook and no module to install on your database. On each pass, Aidoo queries the watched model and keeps the records created or updated since the previous pass, then groups them into one run.

The interval comes from the tier and cannot be set per agent: every event agent in the workspace follows the same rhythm.

Scheduled agents are not concerned. An agent on a schedule follows exactly the time expression you give it, in its own timezone. Nothing stops you running it every quarter of an hour on Starter: there, your credit pool sets the limit, not the tier.

Outside the operating window, nothing is lost. If you have defined active hours, watching stops outside them without moving its marker. Whatever happened overnight is handled on the first morning pass.

When there is a surge. One pass picks up at most 200 records, split into runs of 25. The rest is taken on the following pass, nothing is skipped.

What a run consumes

Credits are computed from the tokens exchanged with the model, multiplied by that model's coefficient. An economical model counts as one, the most capable ones up to four times more.

What makes consumption vary, in order of importance:

The model chosen. This is factor number one. Moving from a capable model to an economical one divides the bill by four on the same mission.

The number of records processed. Every record read takes up room in the conversation, and that conversation is sent back to the model on every turn. Processing 200 invoices costs well more than twice as much as 100.

The number of round trips. A mission requiring ten tool calls costs more than one requiring three, because the history grows with each turn.

The external tools enabled. A connected application with no restriction on its tool list reloads its whole catalogue every turn. It is the most frequent cause of unexplained consumption.

The frequency. An agent running every 5 minutes fires 288 times a day; the same agent once a day fires once.

Bringing the bill down

Tracking consumption

The Billing page shows the current month's gauge and the balance held in reserve. The "Consumption history" button opens the detail: credits spent month by month, broken down agent by agent.

Two lines are worth a glance: Aidoo Module (sandbox), a reminder that deployments draw on the same pool, and Other / deleted agent, which gathers what agents since archived consumed. What was spent stays visible, even when the agent no longer is.

An alert warns you at 80% of the monthly pool. That is the right moment to choose between buying a pack, spacing an agent out, or changing its model.

When the pool runs dry

There is no overage billing. You will never get a surprise invoice because an agent looped: it stops, it waits, it tells you.

A budget per agent

On top of the shared pool, each agent can be given its own monthly ceiling. Useful when an experimental agent lives alongside production ones: the former cannot drain the latter's pool.

Next step

• Best practices and troubleshooting: an agent consuming too much
• Rules and permissions: restricting external tools