Docs

Developer docs

API reference and guides for the ZGo gateway — dual protocol (OpenAI / Anthropic), field reference, response shapes and billing.

Guides

Overview

ZGo is a model gateway compatible with both OpenAI and Anthropic. One key and one endpoint give you models from multiple upstreams.

What ZGo is

Only the unified ZGo interface is exposed; upstream sources stay invisible — swapping sources, adding channels or an outage never requires a code change.

Two protocols

Both protocols are served from the same host. Connect with whichever your client speaks:

# OpenAI side (most clients)
https://<your-domain>/v1

# Anthropic side (Claude Code, …)
https://<your-domain>

# ⚠ The two Base URLs differ: an Anthropic client that adds /v1 hits /v1/v1/messages → 404

Core capabilities

  • Chat completions: OpenAI `/v1/chat/completions` and Anthropic `/v1/messages`
  • Streaming (SSE) and tool calling
  • Vision input (standard `image_url`)
  • Long context and prompt caching (cached input is far cheaper)

Route stability

Routes are generally stable. When a single upstream hiccups, we de-weight and switch — instead of handing you the error.

Mechanics: channel health weighting; 3 consecutive failures trip a 60s breaker; recovery releases only 20% of traffic as a probe; plus switching to a backup channel within the retry budget.

Any route can fluctuate. What we deliver is automatic switching and fast recovery — not a promise of zero downtime.