Context & usage

Daily token & cost budgets

Put a boundary around daily work.

Pause work based on configured daily token or spending budgets.

01
Set a daily limit for the selected conversation.Actual Linqbase interface · demonstration project
TURN IDEAS INTO POSSIBILITIES

Put a boundary around daily work.

When limiting usage for a conversation, project or available daily allowance.

Unattended tasks need explicit spending or token limits. Daily budgets let you set boundaries per conversation, project or globally and pause when they are reached.

Choose a limit and review the reserve and restart behaviour. Pausing one billing route should not be confused with a provider subscription reset.

YOUR NEXT STEP

How to get started.

From your first choice to the result. Here is how to use this feature in your own project.

  1. 01

    Set the relevant daily budget and allocate available allowance across conversations where desired.

  2. 02

    Monitoring uses reported consumption. Token budget monitoring applies a reserve of 15,000 tokens.

  3. 03

    Choose whether paused work may resume automatically the following day when allowance is available.

IN PRACTICE

How it could work for you.

Allocate part of a daily budget to a design conversation and preserve the rest for tests.

How to assess the result

In-flight provider usage can arrive after a request begins. A configured limit is not an exact prepaid wallet.

GET STARTED IN LINQBASE

Where to find it.

Conversation / project → Budget settings; Usage & costs

Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.
SAVE & CONTINUE

What is saved?

Limits, usage and budget-pause reasons are saved.

GOOD TO KNOW

What you need to know

Provider usage may arrive late and an in-flight request can add consumption. This is not an absolute provider billing cap. A limit below the reserve leaves no space for new work.