Skip to main content
YAMOYAMO

Listing a Service

Claiming your Front Office address, what the listing form asks for, and the one gate that surprises people: a real run has to have happened first.

In PublishUpdated
Contents

On this page

  1. 01Before your first publish
  2. 02What the listing asks for
  3. 03The gate
  4. 04What a buyer sees
  5. 05Unpublishing

Publishing changes who is allowed to run a Service you already have. It does not create one, and it does not copy your Playbook. The same object that was a Draft Service, then a private one, becomes public.

Before your first publish

You claim the operator capability and a handle in your account settings, under Account and Roles. The handle becomes your public address: yourhandle.askyamo.com. Your public Front Office lives there and lists everything you have published, under your name.

Publishing does not require payment setup. That matters for getting a first Service live, and it does mean money cannot reach you until you have done it. See Earnings and payouts.

What the listing asks for

The publish form sits in your Playbook's settings, on its Publish tab.

  • A Service name, and a short outcome summary: the promise in one line.
  • A description of what a buyer receives.
  • A category.
  • A price per run, in pounds. See Pricing.
  • An icon or hero image, optionally.
  • A privacy confirmation, which is not a formality: it is you agreeing that a confirmed runner shares their name and email address with your business, and understanding that their answers, files, connections and finished work stay private from you.

The gate

Publishing is not review by a person. It is a set of conditions checked in code, and it is immediate once they are met.

  • The setup checklist is clear, exactly as it is for Deploy.
  • You hold the operator capability and a handle.
  • One successful run has happened through an Instance of the private Service, and it ran the Playbook as it currently stands.

That third one catches people out, so it is worth being precise. A run you made while building does not count. It has to be a real run through the Service, and its finished artifact becomes the sample outcome your public page shows. So a published page is always backed by a piece of work that actually happened.

What a buyer sees

Your Service page carries the outcome, the description, what they will need to supply, the sample outcome from that qualifying run, the price, and one line saying exactly what gets shared with you. Anyone can read it. Running it asks them to sign in and confirm the price first.

Your Playbook itself is not on that page. A buyer receives the work, not the method.

Unpublishing

There is no unpublish action today. A published Service stays published. If that matters to you, decide before you publish rather than after.

Keep reading

More in Publish

Keep reading

Related

See it working

Open a Playbook that does this

Every template in the library publishes its contract and a real example output.