Frequently asked questions
Common questions about Essevin integration, keys, protocols, models, and clients.
No. Essevin is directly accessible from mainland China without a proxy.
OpenAI protocols for GPT, Codex, and third-party clients include /v1. The Anthropic protocol for Claude Code and the Anthropic SDK does not; those clients append the API path themselves.
Use the OpenAI Images protocol: POST https://api.essevin.com/v1/images/generations with model, prompt, and size. GPT Image and Gemini image models use the same client-side request shape. Check GET /v1/models for models available to the current key, then see the Image API for generation and editing fields.
No. Each key belongs to one plan group. Use an OpenAI plan key for GPT and a Claude plan key for Claude. Create both in the console when your application needs both families.
Yes. The console's one-click integration dialog provides a Windows PowerShell command. Each manual setup page also includes Windows instructions.
The command contains a single-use integration token that expires after 15 minutes, not the API key itself. The script only updates local configuration and backs up existing settings.
Yes. Usage from the same key is combined under one account. Separate named keys per device make usage easier to attribute.
Sign in to the console. Usage Statistics shows the model, token count, and charge for every request.
This usually indicates temporary instability for that model. Retry shortly and contact us if it persists. See Troubleshooting for other errors.
Direct browser connections are supported. Web clients often do not append an API path. For OpenAI or GPT modes, enter the complete https://api.essevin.com/v1 URL. For Anthropic mode and Claude, omit /v1.