Files
zooqueenandHanzo Dev cfc662b3d9 Verify the edge proxy against the live gateway
The Hanzo cloud is back — iam, kms and cloud.hanzo.ai all answer again, and
api.hanzo.ai is serving 26 models including zen and zen-free. So the proxy
was pointed at the real thing rather than a stand-in.

It works. A preflight from zoolabs.io answers 204 with the origin echoed. A
GET for /v1/models goes through and comes back with all 26. A chat request
reaches the gateway and the gateway's own 402 — a billable tenant is
required — arrives intact, with the CORS headers a browser needs, rather
than being swallowed. Everything on the path is proven except the
credential.

api.hanzo.ai still sends no Access-Control-Allow-Origin of its own, checked
again just now, so the proxy is still what makes a static site able to call
it at all.

Also: the suite pointed at whatever was listening on 4996, which made it
pass or fail on what else happened to be open. It starts its own gateway on
a free port now, so seven green means seven green.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-02 23:59:16 -07:00

15 lines
268 B
JSON

{
"name": "@zooai/cloud-edge",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "wrangler dev",
"deploy": "wrangler deploy",
"test": "node --test src/*.test.ts"
},
"devDependencies": {
"wrangler": "^4.0.0"
},
"type": "module"
}