Lists the skills the caller's org can reach — the brand's embedded catalogue…

Lists the skills the caller's org can reach — the brand's embedded catalogue plus the org's own authored ones — with each one's activation flag.

GET /v1/tools/skills

Tools → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/tools/skills`
Method	`GET`
Operation	`get_tools_skills`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Lists the skills the caller's org can reach — the brand's embedded catalogue plus the org's own authored ones — with each one's activation flag. A skill is discovery and activation metadata attached to an agent, never called directly, so every entry here is non-dispatchable. It is GET /v1/tools narrowed to one source, not a second store: a name a caller sees here is the same entry, with the same activation state, that discovery reports.

Request

1 field.

Field	In	Type	Required	Description
`activated`	query	string	—	Activated keeps only the tools activated for the caller's org and project, and only when it is exactly the string "true".

Response

Status	Body	Meaning
`200`	sourceToolList	ok

200 body — 12 fields.

Field	In	Type	Always	Description
`source`	body	string	—	Source is the source these tools came from.
`tools`	body	Tool[]	—	Tools is the caller's tools from that source.
`tools[].activated`	body	boolean	—	Activated is filled by the registry from the activation store for the requesting (org,project); providers leave it zero.
`tools[].description`	body	string	—	Description is the prose a model reads to decide whether to call the tool.
`tools[].dispatchable`	body	boolean	—	Dispatchable is whether the tool can be CALLED.
`tools[].inputSchema`	body	any	—	Schema is the JSON Schema of the call arguments — the MCP inputSchema.
`tools[].name`	body	string	—	Name is the tool's id in the flat, fleet-wide tool namespace — the value a tools/call passes.
`tools[].price`	body	Price	—
`tools[].price.amount`	body	any	—	Amount is what ONE call costs, EXACTLY: an 18-decimal USD value, so a per-call price of $0.0025 is$ 0.0025 and not a cent-floored zero.
`tools[].price.currency`	body	string	—	Currency is the ISO 4217 code, e.g.
`tools[].price.recipient`	body	string	—	Recipient is the payout wallet ref the marketplace seller is paid at.
`tools[].source`	body	string	—	Source is where the tool comes from: connector, function, zap-service, agent, skill or mcp.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

import { Configuration, ToolsApi } from 'hanzoai';

const api = new ToolsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getToolsSkills();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ToolsApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ToolsApi(client).get_tools_skills()

cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)

resp, _, err := client.ToolsAPI.GetToolsSkills(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_cloud::apis::{configuration::Configuration, tools_api};

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

let result = tools_api::get_tools_skills(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ToolsApi;

ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));

var result = new ToolsApi(client).getToolsSkills();

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

curl https://api.hanzo.ai/v1/tools/skills \
  -H "Authorization: Bearer $HANZO_API_KEY"

The door reaches tools through the tools tool, which names its 19 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": "list_mcp_servers"
         }
       }
     }'

Tools API · All Hanzo APIs · Interactive reference

Lists the skills the caller's org can reach — the brand's embedded catalogue…

Request

Response

Examples

On this page