Marketplace
marketplace: 23 operations.
Also for this capability: API · CLI · MCP · SDKs
marketplace: 23 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | marketplace |
| Address | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | GET /v1/marketplace/seller · GET /v1/marketplace/shop · GET /v1/marketplace/shop/{id} |
| Product | marketplace |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
input | object | — | — | — | arguments for the chosen op |
op | string | yes | — | — | — |
tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "marketplace",
"arguments": {
"op": "list_marketplaces"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one MCP answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
marketplace dispatches to 23 operations. 3 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which describe resolves.
| Operation | Route | Product | Summary |
|---|---|---|---|
get_marketplace_seller | GET /v1/marketplace/seller | marketplace | Answers where the caller's org stands as a seller, in one read: its founders' identity verification (KYC) and legal entity (KYB), its tax form and whether it is certified and valid, its own sanctions screening — only what an org may see about itself — the payout wallet it proved, the TaxPrincipalCredentials signed for its agents, what it earned in the year from the economic events the rails stated, and the 1099s payers furnished it. |
get_marketplace_shop | GET /v1/marketplace/shop | marketplace | Searches every public listing of every kind — agents and personas to hire, apps, skills, MCP servers and tools — newest first, with facets by kind, category, price and rating, paged. |
get_marketplace_shop_by_id | GET /v1/marketplace/shop/{id} | marketplace | Reads one public listing as the shop shows it — its seller's public face, its reputation and the ways to buy it. |
The same capability over plain HTTP is in the marketplace API reference, on https://api.hanzo.ai.
All 120 tools · MCP · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.