List subprocessors

Lists the third parties your organization sends data to, each naming what it is for.

GET /v1/trust/subprocessors

Addresshttps://api.hanzo.ai/v1/trust/subprocessors
MethodGET
Operationget_trust_subprocessors
AuthAuthorization: Bearer $HANZO_API_KEY

Lists the third parties your organization sends data to, each naming what it is for.

Request

GET /v1/trust/subprocessors takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200trust.subprocessorListok
defaultproblem-detailsrefused

200 body — 1 field.

FieldInTypeAlwaysDescription
subprocessorsbodyany[]—Subprocessors is the list, each naming at least what it is and what it is for — a name alone says nothing.

Failure carries the platform error shape — see Errors.

Examples

hanzo trust subprocessors
import { Configuration, TrustApi } from 'hanzoai';

const api = new TrustApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTrustSubprocessors();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TrustApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TrustApi(client).get_trust_subprocessors()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.TrustAPI.GetTrustSubprocessors(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, trust_api};

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

let result = trust_api::get_trust_subprocessors(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TrustApi;

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

var result = new TrustApi(client).getTrustSubprocessors();
curl https://api.hanzo.ai/v1/trust/subprocessors \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches trust through the trust 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_trusts"
         }
       }
     }'

Trust API · All Hanzo APIs · Interactive reference

Was this page useful?