Every API on this site (the OpenAI / Anthropic (Claude) / Google / OpenRouter relays, the site-native APIs and MCP) is paid with your account credits.
402 right away (the site-native chat endpoint replies with a message in the stream) and the model is not called.count_tokens, video job status polling and balance checks are not charged.The exact amount charged for each call is the one reported with the response (see the next question). APIs and models change frequently. If you encounter an unsupported API or model, please contact us and we will add support as soon as possible.
X-Cost-Points (points charged for this call) and X-Credits-Remaining (your balance after the call).: cost=N and : credits-remaining=M carrying the same information; official SDKs ignore comment lines, so compatibility is not affected. Google Gemini streaming does not carry these lines — use the balance check below.cost (points charged) and credits (balance after the call).result._meta.Check your available credits at any time (free):
curl https://www.myai168.com/en/api/user/get_credits \
-H "Authorization: Bearer YOUR_API_KEY"
{"status": "OK", "credits": "34567", "credits_date": "2026-12-31"}
credits is your available balance (the numbers above are illustrative only) and credits_date is the expiry date of your credits; after that date the available balance is treated as 0. The Developer API Key page shows your account's cumulative API usage and the credits used by each key.
When you create or edit a key on the Developer API Key page, you can set its credit limit (0 = unlimited). Once the credits used by that key reach the limit, every further call with it returns HTTP 401 with API key credit limit reached! and the model is not called; raise the limit to continue (the used amount is not reset). The limit is checked before each call, so the last call may take the total slightly over the limit.
For MCP clients connected with OAuth (such as Claude.ai), you can set an account-level credit limit on the MCP Connections page.
We recommend a separate key, each with its own limit, for every program, CLI or AI agent you run, so one misbehaving program cannot drain your account. If a key leaks, delete it on the Developer API Key page right away and switch to a new key.
Every API authenticates with your developer key: send it in the Authorization: Bearer YOUR_API_KEY header (Anthropic endpoints also accept x-api-key, Google endpoints also accept x-goog-api-key); never place keys in URL query strings.
Get your developer key at: https://www.myai168.com/en/ai/user/developer
For base URLs, authentication, streaming, response headers and error codes, see API Quick Start; for the full list of documentation pages, see the Developer Center (https://www.myai168.com/en/developer/).