docs: /v1/decisions is live on api.hanzo.ai, serving kai (stage a5) and Jev.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
2026-09-27 18:35:13 -07:00
co-authored by Hanzo Dev
parent 11c1cc3e4c
commit 235a0c7d87
3 changed files with 3 additions and 8 deletions
-5
View File
@@ -19,11 +19,6 @@ POST https://api.hanzo.ai/v1/decisions
The wire is OpenRouter's Decisions API. A client written for Jev works
unchanged: set its base URL to `https://api.hanzo.ai/v1` and send a Hanzo key.
<Callout>
The route is being added to the gateway. Until that release is live,
`api.hanzo.ai` answers `404` on this path.
</Callout>
## Request
```bash
@@ -18,8 +18,8 @@ and your policy keeps the last word.
**Kai runtime**: `POST /v1/decisions` is served by the decision runtime,
`decision serve`, which listens on `127.0.0.1:8080` by default; the public
route is [`api.hanzo.ai/v1/decisions`](/docs/decisions), being added to the
gateway. The decision responses quoted in these recipes are real, from that
route is [`api.hanzo.ai/v1/decisions`](/docs/decisions), the same runtime behind
a Hanzo key. The decision responses quoted in these recipes are real, from that
runtime serving `kai` (stage a5).
```bash
+1 -1
View File
@@ -85,7 +85,7 @@ questions to billing. Suites, deduplication and scores:
| Part | Status |
|---|---|
| **Kai**, the model (`hanzoai/kai`, one checkpoint line, a revision per training stage) | stage a5 measured above; weights not published |
| **Endpoint**: `POST https://api.hanzo.ai/v1/decisions`, serving `kai` and Jev | being added to the gateway; see [Decisions](/docs/decisions) |
| **Endpoint**: `POST https://api.hanzo.ai/v1/decisions`, serving `kai` and Jev | live: `kai` is stage a5 (calibration `cal_47711d44267fdbdd`), served from Hanzo's own infrastructure; see [Decisions](/docs/decisions) |
| **Decision Programs, Packages, policy gates** | landed, as a library |
| **Programs on the wire** (`"program": "agent.preflight@1"`) | specified in HIP-1332 §17; not served |
| **Kai inside Enso** | in progress; the agent programs are written, each set to `shadow` or `advisory`, and not yet wired into Enso |