Create install

Activates one tool for the caller's own org and project.

POST /v1/marketplace/install

Addresshttps://api.hanzo.ai/v1/marketplace/install
MethodPOST
Operationpost_marketplace_install
AuthAuthorization: Bearer $HANZO_API_KEY

Activates one tool for the caller's own org and project. A marketplace install IS the tool plane's activation write — one store, one truth — so an installed capability is immediately dispatchable and a monetized one is priced from its listing at every call. The tool must resolve in the caller's scope, so installing something that does not exist is refused rather than recorded.

Request

1 field, body application/json (required).

FieldInTypeRequiredDescription
toolbodystring—Tool is the registry name of the capability to activate (or deactivate) for the caller's own org and project.

Response

StatusBodyMeaning
200marketplace.installStateok
defaultproblem-detailsrefused

200 body — 2 fields.

FieldInTypeAlwaysDescription
installedbodyboolean—Installed is its activation after the write.
toolbodystring—Tool is the capability the write applied to.

Failure carries the platform error shape — see Errors.

Examples

hanzo marketplace install
import { Configuration, MarketplaceApi } from 'hanzoai';

const api = new MarketplaceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postMarketplaceInstall({ tool: "<tool>" });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import MarketplaceApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = MarketplaceApi(client).post_marketplace_install(tool="<tool>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.MarketplaceAPI.PostMarketplaceInstall(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, marketplace_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = marketplace_api::post_marketplace_install(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.MarketplaceApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new MarketplaceApi(client).postMarketplaceInstall();
curl -X POST https://api.hanzo.ai/v1/marketplace/install \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "tool": "<tool>"
     }'

MCP reaches marketplace through the marketplace tool, which names its 23 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_marketplaces"
         }
       }
     }'

Marketplace API · All Hanzo APIs · Interactive reference

Was this page useful?