List features

Returns the supported feature flags and their resolved values for the caller's org.

GET /v1/o11y/features

O11y → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/o11y/features`
Method	`GET`
Operation	`get_o11y_features`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Returns the supported feature flags and their resolved values for the caller's org.

Callers need the viewer role; the runtime's own gate enforces it.

Request

GET /v1/o11y/features takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	o11y.O11yFeaturesOut	ok
`202`	Approval	held for approval
`default`	problem-details	refused

200 body — 10 fields.

Field	In	Type	Always	Description
`data`	body	o11y.O11yFeature[]	—	Data are the features.
`data[].defaultVariant`	body	string	—	DefaultVariant is the variant used when nothing overrides it.
`data[].description`	body	string	—	Description says what the flag gates.
`data[].kind`	body	string	—	Kind is the flag's value kind, e.g. boolean.
`data[].name`	body	string	—	Name is the flag's name.
`data[].resolvedValue`	body	any	—	ResolvedValue is the value resolved for the caller's org.
`data[].stage`	body	string	—	Stage is the flag's lifecycle stage, e.g. stable.
`data[].variants`	body	object	—	Variants are the flag's possible values, by variant name.
`data[].variants.*`	body	any	—
`status`	body	string	—	Status is "success".

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo o11y features

.ts

.py

.go

.rs

.java

import { Configuration, O11yApi } from 'hanzoai';

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

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = O11yApi(client).get_o11y_features()

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

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

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

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

let result = o11y_api::get_o11y_features(&cfg, Default::default()).await?;

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

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

var result = new O11yApi(client).getO11yFeatures();

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

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

O11y API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList views NextList keys — GET /v1/o11y/fields/keys