Quick start
Install CC Switch or call the API directly, then verify with a short text request.
Most people finish first setup with CC Switch. If you are wiring an SDK or your own server, jump to the API examples below and paste the base URL plus key yourself.
One model group needs only one API key. Extra keys do not raise concurrency—they mainly help you isolate apps, quotas, and revocation.
https://zashmodel.com/v1https://zashmodel.comClaude Code adds /v1/messages automatically. When sending a raw HTTP request, include /v1 exactly once in the full URL.
Recommended: CC Switch
- Install CC Switch
Download the Windows, macOS, or Linux build, install it, and leave the app running in the background so one-click import can open it.
Need a longer walkthrough? See Claude Code or Codex CLI—both include a CC Switch section.
- Create an API key for your group
Open API Keys, pick the model group this key should use, then create and copy it. A website password or an upstream vendor key cannot replace your Zashmodel API key.
Sign in first if needed, and keep enough wallet balance for the models in that group.
- Import with one click
On the key row, choose Import to CC Switch. Select the tools you use—Claude Code, Codex, and any others listed there—then confirm so CC Switch writes the provider for you.
- Send a short test message
In the tool you imported, send a brief text prompt first. When it replies, open Request logs to confirm the model, status, and charge.
Developers: call the API directly
Replace YOUR_API_KEY with your own key. Set these variables on your computer or application server; never put a real key in browser code, a public repository, or a screenshot.
export ZASHMODEL_API_KEY="YOUR_API_KEY"
export ZASHMODEL_BASE_URL="https://zashmodel.com/v1"
export ZASHMODEL_MODEL="YOUR_MODEL_ID"Verify access, then send a request
Choose the syntax for your terminal. Listing models checks authentication and visibility; the selected model must also support the endpoint you call.
curl --fail-with-body "$ZASHMODEL_BASE_URL/models" \
-H "Authorization: Bearer $ZASHMODEL_API_KEY"curl --fail-with-body "$ZASHMODEL_BASE_URL/responses" \
-H "Authorization: Bearer $ZASHMODEL_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<JSON
{
"model": "$ZASHMODEL_MODEL",
"input": "Hello!"
}
JSONA successful Responses request returns JSON with generated content in output. Then open Request logs to check the model, status, token usage and charge. Generation requests consume account balance.