Uninstall deactivates one tool for the caller's own org and project, so it…
Uninstall deactivates one tool for the caller's own org and project, so it stops being dispatchable there.
POST /v1/marketplace/uninstall
| Address | https://api.hanzo.ai/v1/marketplace/uninstall |
| Method | POST |
| Operation | post_marketplace_uninstall |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Uninstall deactivates one tool for the caller's own org and project, so it stops being dispatchable there. It is the exact inverse of install and touches the same activation record; deactivating something that was never active is not an error. The listing itself is untouched — this withdraws the caller's use of a capability, not anyone's offer of it.
Request
1 field, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
tool | body | string | — | Tool is the registry name of the capability to activate (or deactivate) for the caller's own org and project. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | installState | ok |
200 body — 2 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
installed | body | boolean | — | Installed is its activation after the write. |
tool | body | string | — | Tool is the capability the write applied to. |
Failure carries the platform error shape — see Errors.
Examples
hanzo marketplace uninstallimport { Configuration, MarketplaceApi } from 'hanzoai';
const api = new MarketplaceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postMarketplaceUninstall({ 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_uninstall(tool="<tool>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.MarketplaceAPI.PostMarketplaceUninstall(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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_uninstall(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.MarketplaceApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new MarketplaceApi(client).postMarketplaceUninstall();curl -X POST https://api.hanzo.ai/v1/marketplace/uninstall \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tool": "<tool>"
}'The door reaches marketplace through the marketplace tool, which names its 6 operations with its own verbs — this one among them, under a name only the door 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": "get_marketplace"
}
}
}'How is this guide?