Hanzo
Migrate

Migrate

Fifteen vendors, each mapped to the Hanzo capability that answers it — nouns, the call before and after, and what does not carry.

Fifteen guides, one per vendor. Each names the capability that answers it, maps the vendor's 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.

FromWhat it doesCapability
ComposioAuthenticated third-party tools for agents/v1/integrations (40) · /v1/connectors (8)
E2BSandboxes for code an agent wrote/v1/sandboxes (19) · /v1/exec (2)
Amazon SQSQueues between services/v1/mq (15) · /v1/pubsub (8)
TwilioPhone numbers, SMS and calls/v1/tel (10) · /v1/channels (7) · /v1/notify (4)
AgentMailMailboxes an agent can send and read/v1/notify (4) · /v1/channels (7)
ElevenLabsSpeech synthesis and transcription/v1/audio (5)
TavilyWeb search and page extraction for agents/v1/websearch (6) · /v1/crawl (1) · /v1/scrape (1)
GoDaddyBuying and holding domains/v1/domain (7)
DopplerSecrets, held for an org/v1/kms (5)
LagoMetered billing and invoices/v1/billing (45) · /v1/usage (11) · /v1/pricing (25)

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?

On this page