Install
Every framework, language, and platform Hanzo installs into, with the line that starts the work.
Install
Hanzo goes into the stack you already have. Pick yours below and copy the line — an install command for a framework, a tag for a no-code platform, a base URL for an SDK you are already calling.
44 of 44. Anything not listed reaches the same endpoints over the HTTP API.
One key, one address
Whatever you install, it points at the same place: api.hanzo.ai, authenticated
with one key. That is why a project can start on a snippet and end up calling the
API from a server without changing accounts, keys, or hosts — the surface widens,
the credential does not.
Mint a key in the console, or see Getting Started for the five-minute path from nothing to a first call.
Nothing to install
Every endpoint an SDK reaches is reachable directly. A stack with no Hanzo package — or one you would rather not add a dependency to — uses the HTTP API and loses nothing but the typing.
Connecting, not installing
Installing puts Hanzo into your app. Connecting points Hanzo at a service you already run — GitHub, Slack, Google, or any MCP server. That is a different catalog: see MCP and connectors.
How is this guide?
Last updated on