Product descriptions in bulk
Write a product description under 60 words and five benefit bullets strictly from the specs: <specs>
system: You write for an online store: specific, no superlatives.max_tokens: 400ChatGPT API (OpenAI GPT) with ruble billing: GPT flagships and light Luna models via one Zerocoder key. Input and output per 1M tokens, streaming, SDK.
ChatGPT is OpenAI's family of text models for chat, code, analysis and vision tasks. The family covers everything from quick, cheap replies to deep reasoning on long, complex prompts, so you pick the model that matches the job instead of overpaying for a single do-it-all endpoint.
One API key unlocks every model in the family. One ruble wallet pays for all of them, topped up with a Russian card or a company invoice, so you don't need a foreign card or a VPN. Docs and the key cabinet live on zerocoder.com, and the endpoints are compatible with the SDKs you already use.
You send a request to /v1/messages (Anthropic-style format) or /v1/chat/completions (OpenAI-style format), naming the model id you want. Before generation, Zerocoder reserves an estimate based on your input and max_tokens; after the model answers, the real usage is charged and any difference is refunded. Both endpoints support streaming, so you can show tokens as they arrive instead of waiting for the full answer.
The live GET /v1/models price list in rubles and dollars. Where we are cheaper, the vendor's official price for the same unit is struck through. Minimum per call: 0.5 ₽. Endpoints: /v1/messages, /v1/chat/completions
| Model | Price | Unit | Discount |
|---|---|---|---|
GPT-5.4recommended gpt-5.4 · OpenAIalso: openai-custom:gpt-5.4, gpt | Official price: | per 1M tokensofficial: 3:1 blend · $2.50 in / $15 out | -56% |
GPT-6 Luna gpt-6-luna · OpenAIalso: gpt-luna, gpt-nano | Official price: | per 1M tokensofficial: 3:1 blend · $0.10 in / $0.50 out | -75% |
GPT-5.5 gpt-5.5 · OpenAI | Official price: | per 1M tokensofficial: 3:1 blend · $5 in / $30 out | -6% |
GPT-6.1 Sol gpt-6.1-sol · OpenAI | Official price: | per 1M tokensofficial: 3:1 blend · $2 in / $10 out | -75% |
GPT-6 Sol gpt-6-sol · OpenAI | Official price: | per 1M tokensofficial: 3:1 blend · $2 in / $10 out | -75% |
GPT-5.6 Terra gpt-5.6-terra · OpenAI | Official price: | per 1M tokensofficial: 3:1 blend · $2 in / $12 out | -32% |
GPT-5.6 Sol gpt-5.6-sol · OpenAI | Official price: | per 1M tokensofficial: 3:1 blend · $4 in / $20 out | -24% |
GPT-5.6 Luna gpt-5.6-luna · OpenAIalso: gpt-mini | input 39.6 ₽ / output 317 ₽$0.440 / $3.52 | per 1M tokens | — |
Pick a model and a volume — the calculator uses the same formulas as API billing.
input 99 ₽ / output 594 ₽ per 1M tokens
minimum per call: 0.5 ₽
Prices from GET /v1/models, internal exchange rate. Failed generations are not charged.
The OpenAI SDK in Python and Node.js, the Anthropic SDK or curl: swap the base URL and the key — requests, streaming and response handling stay as they are. ChatGPT answers on POST /v1/messages and /v1/chat/completions.
Base URLhttps://zerocoder.com /api/v1Anthropic SDK — https://zerocoder.com, without /v1
Model in the samples — gpt; any model from the table works
from openai import OpenAI client = OpenAI( base_url="https://zerocoder.com/api/v1", api_key="zc-sk-…",) r = client.chat.completions.create( model="gpt", messages=[{"role": "user", "content": "Hello!"}],)print(r.choices[0].message.content)import OpenAI from "openai"; const client = new OpenAI({ baseURL: "https://zerocoder.com/api/v1", apiKey: "zc-sk-…",}); const r = await client.chat.completions.create({ model: "gpt", messages: [{ role: "user", content: "Hello!" }],});console.log(r.choices[0].message.content);import Anthropic from "@anthropic-ai/sdk"; const client = new Anthropic({ // without /v1: the SDK appends /v1/messages itself baseURL: "https://zerocoder.com/api", apiKey: "zc-sk-…",}); const msg = await client.messages.create({ model: "gpt", max_tokens: 300, messages: [{ role: "user", content: "Hello!" }],});console.log(msg.content[0].text);# Anthropic Messages formatcurl https://zerocoder.com/api/v1/messages \ -H "x-api-key: zc-sk-…" \ -H "content-type: application/json" \ -d '{"model": "gpt", "max_tokens": 400, "messages": [{"role": "user", "content": "Hello!"}]}' # OpenAI chat/completions format, streamingcurl -N https://zerocoder.com/api/v1/chat/completions \ -H "authorization: Bearer zc-sk-…" \ -H "content-type: application/json" \ -d '{"model": "gpt", "stream": true, "messages": [{"role": "user", "content": "Hello!"}]}'OpenAI list price (GPT-5.4); bars and discount compare both prices blended 3 : 1 (input : output); checked 4 October 2026

From a key to production — six steps based on the real /api/v1 contracts. Each step links to the relevant docs section.
Sign up, open the API section of your account, top up the balance in rubles and create a zc-sk-… key. One key unlocks ChatGPT and every other model in the catalogue.
Read more →POST /v1/chat/completions (Bearer) or /v1/messages (x-api-key) with model and messages — OpenAI and Anthropic shapes, the SDKs work with a swapped base URL.
Read more →stream: true — the answer arrives as SSE chunks with a final billing event showing the real charge. The reserve is taken by max_tokens (default 8192), so set it to fit the task.
Read more →30 requests per minute per key: on 429 wait and retry with a growing pause; 402 — top up the balance; 400 — check model against GET /v1/models. Failed generations are not charged, so retrying is safe.
Read more →GET /v1/balance returns the balance and 30-day spend; every call's price comes back in the response — write it to your logs and set an alert threshold in your own monitoring.
Read more →Keep the key in server secrets, never in the frontend. For high ChatGPT volumes contact us — the limit is raised individually and companies can pay by invoice. Check the observed stability on the status page.
Read more →HTTP Request node: POST to the /api/v1 endpoint, x-api-key header and a JSON body built from workflow fields. For video add a Wait node and a second HTTP Request on GET ?id= in a loop until completed.
HTTP “Make a request” module: POST, Body type JSON, x-api-key header. The response is parsed automatically — the image url or the answer text flows into the next modules.
Webhooks by Zapier → Custom Request action: POST, Data — JSON with model and prompt, Headers — x-api-key. Response fields are available to the following Zap steps.
In Apps Script use UrlFetchApp.fetch with method post, contentType application/json and a payload from the cells: prompts in one column, results written to the next one.
A bot on aiogram, grammY or Telegraf calls the same HTTP API: user message → model request → reply in the chat. For video — poll the status and send the file from the finished URL.
For text models the official OpenAI and Anthropic SDKs work with a swapped base URL and our key — your application code stays the same. Images and video are a plain HTTP call from any language.

More than a key: we help wire ChatGPT and other models into your workflows — from audit to production, with invoice payment.
# 401 {"type":"error","error":{"type":"authentication_error","message":"Invalid or revoked API key."}}
# 402 {"type":"error","error":{"type":"billing_error","message":"Not enough API balance: …"}}
# 429 {"type":"error","error":{"type":"rate_limit_error","message":"…"}} ← 30 requests/min per key
# 400 {"type":"error","error":{"type":"invalid_request_error","message":"Unknown model \"…\". See GET /v1/models."}}
# /chat/completions uses the OpenAI envelope: {"error":{"message":"…","type":"…","code":"insufficient_balance"}}
# streaming: the reserve (by max_tokens) is settled after the answer; a failure before the first token is refunded
# event: billing {"charged_rub":…,"reserved_rub":…,"balance_rub":…,"unit":"1M_tokens","rub_per_mtok_in":…,"rub_per_mtok_out":…,"rub_per_mtok":…}
Numbers come from the public /status summary: the share of successful requests over a period for the whole API and for the category as a whole (the summary has no per-model breakdown), no SLA promises. Failed generations are not charged, so retrying is safe.
Tracking since Aug 6, 2026.
Customer support bot that answers in a brand voice and escalates edge cases to a human
SaaS feature that drafts, rewrites or summarizes user documents on demand
Internal tool that reviews pull requests and explains code changes in plain language
Indie product that turns screenshots into structured data using vision input
Content pipeline that classifies, tags and extracts fields from incoming text at scale
Telegram or website assistant that keeps conversation history and streams replies live

Copy the prompt and the parameters into the request body — the fields are named exactly as in the /api/v1 contract. Replace the angle-bracket placeholders with your material.
Write a product description under 60 words and five benefit bullets strictly from the specs: <specs>
system: You write for an online store: specific, no superlatives.max_tokens: 400For the page below suggest three title options under 60 characters and a description under 155 characters with the key phrase “<phrase>”: <page text>
max_tokens: 400<the customer's message to classify>
system: Return JSON only: {"category": billing | delivery | quality | other, "priority": low | medium | high}max_tokens: 60Translate into German for an Austrian audience, keep formatting and placeholders in curly braces, adapt idioms: <text>
max_tokens: 1500<conversation history in messages, last turn from the user>
system: You are a consultant at a bicycle shop. Keep it short, ask about height and budget, suggest at most two models.stream: truemax_tokens: 500
Industries where this kind of generation becomes part of the workflow rather than an experiment.
ChatGPT through Zerocoder is billed per token: each GPT model has two prices per million tokens — input and output (output costs more), shown in the table above and in GET /v1/models, with the per-call minimum in min_rub. max_tokens is reserved at the output price and settled after the answer by usage; the actual charge arrives in the billing block of the last stream chunk.
Change two lines: base_url to zerocoder.com/api/v1 and api_key to a zc-sk-… key. The /v1/chat/completions format, the system / user / assistant roles, streaming and error codes match OpenAI, so the rest of your Python or Node.js code stays as it is. If you do not need the SDK, plain requests works — see the ChatGPT sample above.
The shared key limit is 30 requests per minute across all API endpoints; above it ChatGPT returns 429 rate_limit_error. Context is bounded by the chosen GPT model, max_tokens caps the answer and sets the reserve size, which is held until the answer ends. The temperature parameter is accepted but does not affect the answer.
The short ids gpt and gpt-luna are pinned to specific versions — which ones is shown in the aliases field of GET /v1/models; call newer versions by their exact id from the table. The flagship gpt is for reasoning and code, the light gpt-luna for routine generation, classification and extraction at the lowest price. The value smart hands the choice to the router, and the bill is for the model that actually answered.
If the ChatGPT answer never starts — the provider is down or the request is rejected — the reserve returns to the balance in full with no support ticket. Request format errors (400) and rate limiting (429) cost nothing. If a stream breaks midway, only the tokens actually generated per usage are charged.
Yes. A legal entity requests an invoice in the API account and pays it from the corporate account; once credited, the amount is spent on ChatGPT and other models with the same key. A Russian bank card tops up the balance immediately, and accounting documents are provided on request. No OpenAI account, VPN or foreign card needed.
There is no free quota in the API: the wallet opens with a minimum first top-up, then ChatGPT is charged per token with a per-call minimum. You can test GPT model answers on your own tasks for free in the Zerocoder studio and the ChatGPT tool in the catalogue, then move the prompt into /v1/chat/completions.
Yes. With stream: true the ChatGPT answer arrives in OpenAI-format chunks and ends with data: [DONE], the last chunk carrying a billing block with the actual charge. A user message may include up to 4 images as image_url parts (https URL or data URI) — vision is in beta: a dedicated vision model handles the pictures, and its name is visible in the model field of the response.

Up to -75% vs the official API · ruble billing, no VPN