Skip to main content
The buyer API is the HTTP surface for agents and scripts working on a buyer team: browse the published catalog, inspect quality evidence and taskset previews, and read your team’s purchases, bids, opportunities, wallet, and notifications. Buying, bidding, and paying stay in the web app. Base URL https://api.datavendor.ai, every route under /v2, authenticated with a team API key. Keys, conventions, and errors are shared with the vendor API and described on Using the API. The OpenAPI document behind this page is served with an interactive reference. A first call, returning the published catalog:

Objects

The same reads are available as MCP tools for coding agents.
Endpoint reference

Catalog

Buyer-facing reads over published listings from every team. Each listing carries the vendor organization’s team_name; bids and purchases never name the buyer to the vendor.

Browse

Browse is filtered and sorted server-side. The first page carries tab counts and filter facets; follow next_cursor for the rest. Tag and asset type values come from the taxonomy endpoints. Language, file extension, robotics format, and capability values come from the first page’s facets, which count every published listing (or every search match when query is set) regardless of the other filters. Price, sample price, price per task, and scale filters are min_/max_ pairs (for example min_price and max_price); send either bound or both, and both are inclusive. A sample price bound only matches listings that offer a sample. Asset count pairs bound how many assets of one type a listing includes: min_codebases/max_codebases, min_tasksets/max_tasksets (HUD tasksets and Harbor bundles together), min_environments/max_environments, min_robotics_datasets/max_robotics_datasets, and min_raw_data/max_raw_data. A listing without that type counts zero. rare_languages_only=true keeps listings whose codebases are at most 40% JavaScript, TypeScript, and Python combined, by language bytes; listings without a language byte breakdown never match.
Request
Response 200
Request
Response 200
Request
Response 200
Request
Response 200
Request
Response 200
Request
Response 200
Request
Response 200

Taxonomy

The vocabularies vendors classify with and buyers filter by. Pass the returned values into browse filters; an unknown value matches nothing rather than erroring.
Request
Response 200
Request
Response 200
Request
Response 200
Request
Response 200

Buying

The key-holding team’s own buyer history. Purchasing, bidding, and accepting offers stay in the web app.

Purchases and bids

Request
Response 200
Request
Response 200

Your opportunities

Listing requests your team posted, plus read-only project opportunity and bid history.
Request
Response 200
Request
Response 200
Request
Response 200
Request
Response 200
Request
Response 200

Account

Request
Response 200
Request
Response 200