Your client asks where the data came from.From now on you can show them, instead of assuring them.
You post what is needed: arm, task, volume and what an hour pays. Publishing reserves the whole budget. Whoever joins records at their own place and keeps their own dataset. Billing is by the hour recorded, payout after you accept.
- 10 %
- Platform share, out of the hourly rate, no other fee
- After acceptance
- is when payout happens, not before
- Per contribution
- an account, a server timestamp, an authorship declaration
- anonymous
- neither your name nor your client's appears anywhere
Pick a part out of the bin and place it in the fixture
- Episodes collected
- 412
- Hours collected
- 20.6
- Missing until the pot is full
- 388
- Per hour
- Budget
- Exclusive
- Yes
- Client
- anonymous
You are not buying the data for yourself.
For people whose work is only finished once somebody else is satisfied.
A lab says: we are missing data. You say: I have to explain where it came from and what it cost. Consultancy, integrator, research service, procurement - what connects them is the position, not the industry: you price the work before anyone knows how hard the recording will be.
Which of these is you?
You defend every figure in a deck for a requirement you did not write.
You price a grip nobody has recorded yet, before the line is built.
You hand over something that survives a formal acceptance, not something that looks fine.
You file a supplier, a price and a record that an audit can follow.
Your client always asks the same three questions, and none of them is about volume. Volume can be bought; traceability and predictability cannot.
Walk through the process firstA Collection is a public request with a funded pot behind it.
Not a contract with one supplier, but a public task several people can work on at the same time.
You name two things: which robot arm the recordings must show, and the task in your own words. Volume, hourly pay and the credit behind it turn that into a job. Publishing reserves the whole budget - not spendable twice - and without cover the Collection does not appear.
Whoever collects keeps their own dataset; the datasets are linked to the Collection, not merged. A different arm has different joints and value ranges, so merging on upload would produce a dataset that reads fine and is wrong all the same. Assembly happens on download: every contribution on its own, plus one archive of everything you accepted.
- Two mandatory entries: robot arm and task description
- Attachments are optional: images, videos, documents
This is the sheet you put in front of your client
Set the three numbers you work with anyway and walk through it. Left your money, right what arrived.
Not a usable rate. The sheet keeps the last figure it could work with.
The rate is yours; this page publishes no range. The field starts on what the platform stores for a new operator.
Not the length of the recording: the time for one usable episode, discarded attempts included.
- Price per episode
- 0.75 EUR
- Actual cost per hour
- 15.00 EUR
- Rate you set
- 15.00 EUR
The form takes 1.00 EUR to 1000.00 EUR per hour - a brake against a typo, not a recommendation.
The amount sits in your account and does not expire. As long as no Collection runs, nothing happens.
Publishing binds the whole budget. It is not deducted, but you cannot spend it a second time.
Whoever joins takes a slot and an allowance at a fixed price. No money moves, and unused allowances fall back.
Checked at the door, measured on the server and charged. The amount reaches the collector, but locked. From here your review period runs.
With acceptance the amount becomes payable for the collector, and the episodes count towards the fill level.
On rejection the amount is clawed back, credited to you and falls back into the budget of this Collection. The collector keeps their dataset.
Whatever is left of the budget goes back into your credit. The Collection stays visible, marked as closed.
Your money
- Credit
- 600.00 EUR
- Of that reserved
- 0.00 EUR
- Spent
- 0.00 EUR
- Refunded
- 0.00 EUR
Budget for this Collection600.00 EUR
Your Collection
Progress
0 of 800 episodes
0 hours collected
- Review period running
What you can tell your client now
- Cost
- Nothing. Money lying ready carries no fee.
- Nothing spent, everything bound. Whoever sees the tile sees funded work.
- Unchanged. A slot costs nothing, neither you nor them.
- Charged and locked for the collector, nothing paid out. The figure comes from the delivered file, not a stopwatch.
- Final: a booking with a timestamp, an amount and a reference. Items like these make a breakdown, not a sum.
- Zero for this contribution. The refund stands as a line of its own.
- Final, and broken down per contribution.
- Origin
- None yet, there is no contribution.
- None yet, there is no contribution.
- No recording yet, but it is fixed which account holds which allowance.
- An account, a server timestamp and an authorship declaration with its text version.
- Complete, with account, timestamp and declaration. No collective item saying "from various sources".
- None, because the recording does not become part of your Collection.
- Complete per contribution, and kept. You can pass it on without anybody learning your name.
The paragraph you put in your quote
800 episodes, around 40 hours of recorded material. Budget 600.00 EUR, reserved in full the moment the request goes public. Of that, 536.00 EUR reaches the collectors and 64.00 EUR is the platform share of 10 percent, taken out of the hourly rate, not added on top. Each contribution is charged on arrival and paid out only after we accept it; a rejected one falls back into the budget. Whatever is left comes back when the request is closed.
Copied to your clipboard
Written from the three numbers above, with the same functions that do the billing. It stays in your browser.
The price per episode is rounded to whole cents, so the actual hour sits a few cents off the rate you set. Both stand above.
Posting costs nothing, and a small pot is a cheap trial: if nobody collects, the budget comes back.
See open collectionsAt any point your money sits in exactly one pot.
Free, reserved, charged, paid out. Whoever keeps those four apart answers every question about money without looking anything up.
Where is your money right now?
What it is
Yours, in your account, tied to nothing, and it does not expire. No minimum volume, no setup fee, no remaining term.
Still your credit, and it does not drop - but the reserved part cannot go anywhere else.
Debited from you, credited to the collector as locked. A reservation alone would not protect them: the work is delivered, so the amount leaves the payer.
The collector's, and payable. One booking per contribution, with a timestamp, an amount and a reference.
Clawed back and credited to you - into the budget of this Collection, not into free credit, so a Collection does not quietly shrink with every rejection.
What moves it out
Publishing a Collection binds it. Without cover the Collection does not appear at all.
An arriving contribution takes its share out. Close the Collection and the rest comes back.
Your acceptance makes it payable, your rejection sends it back. A lapsed review period counts as acceptance, with only the machine check behind it.
Nothing. This is the end of the path, and the only step you cannot undo.
The place stands open again, and the collector keeps their dataset.
The platform share of 10 percent on paid contract work comes out of the hourly rate instead of on top. A dataset sold in the marketplace carries 10 percent.
What you may promise, and what you may not
Six sentences of the kind you would write into a quote. Tap one to see whether the platform covers it.
Recorded on submission with the timestamp, the account, the version of the declaration text and the sender address. Part of the process, not a tick box.
The declaration is an assurance by the collector, not a test. It shifts the burden of proof; it does not prove the recording came out of the camera it names.
Say this instead
Every contribution comes with a named declaration by its author, with a timestamp and an account.
Every archive runs the same eleven checks as a marketplace listing: unpacking, episode count, frame rate, cameras, arm type. That says the file is consistent with itself, no more.
Put that way it is wrong, and the difference shows at the first statement. Charging happens on arrival; only the payout waits for your acceptance.
Say this instead
No contribution is paid out that we have not accepted, and we pay nothing for rejected contributions.
Only if you ticked exclusivity when you created the Collection. Then the sales route is blocked, not merely forbidden. Without the tick the collector may list their dataset.
Say this instead
The Collection is posted as exclusive, and the block applies from acceptance onwards.
The fill level shows where you stand, not when you arrive. How fast it goes depends on how many people with the required arm want the task.
Say this instead
We can name the status at any time, in episodes, hours and money.
You see everything. Nobody sees you.
The client behind a Collection is never named. For a service provider that is not a detail; it is what protects the relationship with their customer.
On the tile, in the detail view and in the public interface there is no name, no account, no country and no logo - not even as a field the page merely hides. If the client were visible, every collector could approach them directly. Anonymity here is the condition under which you can use the tool at all.
Two places are yours to watch: the description box is your text, so no company name in it - yours or your client's. Attachment metadata is cleaned on upload, but a letterhead in an image stays a letterhead.
Look at the tile as:
- Task, attachments, progress, rate per hour
- yes
- yes
- yes
- Your name or account
- only yourself
- no
- no
- The individual contributions
- all of them
- only their own
- no
- What the collectors earn
- the amounts you pay
- only their own
- no
- Who else is collecting
- the number
- no
- the number
Whether collectors are visible to each other by name is not decided yet. Until it is, the careful reading applies: they are not.
We are a tool for you and a competitor to you. Both are true.
Two things that do not read well for us. They stand here and not in the small print.
Our page for labs says that commissioning a data vendor means a quote, a contract, prepayment and waiting. What is meant there is the procedure, not the profession: somebody pays before a single recording exists, and provenance cannot be checked after delivery. We are not against the trade. We are against the old procedure.
Whoever procures data and passes it on sits in that same procedure one step further up: it costs a lab waiting time and it costs you margin. Posting turns the order around - budget fixed beforehand, provenance per contribution, ordering more means topping up credit. A vendor, too, can use it.
On the same platform where you post, we sell finished datasets and offer managed data packages of our own. For some enquiries that is an offer standing next to yours, and your client can open the marketplace themselves. There is no partner programme and no assurance that we will not take an enquiry ourselves.
What protects your customer relationship is not a promise: there is no field for who you are procuring for, and the collectors do not see you. And buying was never your service. Yours is turning a vague description into a task somebody can record, judging whether a recording is good, and handing the result over.
Every question your client asks has two answers
Pick what they ask. Left the usual route through a single supplier, right what posting here answers.
Through a single supplier
An assurance in the contract, which you pass on unchecked.
Prepayment or payment terms, both unrelated to the volume delivered.
A date that hangs on one supplier's workload. You hear about a delay afterwards.
It arrives as a whole, after weeks, and you see it once it is paid for.
New contract, new negotiation, new waiting time.
Remaining term and notice period, often a minimum order.
Posting a collection here
Per contribution an account, a server timestamp and an authorship declaration.
One booking per contribution, measured from the delivered file, and the rest comes back.
No date. A fill level in episodes, hours and money that you can read any day.
You see every contribution before accepting. A rejected one is clawed back and never enters your archive.
Top up credit, the same request keeps running.
Close the Collection; the reserved budget falls back into your credit.
And these hold regardless of the question
- Billing unit
- Hours of recorded material, measured from the file
- Format
- LeRobot v2.1, cameras given by role
- Exclusivity
- A tick box, fixed from the first contribution
The left column describes a procedure, not a company and not a profession.
Frequently asked questions
Only if you tell them. The Collection names no client, and the accepted contributions sit in your account. The entries per contribution are complete enough to pass on.
Any number of Collections side by side, each with its own budget and its own billing. They sit in one account: separate client areas do not exist today. Tell us before you start if you need that.
The budget stays reserved, and you can sharpen the Collection, pause it or close it; on closing it falls back into your credit. If it happens repeatedly, the task is described too narrowly, or the rate sits below comparable Collections.
You reject it, entirely or per episode, with a reason from a fixed list and a text alongside, and the collector sees both. Rejected recordings never enter your archive. Give proper reasons: a request's reputation comes from how its client handles contributions.
Every accepted contribution on its own, downloadable individually, plus one archive of all of them in the LeRobot format. Before it is built you see what goes in, what stays out and why.
You have read how it works. Here is where you use it.
Looking around costs nothing and needs no account. Only the form does.
List a data request
Every open Collection is public, so you can read a live request before writing your own. While that route is being switched on, we set the first one up with you.
See open collectionsBuy a dataset
Sometimes the material has already been recorded, and buying beats commissioning it again. Filtering by arm, task and volume is open to anyone.
Browse the marketplaceCreate an account
Registering and signing in sit on the same page, and you choose your role there. As a buyer you want the company side.
RegisterThe next enquiry comes with the same question.
A Collection you post today collects while you work on something else. When your client asks where the data came from, you open a breakdown.