Introduction

Chat, Anthropic Messages, and image routes behind one Zashmodel key—with setup guides for the tools you already run.

One Zashmodel API key reaches OpenAI-compatible Chat Completions and Responses, Anthropic Messages, and the image routes enabled for your account. Coding-tool walkthroughs live in the same docs set.

Zashmodel is a unified model gateway: apps and agents keep a stable contract while routing, keys, and request logs sit behind it. Create keys and top up in the console; live model availability and pricing stay on the main site—not in a second docs catalog.

Land your first request

  1. Issue a key for the right group

    In the console, open API Keys and create a key under a group that includes the models you need. Quotas, expiry, and IP rules are per key.

    API Keys →
  2. Aim your client at this host

    Keep your existing SDK or curl flow. Change only the base URL and credential to Zashmodel values.

    OpenAI SDK and Codex base URLhttps://zashmodel.com/v1
    Claude Code base URLhttps://zashmodel.com

    Claude Code adds /v1/messages automatically. When sending a raw HTTP request, include /v1 exactly once in the full URL.

    Authenticate with your Zashmodel key. Do not mix hostnames or credentials from another relay.

  3. Match the protocol to the job

    Chat Completions, Responses, Anthropic Messages, and Images are separate contracts. Pick the one your client expects, then confirm the serving route and cost in request logs.

    API requests →

What the gateway already covers

Drop-in OpenAI-compatible path

If you already speak OpenAI SDKs, swap the base URL to /v1 and keep client code largely unchanged.

Anthropic Messages as-is

Claude-oriented clients keep the Anthropic host and Messages fields; docs do not collapse them into an OpenAI-shaped substitute.

Smart keys and group failover

Route by account policy, then fall back across groups when a primary path is unhealthy—inspect which route actually served each call.

Billing follows Model Square

Model availability, groups, and billable units are defined on the live pricing pages—treat those as the source of truth, not a copy here.

Jump to a guide

Coding tools

Wire Codex, Claude Code, Cherry Studio, and similar CLIs step by step.

Image Generation

Generate or edit images on enabled models and read route pricing in Model Square.

Smart API Key

Pick a routing strategy for the models your account can already use.

Group failover

Configure backups and see which route handled a request.

Models and billing

Routes, pricing units, wallet balance, and request logs.

Endpoints and auth

Base hosts, auth headers, and which contract each request type expects.