Delete targets

Deregisters one machine. Only its owner, or an org admin, may remove it; an unknown id, a cross-org id and a machine owned by someone else all answer the…

DELETE /v1/agent/targets/{id}

Agent → · All API references → · Get started →


Address	`https://api.hanzo.ai/v1/agent/targets/{id}`
Method	`DELETE`
Operation	`delete_agent_targets_by_id`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Deregisters one machine. Only its owner, or an org admin, may remove it; an unknown id, a cross-org id and a machine owned by someone else all answer the same not-found, so a probe learns nothing about what exists.

Request

1 field.

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the target to act on, from the path.

Response

Status	Body	Meaning
`200`	agent.targetDeleted	ok
`default`	problem-details	refused

200 body — 2 fields.

Field	In	Type	Always	Description
`deleted`	body	boolean	—	Deleted is true when the target was removed.
`id`	body	string	—	ID is the target that was removed.

Failure carries the platform error shape — see Errors.

Examples

hanzo agent targets rm <id>

import { Configuration, AgentApi } from 'hanzoai';

const api = new AgentApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteAgentTargetsById({ id: 'id' });

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = AgentApi(client).delete_agent_targets_by_id(id='id')

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

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

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

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

let result = agent_api::delete_agent_targets_by_id(&cfg, Default::default()).await?;

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

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

var result = new AgentApi(client).deleteAgentTargetsById();

The method above is the one at the current release of the document. [email protected] (npm) was 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 -X DELETE https://api.hanzo.ai/v1/agent/targets/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches agent through the agents tool, which names its 36 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_agent_conversations"
         }
       }
     }'

Agent API · All Hanzo APIs · Interactive reference

Request

Response

Examples

On this page