Migrate
39 vendors, each mapped to the Hanzo capability that answers it — how to start, nouns, the call before and after, and what does not carry.
39 guides, one per vendor. Each one starts with the shortest path to a working call, names the capability that answers the vendor, maps their nouns onto ours, shows the same call both ways, and says plainly what you lose.
Every capability lives at one address — /v1/<name> — and the operation counts
below are read from the API document this site is built from.
Hosting and delivery
| From | What it does | Capability |
|---|---|---|
| Vercel | Building a repo and serving it on a domain | /v1/platform (37) · /v1/projects (27) |
| Netlify | Static hosting, builds, edge functions and forms | /v1/projects (27) · /v1/functions (11) |
| Render | Apps, cron and managed data stores | /v1/platform (37) · /v1/provisioning (28) |
| Fly.io | Machines placed in named regions | /v1/platform (37) · /v1/visor (34) |
| Heroku | Dynos, buildpacks, pipelines and add-ons | /v1/platform (37) · /v1/provisioning (28) |
Identity
| From | What it does | Capability |
|---|---|---|
| Auth0 | The identity provider your app redirects to | /v1/iam (159) |
| Clerk | Drop-in auth components, users, orgs and sessions | /v1/iam (159) · /v1/account (10) |
| WorkOS | SSO, SCIM directory sync and audit logs | /v1/iam (159) · /v1/audit (1) |
| Okta | Enterprise SSO, lifecycle provisioning and MFA | /v1/iam (159) · /v1/authz (3) |
Data and storage
| From | What it does | Capability |
|---|---|---|
| Supabase | Postgres with auth, storage, realtime and vectors | /v1/provisioning (28) · /v1/iam (159) |
| Firebase | Auth, documents, storage, functions and messaging | /v1/iam (159) · /v1/kv (6) |
| PlanetScale | A database with schema branches and deploy requests | /v1/provisioning (28) · /v1/git (44) |
| Upstash | Serverless Redis, Kafka, scheduling and vectors | /v1/kv (6) · /v1/mq (15) |
| Algolia | Search indexes with ranking, facets and typo tolerance | /v1/index (17) |
| Pinecone | Vector indexes, namespaces and metadata filters | /v1/index (17) · /v1/knowledge (9) |
Observability and product
| From | What it does | Capability |
|---|---|---|
| Datadog | Metrics, traces, logs, dashboards and monitors | /v1/o11y (381) · /v1/metrics (11) |
| Sentry | Error tracking, releases and performance | /v1/event (12) · /v1/o11y (381) |
| PostHog | Product analytics, flags, experiments and replay | /v1/event (12) · /v1/flags (8) |
| Grafana | Dashboards, logs, traces and alerting | /v1/o11y (381) · /v1/notify (4) |
| LaunchDarkly | Which users see which behaviour | /v1/flags (8) · /v1/experiment (7) |
Agents and inference
| From | What it does | Capability |
|---|---|---|
| OpenAI platform | Models, assistants and the platform around them | /v1/ai (272) · /v1/agents (37) |
| Replicate | Running a model under a name | /v1/ml (7) · /v1/ai (272) |
| Modal | Serverless GPU functions, sandboxes and jobs | /v1/functions (11) · /v1/sandbox (19) |
| LangSmith | LLM tracing, datasets and evaluations | /v1/o11y (381) · /v1/eval (16) |
| Composio | Authenticated third-party tools for agents | /v1/integrations (48) |
| E2B | Sandboxes for code an agent wrote | /v1/sandbox (19) · /v1/exec (4) |
| Tavily | Web search and page extraction for agents | /v1/websearch (6) · /v1/crawl (1) |
Messaging
| From | What it does | Capability |
|---|---|---|
| Amazon SQS | Queues between services | /v1/mq (15) · /v1/pubsub (2) |
| Twilio | Phone numbers, SMS and calls | /v1/tel (10) · /v1/channels (7) |
| AgentMail | Mailboxes an agent can send and read | /v1/notify (4) · /v1/channels (7) |
| ElevenLabs | Speech synthesis and transcription | /v1/audio (5) |
Money and business
| From | What it does | Capability |
|---|---|---|
| Stripe | Payments, subscriptions and invoices | /v1/commerce (181) · /v1/billing (45) |
| Lago | Metered billing and invoices | /v1/billing (45) · /v1/usage (11) |
| DocuSign | Legally binding signatures on a document | /v1/esign (13) · /v1/dataroom (26) |
| Carta | Who owns what in a company | /v1/captable (31) |
| GoDaddy | Buying and holding domains | /v1/domain (7) |
Secrets and automation
| From | What it does | Capability |
|---|---|---|
| HashiCorp Vault | Secrets, dynamic credentials and transit encryption | /v1/kms (5) |
| Doppler | Secrets, held for an org | /v1/kms (5) |
| Temporal | Durable workflows, retries and schedules | /v1/auto (17) · /v1/tasks (5) |
The key carries the tenant
Every call below authenticates with one header:
-H "Authorization: Bearer $HANZO_API_KEY"A secret key (sk-) resolves to a user; a publishable key (pk-) resolves to an
org. There is no org, user or project header to set — the gateway derives all
three from the validated key. Whatever your old vendor did with an account SID, a
workspace id, an entity or a project slug, here it is the key.
See API keys for how to mint one, and Errors for the shape every failure takes.
How is this guide?
Vercel AI SDK
createOpenAICompatible takes baseURL. Two other providers on the same parameter reach the responses and messages shapes.
Vercel
Vercel builds a repo and serves the result. Here that is two capabilities — /v1/platform (37) builds and runs an app, /v1/projects (27) serves a static export — and which one you want depends on whether your output needs a server.