Tiktokenizer

Moonshot AI · Exact base text

Kimi K3.1 Pro Token Counter

Kimi K3.1 Pro is the first model in the K3.1 series, with a million-token context window. Moonshot highlights coding, 3D creation, financial research and long-horizon agent work. Its official research listing is dated October 24, 2026. Count plain-text tokens locally with the verified published tokenizer.

Accuracy note

Counts plain text with the verified published tokenizer, including real token IDs. Chat templates, role markers, tool definitions, media inputs and provider-added formatting are outside this base-text count.

Official counting docs →
Provider
Moonshot AI
Release milestone
2026-10-24 official research listing
Local counting
Exact base text
API key needed here
No

Facts checked against official sources on .

Release and model choices

The Pro Highspeed variant is positioned for more responsive interaction, with the announcement describing two to three times the speed of Pro. Both variants are offered across the Kimi product family and API.

The official K3.1 Pro repository publishes its tiktoken vocabulary and tokenizer configuration. This site verified the base vocabulary against the existing K3 browser conversion; that verification does not extend automatically to Highspeed or to complete XTML requests.

ModelLocal countingOpen tool
Kimi K3.1 ProExact base textSelect Kimi K3.1 Pro
Kimi K3.1 Pro HighspeedReference encodingSelect Kimi K3.1 Pro Highspeed

How to count Kimi K3.1 Pro tokens

Counts plain text with the verified published tokenizer, including real token IDs. Chat templates, role markers, tool definitions, media inputs and provider-added formatting are outside this base-text count.

Paste text into Plain text mode, or use Chat messages to count each message body independently. Switching models preserves your input. Chat mode excludes role names, separators and provider wrappers; adding bodies does not reproduce a serialized API conversation.

Local processing does not send your prompt to a model API or generate a response. Published tokenizer assets may be loaded by the browser, while the text analysis itself runs on your device.

Request limits and usage

K3.1 Pro's published tiktoken vocabulary at revision d9e99b0792a5e93b78ea9bea62a68167e36ddd9e matches all 163,584 base ranks in this site's tested K3 browser conversion. Its configured special-token IDs and splitting rules were checked too. Highspeed remains reference-only because its separate tokenizer mapping has not been verified. Neither mode includes XTML, tools, media or API overhead.

For a production request, include the actual conversation, system instructions, tool schemas and supported media in the provider's counting workflow when available. Check response usage after generation and account for subsequent calls, cache behavior, reasoning and output separately.

  • A model's advertised context window is not a guaranteed amount of pasted text.
  • A faster model or a cheaper token rate does not establish a lower total bill for every task.
  • Recheck the exact model version and counting method when migrating an existing prompt.

Tiktokenizer Reference Sources

Tokenizer behavior and model limits change. Verify production decisions with current provider documentation:

Frequently asked questions

Is this an exact Kimi K3.1 Pro tokenizer?

Counts plain text with the verified published tokenizer, including real token IDs. Chat templates, role markers, tool definitions, media inputs and provider-added formatting are outside this base-text count.

Does Kimi K3's exact tokenizer also count K3.1 Pro?

For K3.1 Pro base text, yes: the official vocabulary is byte-identical to K3's, all base ranks and configured special-token IDs match the tested browser conversion, and the splitting rules are unchanged. Highspeed is a separate reference-only selection; its mapping has not been verified.

Does selecting a model call its API or grant access?

No. These are local counting tools. They do not call provider inference APIs, spend model credits or grant access to restricted models. Follow the provider's access and verification process separately.

Can I use the result as my final API bill?

No. Even exact base-text counts exclude parts of a real request. Read the provider's actual usage, apply its current prices and include output, tools and repeated calls as applicable.