Creates the FIRST organization and its admin user.

POST /v1/o11y/register

O11y → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/o11y/register`
Method	`POST`
Operation	`post_o11y_register`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Creates the FIRST organization and its admin user. It is open by design — there is nobody to be signed in as yet — and refuses once setup has completed, after which new users arrive by invitation only.

Open by design; the runtime's own gate is OpenAccess.

Request

5 fields, body application/json (required).

Field	In	Type	Required	Description
`email`	body	string	yes	Email is the admin's email.
`name`	body	string	—	Name is the admin's display name.
`orgDisplayName`	body	string	—	OrgDisplayName is the organization's display name.
`orgName`	body	string	—	OrgName is the organization's name.
`password`	body	string	—	Password is the admin's password.

Response

Status	Body	Meaning
`200`	o11y.O11yRegisterOut	ok

200 body — 10 fields.

Field	In	Type	Always	Description
`data`	body	o11y.O11yUser	—
`data.createdAt`	body	string (date-time)	—	CreatedAt is when they joined.
`data.displayName`	body	string	—	DisplayName is what the console shows for them.
`data.email`	body	string	—	Email is their address.
`data.id`	body	string	—	ID is the user id.
`data.isRoot`	body	boolean	—	IsRoot marks the org's root user, which cannot be deleted or demoted.
`data.orgId`	body	string	—	OrgID is the org they belong to.
`data.status`	body	string	—	Status is their lifecycle state — active, pending_invite or deleted.
`data.updatedAt`	body	string (date-time)	—	UpdatedAt is when their record last changed.
`status`	body	string	—	Status is "success".

Failure carries the platform error shape — see Errors.

Examples

hanzo o11y register --email <email>

import { Configuration, O11yApi } from 'hanzoai';

const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postO11yRegister({ email: "<email>" });

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).post_o11y_register(email="<email>")

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

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

use hanzo_cloud::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::post_o11y_register(&cfg, Default::default()).await?;

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

ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));

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

curl -X POST https://api.hanzo.ai/v1/o11y/register \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "email": "<email>"
     }'

The door reaches o11y through the o11y tool, which names its 340 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": "get_o11y_alert_last"
         }
       }
     }'

O11y API · All Hanzo APIs · Interactive reference

Creates the FIRST organization and its admin user.

Request

Response

Examples

On this page