Model Pricing and Billing

1. Billing Rules

Core billing unit: The platform bills per 100 million Tokens. A 1x multiplier = 40 yuan per 100 million Tokens, equivalent to 0.4 yuan per 1 million Tokens. The "multiplier" and "price per 1 million Tokens" columns in the table below use the same conversion basis, so you can read the prices directly from the table.

One Key works with every model. Multipliers only represent differences in model costs. You do not need a separate Key for each model.

Actual charges are based on system records. If a model receives a temporary subsidy, promotional discount, or multiplier adjustment, the price table on this page will be updated accordingly.

2. Cache Reads and Cache Writes

What is a cache hit? When consecutive requests contain a large amount of identical context, the system can reuse previously processed content. The cached portion does not need to be recomputed at the full input rate. Common examples include long conversations, consecutive follow-up questions, code completion, agent workflows, and multi-turn tool calls.

Input tokens are billed in three separate parts. Reading from the cache (a hit) is heavily discounted. Placing new content into the cache — a cache write, also called a cache miss — is billed at its own rate, which on some models is higher than standard input because the upstream provider charges a premium for it. Ordinary uncached input sits between the two. Each part appears as its own column in your usage records, so the three always add up to the input you actually sent.

Example: In a long conversation, the first turn that establishes the context pays the cache write rate on that context. Every later turn that reuses it pays the much lower cache read rate. New questions and newly generated output are still billed at the model's corresponding multiplier. This is why a conversation's first request can cost more than the ones that follow it.

Whether a request results in a cache hit depends on the request content, model capabilities, upstream caching policy, and current system availability. Final charges are based on billing records.

3. Model List and Multiplier Price Table (All Models Available)

How to read the table: Start with the model name, then check the multiplier, and finally review the "price per 1 million Tokens." A lower multiplier means a lower cost per Token. Multipliers and prices use the same conversion basis.

API endpoint: Use https://jzstoken.com/api/v1 whenever possible. If a client is incompatible with an address that includes /v1, try the base URL without /v1 instead. Different API gateway platforms, clients, and plugins may have different Base URL requirements. After switching models, we recommend testing with a small request first.

Price Table Change Monitoring Skill Installation Guide

The price table change monitoring Skill has been updated to 1.0.4. The new version fixes issues reading large tables in public Feishu documents and prioritizes the actual model price table, preventing explanatory tables from being misidentified as price tables.

One-command installation

clawhub install feishu-public-table-monitor

Update an existing installation to the latest version

clawhub update feishu-public-table-monitor --force

Recommended update command for an OpenClaw / Lobster workspace

clawhub --workdir ~/.openclaw/workspace update feishu-public-table-monitor --force

Example command for monitoring this price table

python3 ~/.openclaw/workspace/skills/feishu-public-table-monitor/scripts/monitor_feishu_price_table.py \
  "https://ycnfsn8b2u4z.feishu.cn/wiki/XFBBweJGoiboM7kKdjKca4Fvnvb" \
  --section-title "三、模型列表与倍率价格表（所有模型可用）"

How to use it: The first run creates a baseline. Run it on a schedule after that. An output of NO_REPLY means the price table has not changed. When changes are detected, it automatically generates a notification covering added models, removed models, multiplier changes, and price changes.

Scope: This Skill is designed for publicly accessible price tables in Feishu documents. For private documents or pages that require authentication, verify access permissions and data security requirements before connecting them.