List authored — GET /v1/tool/plugins/authored

Lists the plugins the caller's org BUILT, newest first, each with the TypeScript as authored.

GET /v1/tool/plugins/authored

Tool → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/tool/plugins/authored`
Method	`GET`
Operation	`get_tool_plugins_authored`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Lists the plugins the caller's org BUILT, newest first, each with the TypeScript as authored. That is a different set with a different lifecycle from GET /v1/tool/plugins, which reports the subsystems this deployment mounted. The bundled CommonJS the runtime executes is never included, and neither is any credential — a plugin names the connectors provider it needs and reads the credential from ctx.auth at run time.

Request

GET /v1/tool/plugins/authored takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	tool.authoredPluginList	ok
`default`	problem-details	refused

200 body — 7 fields.

Field	In	Type	Always	Description
`plugins`	body	tool.AuthoredPlugin[]	—	Plugins is every plugin this org built, newest first, each carrying the TypeScript as authored.
`plugins[].createdAt`	body	integer (int64)	—	CreatedAt is when the plugin was last built, Unix seconds.
`plugins[].id`	body	string	—	ID is the plugin's id within the org, and the id a delete addresses.
`plugins[].name`	body	string	—	Name is the plugin's name: one lowercase path segment, the id it runs by.
`plugins[].org`	body	string	—	Org is the org that built the plugin — the validated caller's.
`plugins[].provider`	body	string	—	Provider is the connectors provider whose credential this plugin uses at run time.
`plugins[].source`	body	string	—	Source is the TypeScript as authored (or as generated from a spec).

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo tool plugins authored list

.ts

.py

.go

.rs

.java

import { Configuration, ToolApi } from 'hanzoai';

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

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ToolApi(client).get_tool_plugins_authored()

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

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

use hanzo_client::apis::{configuration::Configuration, tool_api};

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

let result = tool_api::get_tool_plugins_authored(&cfg, Default::default()).await?;

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

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

var result = new ToolApi(client).getToolPluginsAuthored();

curl https://api.hanzo.ai/v1/tool/plugins/authored \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches tool through the tool tool, which names its 17 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_tools"
         }
       }
     }'

Tool API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList servers NextList plugins