The whole Playbook
Every Play in it, in order, with the reference files it reads and the Connectors you have authorised.
Pay for the work, one run at a time
YAMO charges per run — one execution of a Playbook, from what starts it to what it delivers. There is nothing to pay for a Playbook that is sitting still.
Three things decide what a run costs
The unit is settled. The figures are being finalised and are not published on this page yet.
- 01
Whose Playbook it is
Running your own Playbook draws on your own balance. Running somebody else's published Service is bought at the price they set.
- 02
What the run actually did
Work is metered as it happens — the model calls a run made, and the operations it performed. Nothing is estimated after the fact.
- 03
Whether it delivered
A run that does not deliver is credited back to your YAMO balance. What you pay for is the artifact, not the attempt.
What you are paying for
The artifact it returns
The finished thing the Playbook publishes as its outcome, delivered the way its contract says it is delivered.
A run folder and a receipt
What was read, which Plays ran, and what each one produced — so a result can be traced back to the step that made it.
No markup on model usage
Model usage is passed through at what it cost. YAMO earns on the operations layer instead of on the tokens.
Common questions
What exactly is a run?
One execution of a Playbook, from what starts it to the artifact it returns. It is the unit YAMO meters and the unit you are charged for.
What happens if a run does not finish?
A run that does not deliver is credited back to your YAMO balance rather than charged. Delivery is the thing being paid for, so a failure is not a purchase.
What does it cost to publish a Service?
Publishing sets your own per-run price, and YAMO takes a share of each run somebody buys. The figures are being finalised and are not published on this page yet.
Where to go next
About
Who builds YAMO and why: a platform for the expert who has delivered the same outcome enough times to know the method and still does the work each time.Contact
How to reach YAMO: where to send a question about a Playbook, a Service you have published, a problem with your account, or anything about your data.Changelog
What has changed on YAMO, and when. Entries are added as work ships, so this page is the record of what happened rather than a summary written after.Privacy
How YAMO collects, uses, stores and protects your personal data, what happens to the services you connect, and the rights you hold over all of it.Terms
The terms and conditions for using YAMO: your account, acceptable use, intellectual property, liability, and how either side ends the agreement.Who it's for
The six kinds of expert YAMO is built for, and what changes when the method you already follow becomes a Service that somebody else can run.
Start here
Read a Playbook before you run one
Every template in the library publishes its contract and a real example output. Read one, then decide.