Credits: check, top up, bring your own key, budget a project

Step by step — read the balance and history, buy a pack or subscribe, connect a provider key to stop metering, and give a project its own ceiling.

1. Read the balance

/credits: the balance, a low-balance warning, and the history — every line says what was done (which model, how many tokens, which email send, which storage day) and what it cost. The rate card at the bottom is what you are charged.

2. Top up

/credits?buy lists credit packs. Buying one goes through the store's checkout; credits land when the order is paid. A subscription plan with a monthly allowance grants it each period.

3. Bring your own key

/integrations → the provider (Anthropic, OpenAI, ElevenLabs, Runway…) → paste the key. From then on calls to that provider are yours and are not metered. Keys are encrypted and never shown again; delete the integration to stop using it.

4. Budget a project

On a project's dashboard, Budget → set a ceiling. Credits move from the org wallet into the project's own; everything its agents and creator jobs spend comes from there and stops at the ceiling. Top up adds more; Release returns the remainder to the org. The budget page shows spend by task.

5. When something pauses

An agent run, a creator job or a newsletter that would overdraw pauses in place and says so. Top up (or connect a key) and it resumes; nothing is charged that was not delivered.

For site owners

/treasury issues and tracks credits on your site; /models shows the models available and their rates.