Doken (DK) quantity, 0.30 RMB/DK for payment, Alipay, WeChat, and usage-based consumption. Includes complete inspection steps, practical verification, and error handling.

Recharge and balance consumption

This site currently does not offer a membership subscription plan; it only uses a balance consumption model:Use as much as you recharge, and charge according to the actual model call。 No extra multipliers for user grouping, nor any discounts on top-up tiers.

Payment in RMB, Doken records the balance

1 Word Knife (1 DK) = the amount of tokens used in the selected commercial API reference price, worth $1. The full English name is Doken, Writing by the organization DK。 This is a usage definition; the platform does not actually pay a $1 subscription fee, nor does it equal $1 in cash.

This site records balances and expenses based on this unit. The current recharge price is 0.30 yuan/DK, 10 DK recharge amount is 3 yuan, 100 DK is 30 yuan, plus the following payment channel fees; The price does not equal the exact subscription cost that hasn't been tested. DK does not represent a fixed word count or token count. If you want to know how the same batch of tokens is calculated from reference value to subscription cost, then converted to RMB or JPY, you can check it outUnderstand Doken in three minutes。

The upstream of EasyPay charges a 5% payment channel fee on the recharge amount. Estimated actual payment = recharge amount + payment channel fee. Channel fees are collected upstream by Easy Pay and are not included in DK balances; The recharge price and the amount of DK received remain unchanged.

For example, top-ups 200 DK: Recharge amount 60 yuan, pay the channel fee 3 yuan, estimated actual payment 63 yuan, the amount received still is 200 DK。 The amounts in the table are shown in RMB by denomination; small expenses may be rounded by sub-RMB,Final payment is subject to the display at the payment cashier。

The amount of deposit in the wallet is filled in by DK; The recharge amount, payment channel fee, and estimated actual payment in the payment confirmation are all in RMB. The current minimum top-up amount is 1 DK. Please check the quantity, estimated actual payment, and payment method before placing an order.

Current payment methods

Currently accessedAlipay, WeChatEasy Payment channel, orders are paid in RMB. Other payment portals are not yet open. The fixed quotes for yen, Hong Kong dollars, and US dollars in historical announcements are quoted publicly and should not be interpreted as having already opened for these currencies.

After payment is confirmed, the order status is recorded accordingly. If payment has been made but the balance has not yet been updated, please first check the deposit records and order status, keep the order number and time, and contact the administrator; Do not repeatedly pay for the same order, and do not give merchant or payment keys to anyone.

How to deduct fees when calling the call

Model unit price distinguishes between input, output, cache, and long upper and lower document slots. Different models may solve the same problem, with different token counts and consumption; The price is as followsModel Squareand actual consumption records shall prevail.

For example, if a call is priced at the public price of 0.2 DK, the balance will be deducted by about 0.2 DK; At the current recharge price, this means 0.2 × 0.30 = 0.06 yuan spent, which is 6 cents of the purchased balance. It is not an extra charge of RMB.

The number of tokens and pricing category per request affect consumption; you cannot promise a sentence to spend 0.2 DK fixedly, nor can you exchange 1 DK for a fixed word count.

Cache discounts and long document slots are pricing categories for the model itself, not special user multipliers. The grouping multiplier for this site is uniformly set at 1.

Errors, interceptions, and cancellations

Requests for local security interception do not enter the upstream and do not incur any fees for this model call. Normal and failed requests after entering upstream are handled by the system's deduction, settlement, and refund logic;Client cancellations, disconnections, or errors are not uniformly equal zero cost。 When questions arise, verify the consumption records, request numbers, and order records.

How to distinguish between platform subscriptions and your balance

When calculating costs, the platform should first use the commercial API reference price to obtain DKs for the same batch of tokens, then share the USD cost based on Codex subscription bills and actual usage, and finally convert to RMB or Japanese yen at a clear exchange rate. It cannot be deduced from the current price of 0.30 RMB/DK, nor can it guarantee a fixed DK amount for a single subscription fee.

You are purchasing DK balance on this site,No subscription to this site was purchased, nor was there a weekly or monthly reset rule due to the platform's subscription cycle。

See the current general explanationUnderstand Doken in three minutes。 A complete early cost estimate remainsHistorical announcements archived, where the old estimate is not the current quota guarantee.

The current user service methods are as shown on this pageUsage rulesas the standard. When the price or opening range changes, it will be inAnnouncements and articlesAnnounced publicly.

Checklist before practical use

1. Prepare your own account and access keys, and do not use others' shared credentials.
2. Records client versions, systems, and models to be used for easy reproduction during troubleshooting.
3. Save the original configuration or screenshot, hide keys, verification codes, and private content.
4. Confirm that testing may consume a small amount of DK, starting with a single sentence and a single request.
5. Review the current model plaza and status page before deciding whether to enable more features.

Detailed investigation: Order creation does not guarantee successful payment

First, verify the quantity, principal, channel fee, and actual payment, then complete payment at the actual cash register. When the page prompts 'processing', verify the actual deduction from the payment account and the order status on this site; Don't keep creating the same order. If the payment has not arrived, submit the order number, time, and anonymized payment records; do not submit the payment password.

How to confirm that this section has been learned

Don't just check the "Configuration saved successfully" prompt. You should be able to clearly state the current Base URL, key usage, chosen model, and request protocol, and be able to verify your operation results on the corresponding console. The client-side tutorial uses a single actual plain text response and corresponding logs as the initial completion standard; Account tutorials are based on comprehensive security information; The billing tutorial uses the correspondence between principal, channel fees, and DK as the standard.

If an error occurs, record the occurrence time, HTTP status, content of the anonymized error, and the actual expected result. Do not screenshot the entire page key, and do not give the password or verification code to others. For 401, authentication should be resolved first; for 400, parameters should be resolved first; for 429, intensive retries should be stopped; for 404, request paths and upstream verification should be verified; recharging cannot resolve all errors.

A small task suitable for practice

Complete the minimum steps in this section in your own testing environment, recording in text "how you originally set it, which item you modified, and what results you saw." Do not treat production data, real payments, or irrecoverable commands as exercises. If you encounter features beyond what this section offers, first check the corresponding protocol tutorial before considering adding features; Changing only one configuration at a time makes it easy to judge which step leads to errors.

The next step is the boundary of the version

Return to the full learning map · Streamlined API site configuration · Real-time status of this site。

The tutorial was compiled on October 9, 2026. The specific interface and capabilities may vary depending on the client and upstream versions; The configuration guidelines do not mean that all client versions have passed the test. For balance payments, QQ / Alipay login, and open channels, please refer to the actual page page; Compression interfaces: Previously, upstream 404 and raw image channels were not available, so don't assume configuration files can be automatically removed.