For sellers
Prepare packets for buyers and agents.
Upload source material — Graunt Studio builds the packet with rights, provenance, and a manifest. You approve everything before it lists.
Three steps
-
Upload
Source material or an existing packet bundle.
-
Confirm rights and provenance
Rights basis, source record, freshness, known limitations.
-
List it
Preview the buyer-facing listing and list it. Publication checks run automatically; the same standards apply to every seller.
What could you list on Graunt?
Eight kinds of material buyers and agents pay for. Open one to see what it can look like.
Robotics training and demonstration media.
Recorded task executions an embodied-AI team can train on.
- Teleoperation and demonstration runs — multi-camera video with aligned joint, force, or IMU streams
- Annotated task segments: grasps, insertions, failures, recoveries — with timestamps
- Narrated assembly or repair walkthroughs, transcribed and step-aligned
- Simulation episode collections with scene and randomization metadata
Datasets and database exports.
Structured tables agents can load and query directly.
- Transaction, event, or sensor logs with documented columns and units
- Product, parts, and vendor catalogs; master tables and crosswalks
- Labeled training tables and time series with stated collection windows
Material and chemical properties databases.
Property tables that answer “what is the value” questions precisely.
- Alloy mechanical properties — yield, tensile, fatigue, creep — by temper and temperature
- Polymer and composite datasheets normalized into one queryable schema
- Chemical compatibility, solubility, viscosity, and thermal-property tables
- Coating, lubricant, and adhesive performance data by substrate and condition
Benchmarks and evaluation sets.
The material teams use to check that a model or agent actually works.
- Domain Q&A sets with gold answers and grading notes
- Matching and extraction test pairs — for example, purchase orders to invoices
- Rubric-scored writing or coding tasks; regression suites for agent workflows
Books, reports, and reference texts.
Long-form writing becomes far more useful once it is chunked, indexed, and citable.
- Technical handbooks and manuals with section-level structure and stable IDs
- Industry reports with their tables extracted alongside the prose
- Courseware, field guides, and back-catalog titles with clean chapter maps
Reference data and registries.
The what-maps-to-what and what-exists lists everyone needs.
- Code lists and identifier crosswalks — categories, regions, product schemes
- Standards and specification metadata: numbers, titles, revisions, statuses
- Equipment, facility, and organization registries with source citations
Laws, regulations, and public filings.
Public-source material earns its price through organization and freshness.
- Regulatory corpora by jurisdiction with effective dates and change history
- Agency guidance, dockets, and comment files — deduplicated and indexed
- Permit, license, and registration extracts refreshed on a stated cadence
Agent tools, workflows, and instruction packs.
Operational knowledge packaged so an agent can follow it.
- Repo instructions and coding-agent governance packs
- Step-decomposed SOPs and runbooks with inputs, outputs, and checks
- MCP server definitions and OpenAPI integration packets
What a listing needs
- Source files. A structured dataset (CSV, JSON, Parquet), a reference text bundle (TXT, MD, JSONL), an evaluation set, or a normalization / taxonomy / workflow packet.
- A description. What it is, who it is for, when to use it.
- Declared rights and provenance. License basis, source, date, version.
- A price.
Build & validate a packet · Seller and agent acceptance standards.
Pricing, payouts, and review
Free to list. Fees, payout setup status, taxes, refunds, and publication requirements are shown before a paid listing is submitted or published. Stripe handles payouts where payout setup is complete. When you list, Graunt's deterministic publication checks run automatically — eligible listings publish through the canonical publication gate; anything that needs a closer look routes to manual review.
The machine-readable schedule is published at /v1/meta/pricing; see also /pricing. How publication review works.
Raw uploads and drafts are never public — Graunt sells the evaluated packet, not your files. Compliance posture.