cloud computes the catalog in Go and serves it at /v1/pricing, so the
docs apps and the zen-models package read the endpoint directly rather
than a host that forwards to it. The Base page links to the pricing page
a reader can actually open.
Co-authored-by: Hanzo Dev <[email protected]>
The placeholder was gated on `#app:empty` — but Scalar mounts as a SIBLING of
#app, so #app is empty forever and the loading message became a permanent
146px band pinned above the real reference on every visit, on both viewports.
The first thing a customer saw on our API reference was a load state that
never resolved.
Gated on `html.booting` instead, cleared by a MutationObserver on the first
rendered node with a load-event fallback — so it cannot outlive the load
regardless of where Scalar mounts.
Also: the file claimed 'no runtime CDN' while Scalar fetches fonts.scalar.com
(13 CSP-blocked requests per load, silently falling back off-brand). Comment
corrected to state the truth and Geist pinned so the reference matches docs.
Brand: 'LLM API gateway with all models' -> 'One API for every model';
'chat-completions proxy' -> 'chat completions'. Honesty: dropped the '$5 free
credit' line from base-docs pricing (that grant is disabled).
- Fix 6 wrong model prices in zen-docs pricing.mdx to match Go billing
controller (zen4-ultra, zen4-max, zen4-pro, zen4-coder-flash,
zen3-nano, zen3-guard)
- Fix zen-models compute tiers to match marketing (Nano $5 through
Power $49, not the old PaaS internal pricing)
- Fix platform AI model prices to include 1.2x third-party markup
(Claude Sonnet $3.60/$18, GPT-5 $1.50/$12, etc.)
- Update base-docs pricing to use marketing tiers matching
platform/visor ($5/$6/$12/$24/$36/$49 instead of PaaS $6-$384)
Replace hardcoded 3-tier pricing with dynamic fetch from
pricing.hanzo.ai/v1/pricing/cloud/plans. Shows all 6 canonical
PaaS compute tiers (Starter $6 through Enterprise $384) with
real vCPU/RAM/disk specs and hourly rates. Static fallback
ensures the page renders even when the API is unreachable.
New docs site for Hanzo Base following the monorepo docs framework pattern:
- Landing page with feature grid, quick start, and architecture highlights
- 9 documentation sections: getting-started, collections, auth, realtime,
file-storage, cloud-functions, SDK (JS + Go), and deployment
- K8s manifests for base.hanzo.ai (static docs) and api.base.hanzo.ai
(multi-tenant Base platform with IAM/KMS integration)
- Dockerfile with nginx for static export serving
- Monochrome Hanzo theme via neutral.css + Geist fonts
zeekayandHanzo Dev