A Playbook is the first stage of a Service. While you are still building it, it is a Draft Service: yours, and runnable by nobody. Deploy turns that Draft Service into a private one you can run. After you have run it successfully through one of its Instances, Publish makes the same Service public on your storefront. Deploy always comes first; Publish is the separate decision to let other people use it.

Nothing is created at either step. It is one Service moving from draft, to private, to public.

Your storefront

Publishing starts from the private Service's Playbook settings (Publish tab, behind the header cog). Before your first publish, you claim the operator capability, a handle, in Settings → Account & Roles. It becomes your public address: yourhandle.askyamo.com. Your storefront lists every service you've published, under your name.

Listing a Playbook

The listing form asks for a title, a description of the outcome, and your price. YAMO also requires one successful Run from the current Playbook through this private Service, so the public page is backed by a real Outcome. A listing is priced per run, paid from the subscriber's wallet. Every listing is pay-per-run: one price, one run, one deliverable. Publishing is live immediately: no review queue. Unpublish whenever you like; the Playbook itself stays yours either way.

Price honestly and plainly: a subscriber pays the number you set, per run. Their receipt shows your price as one line: no meters, no token maths on their side.

What subscribers see

Your Service page shows its Outcome, description, and one Run Service call to action. Anyone can read the page. Running asks the person to sign in, pay or confirm the exact per-Run price, and then opens the Service conversation. The Instance asks for the Playbook's declared inputs one at a time and delivers the Outcome with a receipt.

Subscribers get your Playbook's work, not its internals: your references and your document stay yours.

Earnings

You earn on every run of your published services, proportional to real usage: successful services earn more, and a service nobody runs costs its subscribers nothing. The platform takes its cut from your earnings (the take rate). Your earnings and payouts are visible at Settings → Operator.

Agents can run services too

A listing can be marked agent-callable, which lets AI agents discover and run it over MCP, with the payer's explicit consent and spend caps on their side. The same service, a second kind of subscriber.