# Hanzo Console — Hanzo AI

> Track every LLM call across your stack. Monitor costs, latency, quality, and token usage.

platform.hanzo.ai

# Hanzo Console

One admin for everything you run

[Open Console](https://platform.hanzo.ai)[Documentation](https://docs.hanzo.ai/docs/console)

Console — Hanzo

[Chat](https://hanzo.ai/cloud/chat)[Bot](https://hanzo.ai/bot)[Search](https://hanzo.ai/search)[Crawl](https://hanzo.ai/crawl)[Studio](https://hanzo.ai/studio)[Console](https://hanzo.ai/console)[Referrals](https://hanzo.ai/cloud/referrals)[Marketplace](https://hanzo.ai/cloud/marketplace)

- gatewayReady
- payments-apiReady
- checkout-webBuilding
- docs-siteReady

Every request enters here, so the limiter does too.

[Open in the console](https://hanzo.ai/home)

Example project. Every name in it is one you would give your own.

Paste and ship

Paste this into any agent. It reads the skill manifest and calls Console from there.

Agent promptCopy

```
Read https://hanzo.ai/skill.md and use Hanzo Console in my project.
```

## A module per product, one shell around them

Add what you use. Hide what you don't. The shell stays the same.

01

### Providers and models

Every model your organization can call, and which provider serves it. Connect an account of your own and its models appear beside the ones we run.

02

### Usage and balance

A usage record per call and one balance per organization, so spend is attributed where it happened instead of totalled at the end of the month.

03

### Keys

Issue an API key, scope it, revoke it. The key you paste into a client is minted here, and revoking it here is what stops it working.

04

### Applications and stores

Register an app, hand it an identity, give it a store. The console writes the same resources the CLI does, because both are clients of the same API.

05

### Find it by typing it

A command palette reaches every module and every record without learning where anything lives. The sidebar is yours to reorder and prune.

06

### Scoped to the org on your token

Sign-in is OIDC against Hanzo IAM. What you see is what your organization owns, and switching organization switches the whole page — there is no global view to fall into by accident.

/v1One API behind it

OIDCSign in with Hanzo IAM

Per-orgData scoped to your org

OSSMIT or Apache-2.0

## The console is a client. So is your code.

Everything on these screens is a call to api.hanzo.ai/v1, and the typed clients are generated from the same document.

app.py

```
from hanzoai.cloud import ApiClient, Configuration, ChatApi # The key you issued in the console config = Configuration( host="https://api.hanzo.ai", access_token="sk-...", ) with ApiClient(config) as client: print(ChatApi(client).post_v1_chat_completions()) # The call, and what it cost, are on your # organization's usage before it returns.
```

Open source royalty

### 20% to the author of the code that runs

Verify that you own a repository, and every org that deploys a project built from it pays you 20% of its metered spend, accrued each period.

[How authors are paid](https://hanzo.ai/oss)[Our repositories](https://hanzo.ai/open-source)

## Open the console

Sign in with your Hanzo identity. The organization you land in is the one that gets billed, and everything on these screens belongs to it.

[Open Console](https://platform.hanzo.ai)[View on GitHub](https://github.com/hanzoai)

Related capabilities

[Console docs →](https://docs.hanzo.ai/docs/console)

[ChatConversational AI](https://hanzo.ai/cloud/chat)[BotMulti-agent platform](https://hanzo.ai/bot)[SearchRetrieval & answers](https://hanzo.ai/search)

## Get Console

Operator console for the cloud

License: Apache-2.0[hanzoai](https://github.com/hanzoai)

[Deploy to Cloud](https://platform.hanzo.ai/deploy)[Self-host](https://docs.hanzo.ai/docs/console)