Budget
Use this as a planning range before vendor quotes and sample review.
BOUNTY TEMPLATE
Create a compact, rights-cleared evaluation bundle for comparing VLA or robot foundation models on target tasks.
DIRECT ANSWER
This template is designed for model-evaluation buyers who need vendors to quote against specific capture, metadata, QA, rights, and delivery requirements.
Use this as a planning range before vendor quotes and sample review.
Assumes scoped capture, sample QA, and buyer-hosted delivery.
TEMPLATE RESEARCH PATHS
A bounty template should not be a standalone prompt. It should connect to source research, expected formats, budget estimation, baseline specs, and provider choices so the buyer can defend every field in the eventual request.
Before a team posts a template, it should compare public datasets, decide which fields are truly required, and specify how samples will be accepted or rejected. That turns the template from generic procurement copy into an auditable data contract.
The links below keep each template connected to the operational surfaces that make it useful: source discovery, cost estimation, format requirements, glossary definitions, and marketplace routing.
INTERNAL LINKS
Compare adjacent bounty patterns before committing to one capture plan, review cadence, or budget range.
Turn the template into a structured intake with modality, task, geography, rights, metadata, and QA fields.
Stress-test the planned hours, geography, exclusivity, and QA strictness before asking suppliers for quotes.
Use public datasets to calibrate what already exists, what is missing, and where custom data must be cleaner.
Convert the template from plain English into file, schema, manifest, and validation requirements.
Use the shared capture, delivery, consent, and quality baseline before writing template-specific overrides.
Map the bounty to the model behavior it should improve instead of only naming a data modality.
Decide whether the template needs a marketplace bounty, a managed service, or a specialist data partner.
EXTERNAL REFERENCES
Market context for why physical AI systems need custom, enriched, real-world data beyond generic labeling workflows.
Robotics dataset and tooling context for Hugging Face based collection, sharing, conversion, and training workflows.
A cross-embodiment robotics dataset reference for comparing trajectory scale, robot diversity, and VLA training assumptions.
A large in-the-wild robot manipulation dataset reference for real-world trajectory capture and deployment transfer risk.
USE THIS TEMPLATE
Use this scope as the starting point for a sourcing brief our team can review.