NezhaGate FAQ

NezhaGate is an OpenAI-compatible AI model gateway that connects you to GPT, Claude, Gemini and image-generation models through one API and one key. Instead of integrating each provider separately, you point your Base URL at NezhaGate and call multiple flagship models with the OpenAI SDK you already use. The platform includes API key management, balance and usage tracking, a model market and developer docs, billed by usage with no charge on failed requests.

NezhaGate is the platform and website brand, while NezhaAPI is the API / model-gateway service it provides — both point to the same service. NezhaAPI usually refers to the concrete endpoint and how you call it, and NezhaGate to the platform as a whole. Whichever name you see, the Base URL, API key and billing are the same.

It means using a single OpenAI-compatible interface to reach the flagship models of OpenAI (GPT), Anthropic (Claude) and Google (Gemini) at once. You do not maintain three SDKs, three accounts and three billing systems — just one Base URL and one key. To switch or compare models, you change a single model parameter.

NezhaGate currently provides the GPT-5.6 family (Sol / Terra / Luna), GPT-5.5 and GPT Image 2, Claude Sonnet 4.6, Gemini 3.1 Pro and Gemini 3.6 / 3.5 / 3 / 2.5 Flash, plus Nano Banana image generation and Veo 3.1 video, with new models added over time. The full, live model list and capability notes are shown on the Model Market page. Every model is called through the same endpoint and key.

Yes. The main models from GPT (OpenAI), Claude (Anthropic) and Gemini (Google) are all available through one OpenAI-compatible interface. Switching models only requires changing the model field in your request — no new SDK or re-integration needed.

Yes. The platform offers image-generation models such as gpt-image-2, callable through the /v1/images/generations endpoint for both text-to-image and image-to-image. Results are returned as direct links so you can reference them straight from your app. The exact available image models and parameters are described in the Model Market and docs.

The prices and capability notes in the Model Market follow the backend configuration in real time, so price changes appear on the page as they happen. We update the relevant entries when new models launch or billing changes. Please treat the live display on the Model Market and Pricing pages as authoritative.

NezhaGate uses prepaid credits and pay-as-you-go billing: chat models are billed by input / output tokens and image models by count and resolution, with unit prices shown on the Pricing page and Model Market. There are no monthly plans — you pay for what you use, and the balance is drawn down by actual usage. Every call's usage and cost is visible in the console.

NezhaGate offers more competitive model-access pricing through a unified gateway, transparent pay-as-you-go billing and cost optimization. Actual prices are as shown on the Pricing page and Model Market.

Topped-up credits currently have no short-term expiry; the latest rules are as stated by the platform. Failed requests are not charged, and the balance is consumed by actual usage.

Failed requests are not charged. Only calls that return successfully are billed by actual usage; upstream errors or timeouts do not consume your balance. If you see a failed record in the console, no cost is deducted for it.

After signing in, the console shows your real-time balance, per-key usage and every call record. Call logs include the model, time, tokens / image count and cost, making reconciliation and debugging easy. You can also read the current balance programmatically through the balance-query endpoint.

Getting started takes three steps: register an account, create an API key in the console, then point your Base URL at NezhaGate and add the key. Because it is fully OpenAI-compatible, existing OpenAI SDK code needs almost no changes — just swap base_url and api_key. See the developer docs for details.

Set the Base URL to https://nezhagate.com/v1. In the OpenAI SDK, set base_url (or the OPENAI_BASE_URL environment variable) to that address and use the key you created in the console. Use /v1/chat/completions for chat and /v1/images/generations for images — the paths match OpenAI.

Yes. NezhaGate implements the OpenAI-compatible interface, so the official openai SDK works by simply changing base_url and api_key. Request and response shapes match OpenAI, including streaming output and multimodal input.

Yes. Any language that can make HTTP requests or use the OpenAI SDK works, including Python, Node.js, Go, Java and plain curl. The docs include ready-to-run Python, Node.js and curl examples.

Yes. Most of these tools let you set a custom OpenAI-compatible Base URL and API key — point them at NezhaGate to use the platform's models. If a tool supports an OpenAI-compatible or custom endpoint, it can connect to NezhaGate with no extra plugin.

If you suspect an API key is leaked, delete or rotate it in the console immediately — once revoked, the old key can no longer be used. We recommend creating separate keys per project and never embedding keys in front-end code or public repos. You can check each key's usage in the console at any time to spot anomalies.

The official APIs are provided directly by the model vendors and suit teams that have official accounts and their own billing. NezhaGate is more of a unified model gateway, focused on multi-model access, OpenAI-compatible calls, billing management and developer efficiency.

NezhaGate provides a unified way to access mainstream model capabilities; the specific capabilities, context, speed and available features are as described in the Model Market and docs.

NezhaGate suits cases where you need to call several model providers in one project, want unified billing and usage management, or want to quickly validate different models. Common uses include AI tool sites, SaaS products, automation workflows, agents and multi-model comparison. It is especially convenient when you need to switch flexibly between models.

Yes. NezhaGate provides an OpenAI-compatible interface, API key management, pay-as-you-go billing and call logs, which fit integration into commercial products and tool sites. Please follow the platform terms and the upstream vendors' usage policies. We suggest evaluating routes and quota for your needs before going to production.

Under compliant use, NezhaGate aims to provide stable, continuous model access. Actual call behavior can be affected by the model, route, request volume and upstream status. You can review your API keys, balance and every call record in the console.

Keep your API keys safe, top up as needed, and follow the platform Terms and the upstream vendors' usage policies. Check the Pricing page before calling to understand billing and avoid unintended large usage. Specific features, prices and available models are as shown on the latest pages.

You may not use NezhaGate for anything that violates laws or upstream vendor policies, including generating or distributing illegal, infringing, fraudulent or malware content, or automated abuse and bypassing quota or safety limits. Violations may lead to account restriction or termination. The full rules are in the Terms of Service.

Yes. NezhaGate can handle larger-scale batch calls, and we welcome enterprise inquiries. For higher concurrency, dedicated quota or integration needs, reach us via the Contact us option on the site. The plan is tailored to your usage and scenario.