Returns the per-use price of every metered tool — web search, code interpreter,…
Returns the per-use price of every metered tool — web search, code interpreter, image generation, speech — each with the unit it is billed in.
GET /v1/plan/tools
| Address | https://api.hanzo.ai/v1/plan/tools |
| Method | GET |
| Operation | get_plan_tools |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns the per-use price of every metered tool — web search, code interpreter, image generation, speech — each with the unit it is billed in.
Request
GET /v1/plan/tools takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | planToolList | ok |
200 body — 1 field.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
tools | body | any[] | — | Tools are the metered tools, each an opaque object exactly as the catalog emits it — typically name, billing unit and price. |
Failure carries the platform error shape — see Errors.
Examples
hanzo plans toolsimport { Configuration, PlanApi } from 'hanzoai';
const api = new PlanApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getPlanTools();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import PlanApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = PlanApi(client).get_plan_tools()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.PlanAPI.GetPlanTools(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, plan_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = plan_api::get_plan_tools(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.PlanApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new PlanApi(client).getPlanTools();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/plan/tools \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches plan through the plan tool, which names its 15 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_plans"
}
}
}'How is this guide?