Your YAMO balance

Money on YAMO sits in a balance attached to your account, and runs draw against it. There is one balance, whether you are running your own work or buying somebody else's.

Topping up

You add to your balance through a card payment, with a five pound minimum. The prompt appears where it is needed: when a run you are about to confirm costs more than you have, the conversation says so and offers to top up rather than failing at you.

Paying for somebody else's Service

The price is taken when the run is admitted, before it is queued. If your balance will not cover it, the run never starts and nothing is written. You are told, rather than left with a run that fails later for a reason that turns out to be money.

If the run does not finish, the full price is credited back to your YAMO balance. Any ending that is not success does this: a failure, a deadline, a halt. It happens automatically, either the moment the run ends or shortly afterwards when the reconciliation catches it.

Two things that phrase means precisely. The money returns to your YAMO balance, not to your card: your original top up is untouched. And a run that succeeded but whose output you did not like is not this. That is a conversation with the operator, not an automatic credit, because otherwise no run is ever final.

Paying for your own runs

Your own runs are charged after they finish, on what they used, and the charge is allowed to take the balance below zero. That is deliberate: work that has already happened should be billed rather than blocked halfway through, and topping up settles it.

What you see

Every run has a receipt in its run folder. A run of your own Service is itemised, with the model line and the operations line kept separate. A run you bought shows the price you agreed. Usage across a period, with token counts and costs by Playbook, is in your account settings under Usage.

There is no separate balance page today. The balance is visible where it is about to be spent.