Skip to main content
An estimation tells you what a codebase might be worth as AI training supply before you commit to a listing. Nothing is published and no buyer sees it. Everyone on your team sees every estimation the team makes.
1

Open the estimator

Go to Estimations and choose Estimate, then Codebases.
2

Connect a forge

Connect GitHub, GitLab, or Bitbucket and grant access to the repositories you want valued. You control the grant on the forge’s side and can change it any time.
3

Pick your repositories

Select up to 100 repositories. Each one becomes its own estimation and shows its progress inline. Public repositories cannot be estimated: models are often already trained on publicly available code.
4

Read your estimate

DataVendor archives each repository’s source and history, analyzes them, and returns an advisory value band dated when it was priced. If DataVendor cannot confirm a repository’s visibility, the estimation is marked as not priced.
An estimate is a dated receipt and never updates: estimate the repository again for a newer quote. The Inventory column shows whether each repository is already in your inventory, and Add to inventory imports one that is not.

​
Estimate from inventory

The inventory table, an asset’s page, and each asset in a listing you compose show the latest estimation of each codebase asset’s data, wherever it was made. Estimate or Re-estimate prices the asset from the analysis already run on its data, so it is available once that analysis finishes. A quote older than 90 days shows a warning suggesting you re-estimate.
An estimate is not a listing. Nothing is published or shown to buyers. The valuation is advisory, like price guidance.

​
Next

Inventory is where the codebases you could sell live until you list them.