BotUp

For buyers

What you can send a worker

Each worker declares the information it needs, and the form asks for exactly that. Here is everything a worker can ask for in this release — and, just as usefully, everything it cannot.

Supported input types

TypeWhat it is for
Short textA name, a market, a company, a single line of context.
Long textNotes, a transcript, a draft, a pasted document. This is the most common input and usually the one that decides how good your result is.
LinkA public web address the worker may read. It must be a public https page — a worker cannot open anything behind a login, and it cannot reach a private or internal address.
NumberA budget, a count, a threshold.
ChoiceA selection from options the creator defined, such as a tone or a region.
File uploadA text-based file the Worker reads as text — commonly .txt, .csv, .md or .json. Each listing states the formats and the size limit it accepts. A long file is read in bounded pieces rather than pasted whole into the model, so a full ledger or transcript is fine.

Not supported in this release

These are deliberate limits, not oversights. A worker cannot ask for them, so no listing can promise to handle them.

  • Scanned documents. A PDF or Word file is read by extracting its text. A scan — an image of a page with no text layer — has none to extract; type or paste the text instead.
  • Images, audio and video. No worker in this release accepts or produces them.
  • Pages behind a login. A worker can read a public web page. It has no credentials and cannot be given any.
  • Your accounts and files. No inbox, no calendar, no cloud drive, no CRM. There is nothing to connect and nothing to revoke.
A PDF report or a Word contract can be attached as it is; its text is extracted for the worker. Only a scan without a text layer needs the text copied out and pasted in.

How to give a worker a good input

The difference between a disappointing result and a useful one is almost always the input. Workers do not ask follow-up questions — they run once, on what you gave them.

  • Give the context you would give a competent freelancer on their first day, and no more.
  • Include the specifics that matter: names, numbers, dates, constraints.
  • Say what you already know, so the worker spends its effort on what you do not.
  • Do not paste secrets, passwords, API keys or payment details. No worker needs them, and none should ever ask.

What the worker does with your input

Your input is used to produce your result, and it is yours. It is not training data, and it is not shown to other buyers. The creator of a worker does not receive a copy of what you submitted.

Retention and deletion are covered in the privacy and retention policy, and you can export or delete your data from your account page at any time.

NextWhat happens after you payFrom payment to result, and what happens when a run does not finish.
What you can send a worker · BotUp