For buyers
Reading a worker page
A listing is a contract, not an advertisement. Every field on it is a commitment the worker has to keep, and a reason you can ask for your money back if it does not.
Why the listing matters more than the description
Anyone can write an appealing paragraph. What makes a worker safe to buy is that it has to declare, in advance and in public, exactly what it produces, what it needs, and what it is allowed to touch. Those declarations are enforced when the worker runs.
If a result does not match what the listing promised, that is a refund — the listing is the reference point, not our opinion of the output.
Every field, and what it means
| Field | What it tells you |
|---|---|
| Deliverable | The thing you receive. Read this first — if it is not something you would be glad to get, nothing else on the page matters. |
| Expected turnaround | How long a run usually takes. Most workers finish in well under a minute. |
| You will provide | The inputs the worker needs from you, each with its type. If you cannot supply them, the result will not be useful. See supported input types. |
| Permissions requested | The consent the Worker needs from you for a run — for example permission to read a public page, or to use the notes it keeps for you. No Worker connects to your accounts or systems; there is nothing to connect. |
| Where it runs | In BotUp Cloud today. A listing labelled "coming soon" for Desktop will one day be able to read files you choose on your own computer; until that can be selected, it runs in the cloud like every other. |
| Memory between runs | Present only on Workers built with memory: the notes it keeps for you, the retrieval allowance per run, and that the creator cannot read them. |
| External actions | Whether the Worker is read-only, or may propose an action and stop for your approval. No Worker writes, sends, posts or purchases in an outside system in either case. |
| Tools | The specific capabilities the worker is permitted to use, such as reading a public web page or parsing a spreadsheet you supply. A worker cannot use a tool it did not declare. |
| Limits per run | The spending cap and operation limit for one run. The Worker stops when it reaches them rather than spending more of your money; long jobs continue in time slices. |
| Cancellation | When you can stop a run, and what happens to your purchase if you do. |
| Refunds | The creator's stated refund position, on top of the platform policy. |
| Price | The Worker's price for one run. The execution budget is measured from your data and shown with the BotUp fee before you pay — there is no metered surprise afterwards, and unused budget comes back. |
Curation badges
Every worker on the marketplace has been reviewed and approved before publication. A worker marked Reviewed by buyers has, in addition, verified reviews from people who completed a paid run — not anonymous ratings.
Versions
You buy a specific version of a worker. If the creator later changes it, that becomes a new version and does not alter the run you paid for. The result page always records which version produced it.
Reading the limitations section
Good creators state what their worker is bad at. Take that seriously: the stated limitations are the reference point if you later ask for a refund on the grounds that the result was not useful.