> ## 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.

# Buyer MCP tools

> The read-only MCP tools a buyer team's coding agent can call.

The DataVendor MCP server lets an agent search the catalog, inspect a listing's quality evidence
and taskset previews, and check your buyer team's purchases, bids, and opportunities without
pasting IDs by hand. Connection, authentication, and limits are on
[Using the API](/overview/api#mcp). Discovery only: purchasing, bidding, and paying stay in the
web app.

## How tools chain

Discovery runs `list_browse_filters` → `browse_listings` → `get_listing` →
`get_listing_quality` or `preview_listing_taskset`. Recall history with `list_my_purchases` and
`list_my_offers`, and follow your requests with `list_my_opportunities`.

## Catalog

Published listings from every team. `get_listing` names the vendor organization that published the
listing; no tool names a buyer.

| Tool | Arguments | Returns |
| - | - | - |
| `list_browse_filters` | none | `domain_tags`, `asset_types`, and `content_tags`, each as `{ value, label }` pairs. Pass `value` into `browse_listings`. |
| `browse_listings` | `query`, `asset_types`, `domain_tags`, `max_price`, `verified_only`, `limit`, `cursor` | One page of listing summaries with `next_cursor` and `locked`. The catalog entrypoint when you have no listing id. |
| `get_listing` | `listing_id` | The buyer-facing record: title, summary, pricing lines, asset inventory, delivery and terms. Storage locations are withheld until purchase. |
| `get_listing_quality` | `listing_id` | `certified`, `certified_at`, environment-check counts, and the certifying run's check rows. |
| `preview_listing_taskset` | `listing_id`, `taskset_id` | The taskset summary plus the same first-page task preview a buyer sees in the web app. |
| `get_browse_access` | none | Whether the catalog is unlocked for your team and, for vendor-only teams, progress toward the browse gate. |

## Buyer team

The key-holding team's own buyer activity.

| Tool | Arguments | Returns |
| - | - | - |
| `list_my_purchases` | none | Completed purchases, newest first: kind (`full`, `sample`, `offer`), price, fee, total, and whether the listing detail is still available. |
| `list_my_offers` | none | Your team's bids across all listings, with status and decision time. |
| `list_my_opportunities` | `status` (optional) | Listing requests your team posted, with stage, deadline, and accepted asset types. |
| `list_opportunity_bids` | `opportunity_id` | Historical vendor bids on one of your retired project opportunities, from **Projects**: vendor team, task count, timeline, fixed and per-task pricing. |
| `get_my_wallet` | none | Your team's `credits_balance`. The `earnings` fields are zero unless your team also sells. |
| `list_notifications` | `limit` (default 20, max 100) | The notification feed with unread count. Marking read stays in the web app. |

The same reads are on the [buyer API](/buy/api/rest-api).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.