# Models: Every model behind one endpoint and one key — Hanzo AI

> Every model behind one endpoint and one key.

Hanzo OS

# Models

Every model behind one endpoint and one key.

Send a request to api.hanzo.ai and name a model. The same request reaches Enso, Zen or a model another lab serves, in the wire format your client already speaks — OpenAI chat completions and responses, or Anthropic messages.

## API

Operations on api.hanzo.ai. One key reaches every layer.

Method

Path

What it does

`GET`

`/v1/models`

Returns the models the routing table serves.

`POST`

`/v1/chat/completions`

The OpenAI-compatible chat completions API.

`POST`

`/v1/responses`

The OpenAI-compatible responses API.

`POST`

`/v1/messages`

The Anthropic Messages API.

`POST`

`/v1/embeddings`

OpenAI-compatible embeddings.

## Try it

```
curl https://api.hanzo.ai/v1/chat/completions \ -H "Authorization: Bearer $HANZO_API_KEY" \ -H "Content-Type: application/json" \ -d &#x27;{"model": "zen5", "messages": [{"role": "user", "content": "Hello"}]}&#x27;
```

## Docs

[Models](https://docs.hanzo.ai/docs/models)[Chat completions](https://docs.hanzo.ai/docs/openapi/ai/post-chat-completions)

## On this site

[Model catalog](https://hanzo.ai/models)[Enso](https://hanzo.ai/enso)[Zen](https://hanzo.ai/zen)[One API](https://hanzo.ai/llm)[Engine](https://hanzo.ai/engine)[Gateway](https://hanzo.ai/gateway)[Guard](https://hanzo.ai/guard)[Jin](https://hanzo.ai/jin)

## The stack

- CompanyThe legal body: formation, cap table, documents and filings, as operations.
- AgentsWorkers the company keeps: a model, instructions, tools and a budget.
- ModelsEvery model behind one endpoint and one key.
- MemoryWhat the company knows, and when it knew it.
- IdentityWho is acting — a person, a program or an agent — and what it may reach.
- MachinesReal computers, leased by the org, for agents and for the software they ship.

[RecordEvery act on every layer, by a person or an agent, in one trail.](https://hanzo.ai/products/record)
