Fiund / Project pricing
Pricing follows the specification.
A useful quote for robotic datasets separates source fit, preparation work, permission review, and acceptance. Start with a brief so the scope can be discussed.
Project shapes
Choose the conversation your project needs.
For teams exploring what could fit.
Source review
Describe the use case and acceptable source characteristics. Discuss feasibility and the evidence needed to assess a proposed collection. A sourcing inquiry does not reserve inventory or commit either party to a transaction.
Scope a projectFor a bounded collection and acceptance brief.
Defined dataset project
Specify categories, volume units, formats, annotations, and review criteria. Separate source access from preparation work and identify assumptions that change the quote. Review scope and commercial terms before treating the project as agreed.
Scope a projectFor requirements that need a tailored sourcing plan.
Collection or ongoing scope
Discuss whether new capture or continuing sourcing is appropriate for the task. Define milestones, permissions, review stages, and change handling in the proposal. Feasibility and timing depend on the actual collection requirements.
Scope a projectQuote factors
The details that change the work.
Embodiment
Robot platform, end effector, controller, camera arrangement, and any compatibility constraints.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Signals
Required observations, state variables, action representation, units, coordinate frames, and timestamps.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Episodes
Task instructions, starts and stops, resets, success labels, and failed or partial attempts.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Transfer conditions
Object variation, environment changes, operator variation, and intended deployment differences.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Before agreeing a scope
Make the proposal reviewable.
Coverage and units
Define the count being priced, accepted output versus source volume, and any category-level minimums. Identify exclusions and limits of the proposed source.
Preparation and review
List file preparation, annotation, quality review, and correction work. Agree what evidence demonstrates acceptance and how exceptions will be handled.
Use and delivery
Document intended uses, restrictions, delivery format, review milestones, and commercial terms. Confirm each in the project agreement rather than inferring them from a website category.
Common questions
Before you source.
Is ordinary task video a robot trajectory dataset?
No. Video does not inherently contain robot state, joint values, end-effector commands, or control actions. If you require those signals, name them explicitly so sourcing can be evaluated against the right specification.
Can I inquire about a specific robot platform?
Yes. Include the platform, controller, sensors, action representation, and example schema. Availability and collection feasibility must be discussed before any platform-specific data is promised.
Should failed demonstrations be excluded?
That depends on your task. State whether you need successful demonstrations only, recoveries, negative examples, or a labeled mixture, and define how an outcome is judged.
Where are the per-hour or per-record rates?
No fixed public rate is quoted because source requirements and preparation work vary. Email the project brief to Jaeden for a discussion of scope and a project-specific proposal.