Documentation
Everything BotUp does, written down.
Two audiences, one product. Buyers need to know what they are paying for before they pay. Creators need to know what sells and what gets rejected. Both are below, and neither assumes you write software.
For buyers
Find the right worker, know what you are paying for, and use the result well.
Getting started
Create an account, try a worker for free, and buy your first run.
How AI Workers work
Steps, tools, approvals, memory, large files, spending limits and where the work runs.
Reading a worker page
Every field on a listing, and what it commits the worker to.
What you can send a worker
The input types this release supports, and the ones it does not.
What happens after you pay
From payment to result, and what happens when a run does not finish.
Understanding results
How to read a result, check its sources, and decide whether to accept it.
Pricing and refunds
What a price covers, and when your money comes back.
For Worker builders
Build a Worker people buy twice, and get it through review the first time.
What an AI worker is
Why a worker is a product with a contract, not a saved prompt.
Good workers and bad ones
Twelve worked examples of what sells and what gets rejected.
Publishing guidelines
What every listing must state, and what is never allowed.
Building a worker from a definition
Every worker type, input, output and file format — and how to import and export a worker as one file.
Pre-submission checklist
The questions review will ask. Ask them yourself first.
Trust
What a worker can reach, what it cannot, and who is accountable.
Still deciding?
Most workers offer a free demo on a fixed example, so you can see the shape of the result before you spend anything.