> ## Documentation Index > Fetch the complete documentation index at: https://docs.datavendor.ai/llms.txt > Use this file to discover all available pages before exploring further. # How DataVendor works > Who is on the marketplace, how supply reaches buyers, and the rules every sale follows. ## Who is on the marketplace Organizations, not people. An organization holds a **vendor** role, a **buyer** role, or both, and everything it sells, buys, or earns belongs to it. Members work on the organization's behalf, and only team admins move money. See [Organizations and roles](/overview/organizations-and-roles). ## How supply reaches buyers There are two paths, and a vendor can use both. **Listings start with supply.** A vendor packages assets it already has into a listing, prices it, passes quality checks, and publishes it to the catalog. Buyers buy the whole listing, try a sample, or bid their own price. Start with [Create a listing](/sell/listings/create-a-listing) or [Browse and evaluate](/buy/browse-and-evaluate). **Opportunities start with demand.** A buyer posts a request with requirements and a submission deadline. DataVendor reviews it and decides which vendors see it. Tier 2 vendors answer by submitting listings, and the buyer buys through the same checkout as any listing. Start with [Post an opportunity](/buy/post-an-opportunity) or [Respond to opportunities](/sell/opportunities). ## The rules every sale follows ### Private supply only DataVendor is for data models have not already seen. Public repositories cannot be estimated, because models are often trained on public code already. Before a purchase, buyers see metadata, redacted file trees, quality evidence, and taskset previews, never the raw files. ### Vendors keep ownership A sale licenses your assets for a commercial use. The usual starting point is that you keep ownership and grant the rights that use needs; the exact rights depend on the agreement behind the listing. Submitting a listing confirms you own the supply and may license it. ### Buyers stay anonymous A listing shows buyers the vendor organization that published it, but the vendor never learns who bought, bid, or took a sample. A bid shows the vendor an amount and nothing else, and sales list only the listing, the kind of sale, and the amount. Delivery copies tasksets and environments into the buyer's team instead of sharing them from the vendor's, so nothing links the two teams. Opportunities work differently. Vendors see the buyer organization that posted a request unless the buyer posts it anonymously, and the buyer sees which vendor organization submitted each listing. ### Quality comes with evidence Mandatory checks gate publishing and cost nothing. A listing whose other checks, including the credit-priced recommended environment checks, also pass earns the **DV quality certified** verified badge, and buyers can read the verdicts behind it. Editing a listing removes the badge until the checks pass again. See [Quality checks](/sell/listings/quality-checks). ### Vendors set the price Price guidance while you list and codebase estimates are advisory. Neither blocks saving or submitting. Buyers who disagree with a price can [bid](/buy/bid-on-a-listing). ### Sales are final, and access lasts There are no refunds. A paid purchase grants an entitlement that survives the vendor editing or unpublishing the listing. See [Purchases and access](/buy/purchases-and-access). ### Earnings are free to keep on the platform DataVendor's 20% platform fee applies only when a vendor withdraws to a bank. Converting earnings to HUD credits is 1:1 and fee-free. See [Get paid](/sell/get-paid). ### Vendors are self-serve; buyers are invited A vendor organization can list as soon as setup finishes, and Tier 2 is a signature away. Buyer organizations join a waitlist, and DataVendor invites them at a managed pace. See [Become a vendor](/sell/become-a-vendor) and [Become a buyer](/buy/become-a-buyer). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.