Kimi K3.1 Pro review: benchmarks, pricing and original test evidence

Kimi K3.1 Pro partial native API tests: text, code and SVG outputs, plus 11 official and AA benchmark originals. A five-hour subscription quota leaves tasks pending; outputs, budget retries and gaps are disclosed.

Updated: 2026-10-24

Launch sources checked October 24, 2026 · Original testing and commentary by TOKRACE. Third-party scores, vendor scores and our task outputs are presented separately.

What launched: a large-context reasoning and coding model

Kimi has released K3.1 Pro. For developers, the first distinction is access: the official public API, third-party providers and Kimi Coding subscriptions have different model IDs, billing and usage conditions. Our test evidence identifies the provider actually called; official specifications below describe Kimi's own platform.

Kimi K3.1 Pro launch specifications
ItemDocumented information
Model IDskimi-k3.1-pro / kimi-k3.1-pro-highspeed
Context1,048,576 token (1M)
Pro list price$2 / $10 / $0.20 per million tokens: input / output / cache-hit input
Highspeed list price$4 / $20 / $0.20 per million tokens, same order
China platform pricesPro: ¥13 / ¥68 / ¥1.30; Highspeed: ¥26 / ¥136 / ¥1.30 per million tokens, same order. Separate regional price table, not a currency conversion.
Cache writesSeparately billed by retention time. Pro: $2 / $4 or ¥13 / ¥26 per million tokens for 5 minutes / 1 hour; Highspeed: $4 / $8 or ¥26 / ¥52.
ThinkingAlways enabled; low / high / max; default max. Official docs require omitting temperature (fixed at 1).
Weight availabilityNot yet released as checked; Kimi promises release by November 4, 2026.

Source: Kimi release announcement · Official API guide · International pricing · China pricing

To try the model in TOKRACE, configure your own authorized pay-as-you-go API endpoint and key. Open Arena →

Independent third party · Artificial Analysis

Artificial Analysis benchmark originals

AA reports Intelligence Index 55 (#4 at launch), GDPval-AA 1846, Terminal-Bench 4.0 67.2%, and a 2.8T-total / 104B-active architecture. These are AA results. Read the source

Its Terminal-Bench setup differs from Kimi's 65.7%; compare harnesses and tools before scores. Click the unmodified figures for axes, legends and footnotes.

AA Intelligence Index

AA Intelligence Index

Launch score 55, ranked fourth; K3 scored 44.

Artificial Analysis · Source article · Original image URL · Zoom / download

AA agent benchmarks: terminal, GDPval and Briefcase

AA agent benchmarks: terminal, GDPval and Briefcase

Original AA charts for terminal and knowledge-work tasks.

Artificial Analysis · Source article · Original image URL · Zoom / download

AA knowledge reliability and hallucination

AA knowledge reliability and hallucination

AA-Omniscience index, accuracy and hallucination rate.

Artificial Analysis · Source article · Original image URL · Zoom / download

AA cost per task

AA cost per task

Weighted Intelligence Index task cost, including reasoning and caching.

Artificial Analysis · Source article · Original image URL · Zoom / download

AA intelligence versus parameter count

AA intelligence versus parameter count

AA comparisons by total and active parameter count.

Artificial Analysis · Source article · Original image URL · Zoom / download

AA individual evaluation results

AA individual evaluation results

Original overview of eleven AA evaluation metrics.

Artificial Analysis · Source article · Original image URL · Zoom / download

TOKRACE original API tasks

TOKRACE evaluation: current status and evidence

The batch dispatched 51/69 initial requests. All 30 complete text and 4 complete code answers passed checks. Final outputs comprise 12 static images and 2 animations. Three initial attempts hit the 12,288-token limit; two independent 32,768-token retries succeeded. Cycling components move, but legs stretch and joints look mechanical. The five-hour quota caused two 429 errors and left 18 tasks unsent; default animation remains pending. These quota interruptions are excluded from accuracy. Default is documented as max; effective effort is unconfirmed, so results are grouped by requested parameters. These small fixed tasks do not establish an overall ranking.

This new batch uses Kimi Coding's native Anthropic Messages endpoint, separate from the earlier stopped OpenAI-compatible batch. It consumes Coding subscription quota; no per-token paid invoice or conversion from Kimi's public platform list prices is asserted. Requested and returned IDs are retained, without treating a mutable alias as a fixed checkpoint.

Recorded endpoint:https://api.kimi.com/coding · Model ID:k3.1-pro

Actual request URL:https://api.kimi.com/coding/v1/messages

SettingSupport / interpretation
OffUnsupported; no off result is fabricated.
LowRequests send output_config.effort=low; effective strength is not independently verified.
HighOfficially supported; outside this default / low / max comparison.
Default / MaxThe official public API documents default=max. For this native endpoint, default and max label request groups; effective effort is not independently verified.
Small fixed tasks; passing / completed answers. API failures are separate from answer quality.
Requested groupText: passed / completeCode: passed / completeCompleted text first content, medianCompleted text total, medianCompleted code total, median
Requested: low15 / 15Sent / planned: 15 / 15 · 429: 0 · Unsent: 03 / 3Sent / planned: 3 / 3 · 429: 0 · Unsent: 02.79s2.82s11.22s
Requested: default (effort omitted)0 / 0Sent / planned: 1 / 15 · 429: 1 · Unsent: 140 / 0Sent / planned: 0 / 3 · 429: 0 · Unsent: 3———
Requested: max15 / 15Sent / planned: 15 / 15 · 429: 0 · Unsent: 01 / 1Sent / planned: 2 / 3 · 429: 1 · Unsent: 13.55s3.58s156.47s

Text/code batch: 36 retained requests; recorded request time totals 282.09s, excluding visual tasks, retry backoff and unknown interrupted durations. Output limits: 12,288 token; request timeout 600s. See each request for exact settings. The timings describe this run; they do not establish provider-wide speed or different effective reasoning strengths.

For these native requests, max_tokens covers both thinking and final text; no separate thinking.budget_tokens was supplied. Input accounting follows returned usage fields, with cache read/write components retained in the JSON. Hidden reasoning content is not published.

Across all task requests, recorded request time sums to 2991.49s; the batch's wall-clock span is 1130.24s. Requests ran concurrently, so these are different measures. 5 separate protocol diagnostics are excluded from task scores and the task-request count; the historical stopped batch remains separate.

Read individual failures before choosing a model. Deterministic checks cover only the written task requirements; visual commentary is the AI assistant's qualitative inspection. A rendered image is not automatically a correct image, and successful code checks do not establish production reliability.

Updated visual evaluation · 2026-10-24

Requested thinking settings, retries and a cycling pelican animation

This batch calls k3.1-pro through Kimi Coding Plan’s native Anthropic Messages endpoint https://api.kimi.com/coding/v1/messages. Each requested default/low/max configuration plans 23 tasks; at most three requests run concurrently, sequentially within each configuration. New dispatches stopped when the five-hour subscription quota was exhausted. Unsent tasks have no fabricated attempt, and quota failures are not scored as model-answer failures. Default is documented as max; omitted-default and explicit-max requests are independent records and are not treated as distinct capability levels. Low/max use native output_config.effort, not a thinking budget. Prompt-token totals sum native input_tokens, cache_read_input_tokens and cache_creation_input_tokens; raw usage is retained. Initial max_tokens=12,288 covers thinking plus final output; timeout 600 seconds. Temperature/top_p omitted; no thinking.budget_tokens configured. Requests consume subscription quota; metered list prices are not the actual invoice. The stopped Chat Completions subset stays separate. Images and animation directly render the model’s unchanged SVG. Assessments are qualitative AI-assistant visual inspection. Single-request timings include queueing, concurrency and output-length effects; they do not establish a stable speed ranking. Requested and returned IDs are preserved; a mutable API route is not independent proof of a fixed internal checkpoint. The server accepted the invalid-effort negative control, so the effective low/max semantics are not independently confirmed. Results are grouped by requested parameters, not claimed as a verified effort-level comparison. This evidence set includes every initial visual request and independent retry. Static cards reuse the same 12 original static requests below; repeated display does not represent additional API calls. Official parameter documentation

17 visual request records in this evidence set. Failed attempts are retained below each result. We show the first successfully rendered result in each sequence, not a best-of selection. Render success does not imply correct geometry or instruction following. Original first attempts remain below. Dates and budgets can differ; these are examples, not a statistical ranking.

New requests use a 600-second timeout and 12,288 output tokens; after a failed supplemental attempt the retry budget rises to 32,768 (up to 65,536 for repeated DeepSeek truncation). Each request records its exact budget. Animations are model-generated SVG SMIL, captured without source edits at 10 fps for four seconds. Click to play; click again to pause.

The five-hour subscription quota is exhausted and new requests are stopped. Animation outputs for default remain unavailable, pending a quota reset. No automatic polling or retries are running.

Failure records: 0 server errors, 0 connection failures, 0 timeouts, 0 interrupted, 3 truncated, 0 invalid SVG/animation. Wall-clock timings include interruptions; some exceed the configured timeout and should not be interpreted as model inference latency.

Quota errors (HTTP 429): 2. These are access failures, not incorrect model answers.

Download all supplemental requests and failures

Pelican riding a bicycle

Requested default (documented max)
Pelican riding a bicycle · default

2026-10-24 UTC · Attempt 2 · 267.53s · 13700 token

First content: 231.59s · Token limit: 32768

An independent retry succeeded after increasing the output cap to 32,768; the original 12,288-token truncation is retained separately. The long bill, pouch and webbed feet are clear, with a connected bicycle frame, a wing reaching the handlebar and feet at both pedals. Nothing is clipped. The sequence took about 509.41 seconds in total and is not a same-budget first-attempt result.

Recorded requests in this sequence: 2 · Recorded request time: 509.41s

Original SVG · Request evidence

Earlier attempts and failures (1)
  1. #1 · 2026-10-24T01:26:00.042Z · truncated · 241.88s · No complete SVG in the original response
Exact prompt
Generate an SVG of a pelican riding a bicycle
Requested parameter · low
Pelican riding a bicycle · low

2026-10-24 UTC · Attempt 1 · 88.67s · 5221 token

First content: 62.94s · Token limit: 12288

The long bill and hanging throat pouch clearly identify a pelican, and the two wheels connect through a coherent red frame. The wing reaches the handlebar and both feet meet the pedal areas. The saddle is mostly hidden by the body, but the riding pose remains clear; nothing is clipped.

Recorded requests in this sequence: 1 · Recorded request time: 88.67s

Original SVG · Request evidence

Exact prompt
Generate an SVG of a pelican riding a bicycle
Requested parameter · max
Pelican riding a bicycle · max

2026-10-24 UTC · Attempt 1 · 158.59s · 10373 token

First content: 129.04s · Token limit: 12288

The long bill, throat pouch and webbed feet are recognizable, and the two wheels, frame, chain and saddle form a readable bicycle. Both feet meet opposite crank ends while the extended wing reaches the curved handlebar, making the riding connection clear. The complete subject stays inside the canvas against a restrained light background.

Recorded requests in this sequence: 1 · Recorded request time: 158.59s

Original SVG · Request evidence

Exact prompt
Generate an SVG of a pelican riding a bicycle

An analog clock at 9:41

Requested default (documented max)
An analog clock at 9:41 · default

2026-10-24 UTC · Attempt 1 · 154.62s · 10049 token

First content: 139.62s · Token limit: 12288

All twelve numbers and minute ticks are complete and correctly ordered. The short hour hand sits between nine and ten and the minute hand just past eight. Source angles are exactly 290.5° and 246°, with lengths 96 and 132. The separate 09:41 label is clear, with no second hand or overlap.

Recorded requests in this sequence: 1 · Recorded request time: 154.62s

Original SVG · Request evidence

Exact prompt
Return only a complete, self-contained static SVG with viewBox="0 0 800 600". Draw a clear analog clock showing exactly 9:41, with all twelve numbers 1 through 12. The hour hand must be correctly positioned between 9 and 10, not exactly on 9. The minute hand must indicate minute 41. Use a shorter hour hand and a longer minute hand, no second hand. Add a small label "09:41" below the dial. Do not use scripts, external assets or embedded images.
Requested parameter · low
An analog clock at 9:41 · low

2026-10-24 UTC · Attempt 1 · 74.75s · 4852 token

First content: 64.43s · Token limit: 12288

All twelve numbers appear in the correct clockwise order, with a clear 09:41 label below the dial. The source rotates the hour hand 290.5° and the minute hand 246° from twelve, with lengths 118 and 170 respectively. It shows 9:41 correctly, has no extra second hand, and keeps generous spacing and strong contrast.

Recorded requests in this sequence: 1 · Recorded request time: 74.75s

Original SVG · Request evidence

Exact prompt
Return only a complete, self-contained static SVG with viewBox="0 0 800 600". Draw a clear analog clock showing exactly 9:41, with all twelve numbers 1 through 12. The hour hand must be correctly positioned between 9 and 10, not exactly on 9. The minute hand must indicate minute 41. Use a shorter hour hand and a longer minute hand, no second hand. Add a small label "09:41" below the dial. Do not use scripts, external assets or embedded images.
Requested parameter · max
An analog clock at 9:41 · max

2026-10-24 UTC · Attempt 1 · 130.75s · 8357 token

First content: 118.13s · Token limit: 12288

The dial contains all twelve numbers in the correct order and a full minute scale, with a separate readable 09:41 label. Source rotations are 290.5° and 246°, and the hour/minute lengths are 100 and 140, so both the time and relative lengths are correct. There is no second hand or overlapping text.

Recorded requests in this sequence: 1 · Recorded request time: 130.75s

Original SVG · Request evidence

Exact prompt
Return only a complete, self-contained static SVG with viewBox="0 0 800 600". Draw a clear analog clock showing exactly 9:41, with all twelve numbers 1 through 12. The hour hand must be correctly positioned between 9 and 10, not exactly on 9. The minute hand must indicate minute 41. Use a shorter hour hand and a longer minute hand, no second hand. Add a small label "09:41" below the dial. Do not use scripts, external assets or embedded images.

Data chart and proportional bars

Requested default (documented max)
Data chart and proportional bars · default

2026-10-24 UTC · Attempt 1 · 186.04s · 9631 token

First content: 167.01s · Token limit: 12288

The title, total of 84, best quarter Q4 and all four values are correct. Main-chart bars share y=478 as their bottom and have heights 96, 192, 144 and 240, exactly 2:4:3:5. Ten-unit axis intervals span 80 pixels, matching the bars. Value and quarter labels are readable without overlap or clipping.

Recorded requests in this sequence: 1 · Recorded request time: 186.04s

Original SVG · Request evidence

Exact prompt
Return only a complete, self-contained static SVG with viewBox="0 0 800 600". Design a polished dashboard card titled "Quarterly Revenue". Draw a vertical bar chart for Q1=12, Q2=24, Q3=18, Q4=30, in that left-to-right order. All four bars must share a zero baseline, and bar heights must be exactly proportional to the values. Show a y-axis labeled 0, 10, 20, 30 and show the value above each bar. Add summary labels "Total: 84" and "Best: Q4". Use a light background and readable typography. Do not use scripts, external assets or embedded images.
Requested parameter · low
Data chart and proportional bars · low

2026-10-24 UTC · Attempt 1 · 49.87s · 2812 token

First content: 32.18s · Token limit: 12288

Q1–Q4 correctly show 12, 24, 18 and 30, with Total: 84 and Best: Q4. All four source rectangles end at y=450 and have heights 108, 216, 162 and 270, exactly 2:4:3:5. The 0/10/20/30 ticks share the same nine-pixels-per-unit scale. Values, summaries and axis labels remain clear without overlap.

Recorded requests in this sequence: 1 · Recorded request time: 49.87s

Original SVG · Request evidence

Exact prompt
Return only a complete, self-contained static SVG with viewBox="0 0 800 600". Design a polished dashboard card titled "Quarterly Revenue". Draw a vertical bar chart for Q1=12, Q2=24, Q3=18, Q4=30, in that left-to-right order. All four bars must share a zero baseline, and bar heights must be exactly proportional to the values. Show a y-axis labeled 0, 10, 20, 30 and show the value above each bar. Add summary labels "Total: 84" and "Best: Q4". Use a light background and readable typography. Do not use scripts, external assets or embedded images.
Requested parameter · max
Data chart and proportional bars · max

2026-10-24 UTC · Attempt 1 · 129.39s · 6813 token

First content: 111.36s · Token limit: 12288

Quarter order, values, Total: 84 and Best: Q4 are correct and readable. All bars end at y=460, with heights 96, 192, 144 and 240, exactly 2:4:3:5. Each ten-unit tick interval is 80 pixels, consistent with the bars. Summaries and labels do not overlap, and a separate color highlights Q4.

Recorded requests in this sequence: 1 · Recorded request time: 129.39s

Original SVG · Request evidence

Exact prompt
Return only a complete, self-contained static SVG with viewBox="0 0 800 600". Design a polished dashboard card titled "Quarterly Revenue". Draw a vertical bar chart for Q1=12, Q2=24, Q3=18, Q4=30, in that left-to-right order. All four bars must share a zero baseline, and bar heights must be exactly proportional to the values. Show a y-axis labeled 0, 10, 20, 30 and show the value above each bar. Add summary labels "Total: 84" and "Best: Q4". Use a light background and readable typography. Do not use scripts, external assets or embedded images.

Chinese poster and layout constraints

Requested default (documented max)
Chinese poster and layout constraints · default

2026-10-24 UTC · Attempt 1 · 153.48s · 9982 token

First content: 139.22s · Token limit: 12288

All six strings are exact and appear once, with complete readable Chinese glyphs. Font sizes of 56 for the title, 28 for time/place and 16 for the note provide the requested hierarchy. The information card, orange button and bicycle occupy separate areas, with adequate margins and no clipping or overlap.

Recorded requests in this sequence: 1 · Recorded request time: 153.48s

Original SVG · Request evidence

Exact prompt
只输出一个完整、自包含的静态 SVG,viewBox="0 0 800 600"。设计一张清晰、精致的中文活动海报。必须且仅包含以下六段文字,每段出现一次,不能增删字或改写:主标题“周末骑行计划”;副标题“慢一点,看见城市”;时间“10月24日 09:00”;地点“滨江公园东门”;说明“自备头盔 · 全程12公里”;按钮文字“立即报名”。画一个简洁的自行车图标。主标题最大,时间地点次之,说明最小。背景浅色,留足边距,所有文字保持在画布内,不重叠,不使用脚本、外部素材或嵌入图片。
Requested parameter · low
Chinese poster and layout constraints · low

2026-10-24 UTC · Attempt 1 · 51.24s · 3148 token

First content: 34.17s · Token limit: 12288

All six exact Chinese strings appear once, with no extra wording, and the Chinese glyphs render clearly. Font sizes of 56 for the title, 30 for the time/place and 18 for the note establish the requested hierarchy. Information, bicycle icon and button have clear separation, adequate margins and no clipping or overlap.

Recorded requests in this sequence: 1 · Recorded request time: 51.24s

Original SVG · Request evidence

Exact prompt
只输出一个完整、自包含的静态 SVG,viewBox="0 0 800 600"。设计一张清晰、精致的中文活动海报。必须且仅包含以下六段文字,每段出现一次,不能增删字或改写:主标题“周末骑行计划”;副标题“慢一点,看见城市”;时间“10月24日 09:00”;地点“滨江公园东门”;说明“自备头盔 · 全程12公里”;按钮文字“立即报名”。画一个简洁的自行车图标。主标题最大,时间地点次之,说明最小。背景浅色,留足边距,所有文字保持在画布内,不重叠,不使用脚本、外部素材或嵌入图片。
Requested parameter · max
Chinese poster and layout constraints · max

2026-10-24 UTC · Attempt 1 · 122.09s · 7678 token

First content: 111.64s · Token limit: 12288

The six required strings are exact and appear once each, with no additional wording or missing Chinese glyphs. Font sizes of 58 for the heading, 28 for time/place and 16 for the note meet the hierarchy. The button is well separated, the bicycle is recognizable, and all text and graphics remain within the canvas without crowding, overlap or clipping.

Recorded requests in this sequence: 1 · Recorded request time: 122.09s

Original SVG · Request evidence

Exact prompt
只输出一个完整、自包含的静态 SVG,viewBox="0 0 800 600"。设计一张清晰、精致的中文活动海报。必须且仅包含以下六段文字,每段出现一次,不能增删字或改写:主标题“周末骑行计划”;副标题“慢一点,看见城市”;时间“10月24日 09:00”;地点“滨江公园东门”;说明“自备头盔 · 全程12公里”;按钮文字“立即报名”。画一个简洁的自行车图标。主标题最大,时间地点次之,说明最小。背景浅色,留足边距,所有文字保持在画布内,不重叠,不使用脚本、外部素材或嵌入图片。

Animated cycling pelican

Requested default (documented max)

Provider has not returned a renderable result yet.

2026-10-24 UTC · Attempt 1 · 213.24s · 12288 token

First content: — · Token limit: 12288

This attempt did not finish normally with a renderable result: No complete SVG in the original response. Its original evidence is retained; the first successful retry is shown separately.

Recorded requests in this sequence: 1 · Recorded request time: 213.24s

· Request evidence

Exact prompt
Return only a complete self-contained animated SVG with viewBox="0 0 800 600". Draw a recognizable pelican riding a bicycle: long bill and throat pouch, two wheels, connected frame, saddle and handlebar. Animate rotating wheel spokes and a rotating crank with pedaling legs that remain attached to the rider and pedals. Use SVG SMIL animateTransform/animate/animateMotion only (no CSS animation), with a seamless 4-second repeating loop. Keep the whole bicycle and bird on the canvas. Use a light background. No scripts, foreignObject, external assets, external fonts or embedded images. Use only local SVG shapes and text. The animation must visibly move, not just contain animation tags.
Requested parameter · low
Animated cycling pelican · low

2026-10-24 UTC · Attempt 1 · 153.12s · 10010 token

First content: 106.84s · Token limit: 12288

The bill, pouch, wheels and frame are clear, and orange markers make the spoke rotation visible; the crank, both legs and pedals genuinely move. Inspection of 0/1/2/3/4-second frames and playback of the encoded WebP found no clipping or visible loop jump. Legs and pedals share coordinates and stay connected, although eight linear interpolation segments produce slightly mechanical knees and stretching rather than realistic joint kinematics.

Recorded requests in this sequence: 1 · Recorded request time: 153.12s

Original SVG · Animated WebP · Request evidence

Exact prompt
Return only a complete self-contained animated SVG with viewBox="0 0 800 600". Draw a recognizable pelican riding a bicycle: long bill and throat pouch, two wheels, connected frame, saddle and handlebar. Animate rotating wheel spokes and a rotating crank with pedaling legs that remain attached to the rider and pedals. Use SVG SMIL animateTransform/animate/animateMotion only (no CSS animation), with a seamless 4-second repeating loop. Keep the whole bicycle and bird on the canvas. Use a light background. No scripts, foreignObject, external assets, external fonts or embedded images. Use only local SVG shapes and text. The animation must visibly move, not just contain animation tags.
Requested parameter · max
Animated cycling pelican · max

2026-10-24 UTC · Attempt 2 · 333.56s · 20318 token

First content: 296.55s · Token limit: 32768

An independent retry raised the output limit from 12,288 to 32,768 tokens; the first truncated attempt remains retained. Combined request time was about 534.14 seconds. The bill and pouch are recognizable, the wing reaches the handlebar and the body rests on the saddle. Spokes, crank, both legs and pedals visibly move. Individual 0/1/2/3/4-second frames and encoded WebP playback showed no clipping or perceptible boundary jump. Leg endpoints match the pedals, but both legs straighten around one and three seconds and noticeably stretch; motion is connected but mechanically stylized rather than realistic cycling kinematics.

Recorded requests in this sequence: 2 · Recorded request time: 534.14s

Original SVG · Animated WebP · Request evidence

Earlier attempts and failures (1)
  1. #1 · 2026-10-24T01:35:00.887Z · truncated · 200.58s · No complete SVG in the original response
Exact prompt
Return only a complete self-contained animated SVG with viewBox="0 0 800 600". Draw a recognizable pelican riding a bicycle: long bill and throat pouch, two wheels, connected frame, saddle and handlebar. Animate rotating wheel spokes and a rotating crank with pedaling legs that remain attached to the rider and pedals. Use SVG SMIL animateTransform/animate/animateMotion only (no CSS animation), with a seamless 4-second repeating loop. Keep the whole bicycle and bird on the canvas. Use a light background. No scripts, foreignObject, external assets, external fonts or embedded images. Use only local SVG shapes and text. The animation must visibly move, not just contain animation tags.
Historical first attempts · 2026-10-24 · 12 requests

Current outputs and successful retries are shown above. This archive preserves the original first attempts and their assessments; failures here describe those earlier requests. View current results

TOKRACE original visual tests

Historical first-attempt outputs and failures

4 fixed prompts × 3 modes, 12 additional API requests on 2026-10-24. Each image is the first answer rendered from SVG code, with no redraw, repair, feedback or best-of selection. This tests drawing with code, not a native image-generation model. A separate dataset contains 36 text/code attempts.

This batch calls k3.1-pro through Kimi Coding Plan’s native Anthropic Messages endpoint https://api.kimi.com/coding/v1/messages. Each requested default/low/max configuration plans 23 tasks; at most three requests run concurrently, sequentially within each configuration. New dispatches stopped when the five-hour subscription quota was exhausted. Unsent tasks have no fabricated attempt, and quota failures are not scored as model-answer failures. Default is documented as max; omitted-default and explicit-max requests are independent records and are not treated as distinct capability levels. Low/max use native output_config.effort, not a thinking budget. Prompt-token totals sum native input_tokens, cache_read_input_tokens and cache_creation_input_tokens; raw usage is retained. Initial max_tokens=12,288 covers thinking plus final output; timeout 600 seconds. Temperature/top_p omitted; no thinking.budget_tokens configured. Requests consume subscription quota; metered list prices are not the actual invoice. The stopped Chat Completions subset stays separate. Images and animation directly render the model’s unchanged SVG. Assessments are qualitative AI-assistant visual inspection. Single-request timings include queueing, concurrency and output-length effects; they do not establish a stable speed ranking. Requested and returned IDs are preserved; a mutable API route is not independent proof of a fixed internal checkpoint. The server accepted the invalid-effort negative control, so the effective low/max semantics are not independently confirmed. Results are grouped by requested parameters, not claimed as a verified effort-level comparison.

Download prompts, responses, parameters and image provenance

Pelican riding a bicycle

Inspect: Recognizable pelican bill and pouch; Two wheels and a connected bicycle frame; Coherent rider, saddle, pedals and handlebar relationships。

Original pelican prompt: Simon Willison (2024)

Requested default (documented max)Historical first attempt · 2026-10-24

First attempt failed; a later retry rendered successfully. View the successful retry

First answer content 240.93s · Total 241.88s · 12288 completion tokens incl. reasoning

This attempt did not finish normally with a renderable result: No complete SVG in the original response. Its original evidence is retained; the first successful retry is shown separately.

Requested parameter · lowHistorical first attempt · 2026-10-24
Kimi K3.1 Pro low: Pelican riding a bicycle

First answer content 62.94s · Total 88.67s · 5221 completion tokens incl. reasoning

The long bill and hanging throat pouch clearly identify a pelican, and the two wheels connect through a coherent red frame. The wing reaches the handlebar and both feet meet the pedal areas. The saddle is mostly hidden by the body, but the riding pose remains clear; nothing is clipped.

Original SVG · Full-size PNG

Requested parameter · maxHistorical first attempt · 2026-10-24
Kimi K3.1 Pro max: Pelican riding a bicycle

First answer content 129.04s · Total 158.59s · 10373 completion tokens incl. reasoning

The long bill, throat pouch and webbed feet are recognizable, and the two wheels, frame, chain and saddle form a readable bicycle. Both feet meet opposite crank ends while the extended wing reaches the curved handlebar, making the riding connection clear. The complete subject stays inside the canvas against a restrained light background.

Original SVG · Full-size PNG

Exact prompt, shared by the modes
Generate an SVG of a pelican riding a bicycle

An analog clock at 9:41

Inspect: Twelve numbers in the correct order; Minute hand at 246 degrees clockwise from 12; Shorter hour hand at 290.5 degrees, between 9 and 10。

Requested default (documented max)Historical first attempt · 2026-10-24
Kimi K3.1 Pro default: An analog clock at 9:41

First answer content 139.62s · Total 154.62s · 10049 completion tokens incl. reasoning

All twelve numbers and minute ticks are complete and correctly ordered. The short hour hand sits between nine and ten and the minute hand just past eight. Source angles are exactly 290.5° and 246°, with lengths 96 and 132. The separate 09:41 label is clear, with no second hand or overlap.

Original SVG · Full-size PNG

Requested parameter · lowHistorical first attempt · 2026-10-24
Kimi K3.1 Pro low: An analog clock at 9:41

First answer content 64.43s · Total 74.75s · 4852 completion tokens incl. reasoning

All twelve numbers appear in the correct clockwise order, with a clear 09:41 label below the dial. The source rotates the hour hand 290.5° and the minute hand 246° from twelve, with lengths 118 and 170 respectively. It shows 9:41 correctly, has no extra second hand, and keeps generous spacing and strong contrast.

Original SVG · Full-size PNG

Requested parameter · maxHistorical first attempt · 2026-10-24
Kimi K3.1 Pro max: An analog clock at 9:41

First answer content 118.13s · Total 130.75s · 8357 completion tokens incl. reasoning

The dial contains all twelve numbers in the correct order and a full minute scale, with a separate readable 09:41 label. Source rotations are 290.5° and 246°, and the hour/minute lengths are 100 and 140, so both the time and relative lengths are correct. There is no second hand or overlapping text.

Original SVG · Full-size PNG

Exact prompt, shared by the modes
Return only a complete, self-contained static SVG with viewBox="0 0 800 600". Draw a clear analog clock showing exactly 9:41, with all twelve numbers 1 through 12. The hour hand must be correctly positioned between 9 and 10, not exactly on 9. The minute hand must indicate minute 41. Use a shorter hour hand and a longer minute hand, no second hand. Add a small label "09:41" below the dial. Do not use scripts, external assets or embedded images.

Data chart and proportional bars

Inspect: Correct quarter order, values and total of 84; Shared zero baseline and heights in the ratio 2:4:3:5; Readable axis, values and summaries without overlap。

Requested default (documented max)Historical first attempt · 2026-10-24
Kimi K3.1 Pro default: Data chart and proportional bars

First answer content 167.01s · Total 186.04s · 9631 completion tokens incl. reasoning

The title, total of 84, best quarter Q4 and all four values are correct. Main-chart bars share y=478 as their bottom and have heights 96, 192, 144 and 240, exactly 2:4:3:5. Ten-unit axis intervals span 80 pixels, matching the bars. Value and quarter labels are readable without overlap or clipping.

Original SVG · Full-size PNG

Requested parameter · lowHistorical first attempt · 2026-10-24
Kimi K3.1 Pro low: Data chart and proportional bars

First answer content 32.18s · Total 49.87s · 2812 completion tokens incl. reasoning

Q1–Q4 correctly show 12, 24, 18 and 30, with Total: 84 and Best: Q4. All four source rectangles end at y=450 and have heights 108, 216, 162 and 270, exactly 2:4:3:5. The 0/10/20/30 ticks share the same nine-pixels-per-unit scale. Values, summaries and axis labels remain clear without overlap.

Original SVG · Full-size PNG

Requested parameter · maxHistorical first attempt · 2026-10-24
Kimi K3.1 Pro max: Data chart and proportional bars

First answer content 111.36s · Total 129.39s · 6813 completion tokens incl. reasoning

Quarter order, values, Total: 84 and Best: Q4 are correct and readable. All bars end at y=460, with heights 96, 192, 144 and 240, exactly 2:4:3:5. Each ten-unit tick interval is 80 pixels, consistent with the bars. Summaries and labels do not overlap, and a separate color highlights Q4.

Original SVG · Full-size PNG

Exact prompt, shared by the modes
Return only a complete, self-contained static SVG with viewBox="0 0 800 600". Design a polished dashboard card titled "Quarterly Revenue". Draw a vertical bar chart for Q1=12, Q2=24, Q3=18, Q4=30, in that left-to-right order. All four bars must share a zero baseline, and bar heights must be exactly proportional to the values. Show a y-axis labeled 0, 10, 20, 30 and show the value above each bar. Add summary labels "Total: 84" and "Best: Q4". Use a light background and readable typography. Do not use scripts, external assets or embedded images.

Chinese poster and layout constraints

Inspect: All six exact Chinese strings appear once; Clear hierarchy of heading, details and button; Adequate margins, no clipping or overlaps, recognizable bicycle。

Requested default (documented max)Historical first attempt · 2026-10-24
Kimi K3.1 Pro default: Chinese poster and layout constraints

First answer content 139.22s · Total 153.48s · 9982 completion tokens incl. reasoning

All six strings are exact and appear once, with complete readable Chinese glyphs. Font sizes of 56 for the title, 28 for time/place and 16 for the note provide the requested hierarchy. The information card, orange button and bicycle occupy separate areas, with adequate margins and no clipping or overlap.

Original SVG · Full-size PNG

Requested parameter · lowHistorical first attempt · 2026-10-24
Kimi K3.1 Pro low: Chinese poster and layout constraints

First answer content 34.17s · Total 51.24s · 3148 completion tokens incl. reasoning

All six exact Chinese strings appear once, with no extra wording, and the Chinese glyphs render clearly. Font sizes of 56 for the title, 30 for the time/place and 18 for the note establish the requested hierarchy. Information, bicycle icon and button have clear separation, adequate margins and no clipping or overlap.

Original SVG · Full-size PNG

Requested parameter · maxHistorical first attempt · 2026-10-24
Kimi K3.1 Pro max: Chinese poster and layout constraints

First answer content 111.64s · Total 122.09s · 7678 completion tokens incl. reasoning

The six required strings are exact and appear once each, with no additional wording or missing Chinese glyphs. Font sizes of 58 for the heading, 28 for time/place and 16 for the note meet the hierarchy. The button is well separated, the bicycle is recognizable, and all text and graphics remain within the canvas without crowding, overlap or clipping.

Original SVG · Full-size PNG

Exact prompt, shared by the modes
只输出一个完整、自包含的静态 SVG,viewBox="0 0 800 600"。设计一张清晰、精致的中文活动海报。必须且仅包含以下六段文字,每段出现一次,不能增删字或改写:主标题“周末骑行计划”;副标题“慢一点,看见城市”;时间“10月24日 09:00”;地点“滨江公园东门”;说明“自备头盔 · 全程12公里”;按钮文字“立即报名”。画一个简洁的自行车图标。主标题最大,时间地点次之,说明最小。背景浅色,留足边距,所有文字保持在画布内,不重叠,不使用脚本、外部素材或嵌入图片。

Vendor-reported · separate from TOKRACE tests

Kimi K3.1 Pro official benchmark figures

These five unmodified figures come from the Kimi K3.1 Pro launch page and are credited to Kimi / Moonshot AI. TOKRACE has not independently reproduced them. Tool access, harnesses and retry settings differ; consult the original footnotes before comparing them with AA or our small task sample.

Kimi official 14-benchmark overview

Kimi official 14-benchmark overview

Vendor results at maximum effort; mixed tools and harnesses, not reproduced by TOKRACE.

Kimi / Moonshot AI · 2026-10-23 · Source article · Original CDN image · Zoom / download

Official BenchCAD: with and without tools

Official BenchCAD: with and without tools

Voxel IoU on a 1,000-case subset: 92.7% with tools, 72.8% without.

Kimi / Moonshot AI · 2026-10-23 · Source article · Original CDN image · Zoom / download

Official finance workflow benchmarks

Official finance workflow benchmarks

OfficeQA Pro v2: 64.4; Frontier Finance: 58.6.

Kimi / Moonshot AI · 2026-10-23 · Source article · Original CDN image · Zoom / download

Official internal finance benchmarks

Official internal finance benchmarks

Internal modeling, research and business simulation versus K3.

Kimi / Moonshot AI · 2026-10-23 · Source article · Original CDN image · Zoom / download

Official hallucination stress tests

Official hallucination stress tests

Claim-level errors under stress tests; not everyday error rates.

Kimi / Moonshot AI · 2026-10-23 · Source article · Original CDN image · Zoom / download

What else is worth testing?

The following are proposed extensions, not results from this run. They test different failure modes rather than producing another overall score.

TestWhat to inspectEvidence to retain
Ball inside a rotating hexagonCollision boundaries, gravity, energy driftShort video plus physics checks
Responsive page from a screenshotLayout fidelity, typography, mobile overflowReference and 390/1440 px screenshots
Solar-system SVG animationJoints, trajectories, timing consistencyA fixed-duration recording and source
A consistent set of six iconsStroke weight, alignment, visual consistencyOne contact sheet and six originals
Multimodal chart readingValues, units and grounded conclusionsInput chart, exact answer and checks

How to read the official charts

The launch charts cover general reasoning, coding, CAD, finance and factuality. BenchCAD's 92.7% tool-enabled result and 72.8% tool-free result represent different conditions. Finance charts show domain-specific tasks, not a guarantee that every financial workflow is safe to automate.

The hallucination figures are errors on named benchmark sets, not a daily error rate for chat. Kimi's HLE with-tools score and a third-party HLE score can differ because tool access and evaluation rules differ. Keep the model, dataset, harness and budget attached to each number.

Stopped historical subset: 22 short text completions and one interruption

This earlier OpenAI-compatible batch remains separate from the new native Anthropic Messages batch. Its original stopping context and exact parameters remain in the immutable archive; no archived response is merged into the new comparison.

Download the entire stopped batch and its original context

The 22 completed requests cover 15 extraction and seven strict-format instruction tasks. All 22 pass those narrow checks. Mode counts are unequal (default 7, low 7, max 8), so this is neither a complete comparison nor evidence for coding or visual performance. The interruption is excluded from the pass denominator because its upstream result is unknown.

Archived endpoint / model:https://api.kimi.com/coding/v1 · k3.1-pro

Archived requests used a 12,288-token output limit and 600-second timeout with sampling parameters omitted. Recorded completed-request time totals 65.32s; this excludes the unknown interrupted duration and is not a speed ranking. Subscription quota has no asserted per-token invoice.

#1 · Contact extraction 1 · Requested: default (effort omitted) · Predetermined checks passed

2026-10-24T01:11:07.244Z · Total 3.031s · First content 3.029s · Input / completion / reasoning tokens 159 / 103 / 70

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:林桐,28 岁,目前居住在杭州。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"林桐","age":28,"city":"杭州","email":null}
#2 · Contact extraction 1 · Requested: low · Predetermined checks passed

2026-10-24T01:11:10.276Z · Total 2.421s · First content 2.416s · Input / completion / reasoning tokens 160 / 61 / 28

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:林桐,28 岁,目前居住在杭州。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"林桐","age":28,"city":"杭州","email":null}
#3 · Contact extraction 1 · Requested: max · Predetermined checks passed

2026-10-24T01:11:12.703Z · Total 3.935s · First content 3.935s · Input / completion / reasoning tokens 159 / 89 / 56

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:林桐,28 岁,目前居住在杭州。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"林桐","age":28,"city":"杭州","email":null}
#4 · Contact extraction 2 · Requested: max · Predetermined checks passed

2026-10-24T01:11:16.639Z · Total 2.685s · First content 2.685s · Input / completion / reasoning tokens 161 / 113 / 78

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:李明,36 岁,目前居住在成都。电子邮件为 li@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"李明","age":36,"city":"成都","email":"li@example.test"}
#5 · Contact extraction 2 · Requested: low · Predetermined checks passed

2026-10-24T01:11:19.327Z · Total 3.018s · First content 3.012s · Input / completion / reasoning tokens 162 / 136 / 101

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:李明,36 岁,目前居住在成都。电子邮件为 li@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"李明","age":36,"city":"成都","email":"li@example.test"}
#6 · Contact extraction 2 · Requested: default (effort omitted) · Predetermined checks passed

2026-10-24T01:11:22.346Z · Total 3.222s · First content 3.173s · Input / completion / reasoning tokens 161 / 98 / 63

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:李明,36 岁,目前居住在成都。电子邮件为 li@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"李明","age":36,"city":"成都","email":"li@example.test"}
#7 · Contact extraction 3 · Requested: default (effort omitted) · Predetermined checks passed

2026-10-24T01:11:25.572Z · Total 3.098s · First content 3.097s · Input / completion / reasoning tokens 159 / 107 / 74

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:陈夏,22 岁,目前居住在南京。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"陈夏","age":22,"city":"南京","email":null}
#8 · Contact extraction 3 · Requested: low · Predetermined checks passed

2026-10-24T01:11:28.671Z · Total 2.482s · First content 2.401s · Input / completion / reasoning tokens 160 / 67 / 34

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:陈夏,22 岁,目前居住在南京。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"陈夏","age":22,"city":"南京","email":null}
#9 · Contact extraction 3 · Requested: max · Predetermined checks passed

2026-10-24T01:11:31.156Z · Total 4.291s · First content 4.290s · Input / completion / reasoning tokens 159 / 112 / 79

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:陈夏,22 岁,目前居住在南京。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"陈夏","age":22,"city":"南京","email":null}
#10 · Contact extraction 4 · Requested: max · Predetermined checks passed

2026-10-24T01:11:35.451Z · Total 3.146s · First content 3.145s · Input / completion / reasoning tokens 163 / 115 / 79

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:周舟,41 岁,目前居住在苏州。电子邮件为 zhou@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"周舟","age":41,"city":"苏州","email":"zhou@example.test"}
#11 · Contact extraction 4 · Requested: low · Predetermined checks passed

2026-10-24T01:11:38.600Z · Total 2.193s · First content 2.176s · Input / completion / reasoning tokens 164 / 63 / 27

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:周舟,41 岁,目前居住在苏州。电子邮件为 zhou@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"周舟","age":41,"city":"苏州","email":"zhou@example.test"}
#12 · Contact extraction 4 · Requested: default (effort omitted) · Predetermined checks passed

2026-10-24T01:11:40.794Z · Total 3.895s · First content 3.894s · Input / completion / reasoning tokens 163 / 97 / 61

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:周舟,41 岁,目前居住在苏州。电子邮件为 zhou@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"周舟","age":41,"city":"苏州","email":"zhou@example.test"}
#13 · Contact extraction 5 · Requested: default (effort omitted) · Predetermined checks passed

2026-10-24T01:11:44.692Z · Total 2.807s · First content 2.807s · Input / completion / reasoning tokens 159 / 92 / 59

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:吴雨,30 岁,目前居住在武汉。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"吴雨","age":30,"city":"武汉","email":null}
#14 · Contact extraction 5 · Requested: low · Predetermined checks passed

2026-10-24T01:11:47.502Z · Total 2.606s · First content 2.527s · Input / completion / reasoning tokens 160 / 74 / 41

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:吴雨,30 岁,目前居住在武汉。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"吴雨","age":30,"city":"武汉","email":null}
#15 · Contact extraction 5 · Requested: max · Predetermined checks passed

2026-10-24T01:11:50.111Z · Total 4.639s · First content 4.639s · Input / completion / reasoning tokens 159 / 113 / 80

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:吴雨,30 岁,目前居住在武汉。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"吴雨","age":30,"city":"武汉","email":null}
#16 · Stable deduplication · Requested: max · Predetermined checks passed

2026-10-24T01:11:54.754Z · Total 2.241s · First content 2.223s · Input / completion / reasoning tokens 124 / 90 / 67

Exact prompt

把以下编号去重并保持首次出现的顺序:B2,A1,B2,C3,A1,D4。只输出用英文逗号连接的编号,不要空格、标题或解释。

Original answer

B2,A1,C3,D4
#17 · Stable deduplication · Requested: low · Predetermined checks passed

2026-10-24T01:11:57.048Z · Total 1.811s · First content 1.801s · Input / completion / reasoning tokens 125 / 55 / 32

Exact prompt

把以下编号去重并保持首次出现的顺序:B2,A1,B2,C3,A1,D4。只输出用英文逗号连接的编号,不要空格、标题或解释。

Original answer

B2,A1,C3,D4
#18 · Stable deduplication · Requested: default (effort omitted) · Predetermined checks passed

2026-10-24T01:11:58.861Z · Total 3.503s · First content 3.502s · Input / completion / reasoning tokens 124 / 119 / 96

Exact prompt

把以下编号去重并保持首次出现的顺序:B2,A1,B2,C3,A1,D4。只输出用英文逗号连接的编号,不要空格、标题或解释。

Original answer

B2,A1,C3,D4
#19 · Exact fields · Requested: default (effort omitted) · Predetermined checks passed

2026-10-24T01:12:02.366Z · Total 2.603s · First content 2.603s · Input / completion / reasoning tokens 125 / 77 / 53

Exact prompt

仅输出 JSON 对象,且恰好包含 status 和 count 两个字段。status 的值必须为字符串 "ready",count 必须为数字 3。不要 Markdown、解释或额外字段。

Original answer

{"status":"ready","count":3}
#20 · Exact fields · Requested: low · Predetermined checks passed

2026-10-24T01:12:04.971Z · Total 2.227s · First content 2.224s · Input / completion / reasoning tokens 126 / 54 / 30

Exact prompt

仅输出 JSON 对象,且恰好包含 status 和 count 两个字段。status 的值必须为字符串 "ready",count 必须为数字 3。不要 Markdown、解释或额外字段。

Original answer

{"status":"ready","count":3}
#21 · Exact fields · Requested: max · Predetermined checks passed

2026-10-24T01:12:07.201Z · Total 3.623s · First content 3.620s · Input / completion / reasoning tokens 125 / 72 / 48

Exact prompt

仅输出 JSON 对象,且恰好包含 status 和 count 两个字段。status 的值必须为字符串 "ready",count 必须为数字 3。不要 Markdown、解释或额外字段。

Original answer

{"status":"ready","count":3}
#22 · Ordered output · Requested: max · Predetermined checks passed

2026-10-24T01:12:10.827Z · Total 1.838s · First content 1.759s · Input / completion / reasoning tokens 116 / 69 / 42

Exact prompt

将数值 12、3、25、8 按从小到大排序。只输出 JSON 数组,元素为数字。不要解释或代码围栏。

Original answer

[3, 8, 12, 25]
#23 · Ordered output · Requested: low · Interrupted; upstream state unknown

2026-10-24T01:12:12.666Z · Total — · First content — · Input / completion / reasoning tokens — / — / —

Exact prompt

将数值 12、3、25、8 按从小到大排序。只输出 JSON 数组,元素为数字。不要解释或代码围栏。

Original answer

No response retained; upstream state unknown.

Original prompts, answers and code checks

Text and code evidence (JSON) · Static visual evidence · Modes, retries and animation evidence

Each record retains its prompt, response, requested model, returned model, parameters, token usage, completion status and timing. Public evidence excludes hidden reasoning content and credentials. The exact request budget takes precedence over the general methodology text.

Contact extraction 1 · Requested: default (effort omitted) · Quota error (429); no model answer scored

2026-10-24T01:41:49.321Z · Total 0.172s · First content — · Input / completion / reasoning tokens — / — / — · error

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:林桐,28 岁,目前居住在杭州。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:林桐,28 岁,目前居住在杭州。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true
}

HTTP 429: {"error":{"type":"rate_limit_error","message":"You've reached your 5-hour usage limit. Your quota will reset when the current 5-hour window ends. To continue now, purchase extra usage or upgrade your plan: https://www.kimi.com/membership/subscription?tab=quota"},"type":"error"}

Contact extraction 1 · Requested: low · Predetermined checks passed

2026-10-24T01:32:57.711Z · Total 3.394s · First content 3.314s · Input / completion / reasoning tokens 160 / 56 / 23 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:林桐,28 岁,目前居住在杭州。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"林桐","age":28,"city":"杭州","email":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:林桐,28 岁,目前居住在杭州。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Contact extraction 2 · Requested: low · Predetermined checks passed

2026-10-24T01:33:01.107Z · Total 3.553s · First content 3.553s · Input / completion / reasoning tokens 162 / 110 / 75 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:李明,36 岁,目前居住在成都。电子邮件为 li@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"李明","age":36,"city":"成都","email":"li@example.test"}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:李明,36 岁,目前居住在成都。电子邮件为 li@example.test。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Contact extraction 3 · Requested: low · Predetermined checks passed

2026-10-24T01:33:04.664Z · Total 3.946s · First content 3.945s · Input / completion / reasoning tokens 160 / 69 / 36 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:陈夏,22 岁,目前居住在南京。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"陈夏","age":22,"city":"南京","email":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:陈夏,22 岁,目前居住在南京。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Contact extraction 4 · Requested: low · Predetermined checks passed

2026-10-24T01:33:08.615Z · Total 3.580s · First content 3.578s · Input / completion / reasoning tokens 164 / 78 / 42 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:周舟,41 岁,目前居住在苏州。电子邮件为 zhou@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"周舟","age":41,"city":"苏州","email":"zhou@example.test"}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:周舟,41 岁,目前居住在苏州。电子邮件为 zhou@example.test。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Contact extraction 5 · Requested: low · Predetermined checks passed

2026-10-24T01:33:12.198Z · Total 3.610s · First content 3.555s · Input / completion / reasoning tokens 160 / 74 / 41 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:吴雨,30 岁,目前居住在武汉。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"吴雨","age":30,"city":"武汉","email":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:吴雨,30 岁,目前居住在武汉。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Stable deduplication · Requested: low · Predetermined checks passed

2026-10-24T01:33:15.817Z · Total 2.817s · First content 2.811s · Input / completion / reasoning tokens 125 / 47 / 24 · end_turn

Exact prompt

把以下编号去重并保持首次出现的顺序:B2,A1,B2,C3,A1,D4。只输出用英文逗号连接的编号,不要空格、标题或解释。

Original answer

B2,A1,C3,D4
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "把以下编号去重并保持首次出现的顺序:B2,A1,B2,C3,A1,D4。只输出用英文逗号连接的编号,不要空格、标题或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Exact fields · Requested: low · Predetermined checks passed

2026-10-24T01:33:18.637Z · Total 2.154s · First content 2.147s · Input / completion / reasoning tokens 126 / 65 / 41 · end_turn

Exact prompt

仅输出 JSON 对象,且恰好包含 status 和 count 两个字段。status 的值必须为字符串 "ready",count 必须为数字 3。不要 Markdown、解释或额外字段。

Original answer

{"status":"ready","count":3}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "仅输出 JSON 对象,且恰好包含 status 和 count 两个字段。status 的值必须为字符串 \"ready\",count 必须为数字 3。不要 Markdown、解释或额外字段。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Ordered output · Requested: low · Predetermined checks passed

2026-10-24T01:33:20.795Z · Total 1.819s · First content 1.773s · Input / completion / reasoning tokens 117 / 84 / 57 · end_turn

Exact prompt

将数值 12、3、25、8 按从小到大排序。只输出 JSON 数组,元素为数字。不要解释或代码围栏。

Original answer

[3, 8, 12, 25]
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "将数值 12、3、25、8 按从小到大排序。只输出 JSON 数组,元素为数字。不要解释或代码围栏。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Case and line breaks · Requested: low · Predetermined checks passed

2026-10-24T01:33:22.617Z · Total 2.585s · First content 2.578s · Input / completion / reasoning tokens 121 / 42 / 21 · end_turn

Exact prompt

按原顺序将 apple、pear、plum 转为英文大写,每行一个单词。总共三行,不要编号、标点、空行或解释。

Original answer

APPLE
PEAR
PLUM
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "按原顺序将 apple、pear、plum 转为英文大写,每行一个单词。总共三行,不要编号、标点、空行或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Required delimiter · Requested: low · Predetermined checks passed

2026-10-24T01:33:25.206Z · Total 2.318s · First content 2.305s · Input / completion / reasoning tokens 132 / 73 / 47 · end_turn

Exact prompt

提取下面三个工单号,保持顺序:工单 TX-103 已关闭;工单 TX-207 正在处理;工单 TX-309 待分配。只用英文竖线连接三个编号,不要空格或解释。

Original answer

TX-103|TX-207|TX-309
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "提取下面三个工单号,保持顺序:工单 TX-103 已关闭;工单 TX-207 正在处理;工单 TX-309 待分配。只用英文竖线连接三个编号,不要空格或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Grounded question answering 1 · Requested: low · Predetermined checks passed

2026-10-24T01:33:27.527Z · Total 2.166s · First content 2.165s · Input / completion / reasoning tokens 184 / 74 / 45 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:北区仓库今天收到 12 件货物,其中 3 件损坏,不可使用。下一次送货安排在周二。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":9,"nextDelivery":"周二","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:北区仓库今天收到 12 件货物,其中 3 件损坏,不可使用。下一次送货安排在周二。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Grounded question answering 2 · Requested: low · Predetermined checks passed

2026-10-24T01:33:29.698Z · Total 2.893s · First content 2.893s · Input / completion / reasoning tokens 184 / 95 / 66 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:南区仓库今天收到 20 件货物,其中 4 件损坏,不可使用。下一次送货安排在周三。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":16,"nextDelivery":"周三","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:南区仓库今天收到 20 件货物,其中 4 件损坏,不可使用。下一次送货安排在周三。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Grounded question answering 3 · Requested: low · Predetermined checks passed

2026-10-24T01:33:32.593Z · Total 2.380s · First content 2.248s · Input / completion / reasoning tokens 184 / 45 / 16 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:东区仓库今天收到 18 件货物,其中 6 件损坏,不可使用。下一次送货安排在周四。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":12,"nextDelivery":"周四","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:东区仓库今天收到 18 件货物,其中 6 件损坏,不可使用。下一次送货安排在周四。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Grounded question answering 4 · Requested: low · Predetermined checks passed

2026-10-24T01:33:34.977Z · Total 2.832s · First content 2.788s · Input / completion / reasoning tokens 184 / 85 / 56 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:西区仓库今天收到 25 件货物,其中 5 件损坏,不可使用。下一次送货安排在周五。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":20,"nextDelivery":"周五","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:西区仓库今天收到 25 件货物,其中 5 件损坏,不可使用。下一次送货安排在周五。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Grounded question answering 5 · Requested: low · Predetermined checks passed

2026-10-24T01:33:37.815Z · Total 2.374s · First content 2.367s · Input / completion / reasoning tokens 184 / 51 / 22 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:中区仓库今天收到 16 件货物,其中 2 件损坏,不可使用。下一次送货安排在周一。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":14,"nextDelivery":"周一","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:中区仓库今天收到 16 件货物,其中 2 件损坏,不可使用。下一次送货安排在周一。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Contact extraction 1 · Requested: max · Predetermined checks passed

2026-10-24T01:38:21.470Z · Total 4.261s · First content 4.260s · Input / completion / reasoning tokens 159 / 110 / 77 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:林桐,28 岁,目前居住在杭州。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"林桐","age":28,"city":"杭州","email":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:林桐,28 岁,目前居住在杭州。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Contact extraction 2 · Requested: max · Predetermined checks passed

2026-10-24T01:38:25.734Z · Total 4.311s · First content 4.310s · Input / completion / reasoning tokens 161 / 153 / 118 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:李明,36 岁,目前居住在成都。电子邮件为 li@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"李明","age":36,"city":"成都","email":"li@example.test"}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:李明,36 岁,目前居住在成都。电子邮件为 li@example.test。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Contact extraction 3 · Requested: max · Predetermined checks passed

2026-10-24T01:38:30.048Z · Total 3.784s · First content 3.779s · Input / completion / reasoning tokens 159 / 95 / 62 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:陈夏,22 岁,目前居住在南京。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"陈夏","age":22,"city":"南京","email":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:陈夏,22 岁,目前居住在南京。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Contact extraction 4 · Requested: max · Predetermined checks passed

2026-10-24T01:38:33.835Z · Total 4.676s · First content 4.675s · Input / completion / reasoning tokens 163 / 138 / 102 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:周舟,41 岁,目前居住在苏州。电子邮件为 zhou@example.test。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"周舟","age":41,"city":"苏州","email":"zhou@example.test"}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:周舟,41 岁,目前居住在苏州。电子邮件为 zhou@example.test。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Contact extraction 5 · Requested: max · Predetermined checks passed

2026-10-24T01:38:38.515Z · Total 4.787s · First content 4.787s · Input / completion / reasoning tokens 159 / 136 / 103 · end_turn

Exact prompt

从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。
资料:吴雨,30 岁,目前居住在武汉。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。

Original answer

{"name":"吴雨","age":30,"city":"武汉","email":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "从以下资料提取联系信息。只输出一个 JSON 对象,恰好包含 name、age、city、email 四个字段;age 为数字,未提供的 email 为 null。不要 Markdown 或解释。\n资料:吴雨,30 岁,目前居住在武汉。未提供电子邮件。历史备注提到曾在北京出差,不是现居城市。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Stable deduplication · Requested: max · Predetermined checks passed

2026-10-24T01:38:43.305Z · Total 3.630s · First content 3.629s · Input / completion / reasoning tokens 124 / 133 / 110 · end_turn

Exact prompt

把以下编号去重并保持首次出现的顺序:B2,A1,B2,C3,A1,D4。只输出用英文逗号连接的编号,不要空格、标题或解释。

Original answer

B2,A1,C3,D4
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "把以下编号去重并保持首次出现的顺序:B2,A1,B2,C3,A1,D4。只输出用英文逗号连接的编号,不要空格、标题或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Exact fields · Requested: max · Predetermined checks passed

2026-10-24T01:38:46.939Z · Total 3.575s · First content 3.542s · Input / completion / reasoning tokens 125 / 72 / 48 · end_turn

Exact prompt

仅输出 JSON 对象,且恰好包含 status 和 count 两个字段。status 的值必须为字符串 "ready",count 必须为数字 3。不要 Markdown、解释或额外字段。

Original answer

{"status":"ready","count":3}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "仅输出 JSON 对象,且恰好包含 status 和 count 两个字段。status 的值必须为字符串 \"ready\",count 必须为数字 3。不要 Markdown、解释或额外字段。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Ordered output · Requested: max · Predetermined checks passed

2026-10-24T01:38:50.519Z · Total 2.393s · First content 2.393s · Input / completion / reasoning tokens 116 / 92 / 65 · end_turn

Exact prompt

将数值 12、3、25、8 按从小到大排序。只输出 JSON 数组,元素为数字。不要解释或代码围栏。

Original answer

[3, 8, 12, 25]
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "将数值 12、3、25、8 按从小到大排序。只输出 JSON 数组,元素为数字。不要解释或代码围栏。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Case and line breaks · Requested: max · Predetermined checks passed

2026-10-24T01:38:52.918Z · Total 2.880s · First content 2.880s · Input / completion / reasoning tokens 120 / 125 / 104 · end_turn

Exact prompt

按原顺序将 apple、pear、plum 转为英文大写,每行一个单词。总共三行,不要编号、标点、空行或解释。

Original answer

APPLE
PEAR
PLUM
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "按原顺序将 apple、pear、plum 转为英文大写,每行一个单词。总共三行,不要编号、标点、空行或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Required delimiter · Requested: max · Predetermined checks passed

2026-10-24T01:38:55.800Z · Total 2.825s · First content 2.824s · Input / completion / reasoning tokens 131 / 98 / 72 · end_turn

Exact prompt

提取下面三个工单号,保持顺序:工单 TX-103 已关闭;工单 TX-207 正在处理;工单 TX-309 待分配。只用英文竖线连接三个编号,不要空格或解释。

Original answer

TX-103|TX-207|TX-309
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "提取下面三个工单号,保持顺序:工单 TX-103 已关闭;工单 TX-207 正在处理;工单 TX-309 待分配。只用英文竖线连接三个编号,不要空格或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Grounded question answering 1 · Requested: max · Predetermined checks passed

2026-10-24T01:38:58.636Z · Total 2.920s · First content 2.920s · Input / completion / reasoning tokens 183 / 149 / 120 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:北区仓库今天收到 12 件货物,其中 3 件损坏,不可使用。下一次送货安排在周二。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":9,"nextDelivery":"周二","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:北区仓库今天收到 12 件货物,其中 3 件损坏,不可使用。下一次送货安排在周二。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Grounded question answering 2 · Requested: max · Predetermined checks passed

2026-10-24T01:39:01.557Z · Total 3.362s · First content 3.361s · Input / completion / reasoning tokens 183 / 126 / 97 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:南区仓库今天收到 20 件货物,其中 4 件损坏,不可使用。下一次送货安排在周三。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":16,"nextDelivery":"周三","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:南区仓库今天收到 20 件货物,其中 4 件损坏,不可使用。下一次送货安排在周三。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Grounded question answering 3 · Requested: max · Predetermined checks passed

2026-10-24T01:39:04.922Z · Total 3.936s · First content 3.936s · Input / completion / reasoning tokens 183 / 178 / 149 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:东区仓库今天收到 18 件货物,其中 6 件损坏,不可使用。下一次送货安排在周四。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":12,"nextDelivery":"周四","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:东区仓库今天收到 18 件货物,其中 6 件损坏,不可使用。下一次送货安排在周四。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Grounded question answering 4 · Requested: max · Predetermined checks passed

2026-10-24T01:39:08.862Z · Total 3.552s · First content 3.552s · Input / completion / reasoning tokens 183 / 133 / 104 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:西区仓库今天收到 25 件货物,其中 5 件损坏,不可使用。下一次送货安排在周五。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":20,"nextDelivery":"周五","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:西区仓库今天收到 25 件货物,其中 5 件损坏,不可使用。下一次送货安排在周五。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Grounded question answering 5 · Requested: max · Predetermined checks passed

2026-10-24T01:39:12.420Z · Total 3.112s · First content 3.112s · Input / completion / reasoning tokens 183 / 121 / 92 · end_turn

Exact prompt

只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。
材料:中区仓库今天收到 16 件货物,其中 2 件损坏,不可使用。下一次送货安排在周一。仓库负责人姓名没有记载。旧计划曾写周日,已作废。

Original answer

{"usable":14,"nextDelivery":"周一","manager":null}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "只根据以下材料回答。输出恰好包含 usable、nextDelivery、manager 三个字段的 JSON 对象,不要额外文字。usable 是可用件数(数字),nextDelivery 是下一次送货时间(字符串),材料未说明的信息用 null,不能猜测。\n材料:中区仓库今天收到 16 件货物,其中 2 件损坏,不可使用。下一次送货安排在周一。仓库负责人姓名没有记载。旧计划曾写周日,已作废。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Money parsing without rounding invalid inputs · Requested: low · Predetermined checks passed · 18 planned checks

2026-10-24T01:33:40.191Z · Total 11.221s · First content 11.195s · Input / completion / reasoning tokens 184 / 652 / 525 · end_turn

Exact prompt

写 JavaScript 函数 parseCents(value)。value 必须是字符串:允许两端空白;只接受非负十进制金额,整数部分至少一位,小数最多两位;拒绝指数写法、符号、千分位、Infinity、空串、超过两位小数。返回整数分数,超过 Number.MAX_SAFE_INTEGER 则返回 null。非法类型或格式返回 null。不能把非法值四舍五入成合法值。只输出函数代码,不要 Markdown 或解释。

Original code

function parseCents(value) {
  if (typeof value !== 'string') return null;

  const input = value.trim();
  if (!/^\d+(?:\.\d{1,2})?$/.test(input)) return null;

  const [whole, fraction = ''] = input.split('.');
  const cents = BigInt(whole) * 100n + BigInt((fraction + '00').slice(0, 2));

  return cents > BigInt(Number.MAX_SAFE_INTEGER) ? null : Number(cents);
}

Executable checks

const cases=[['0',0],[' 12.30 ',1230],['0.29',29],['1.2',120],['0001.02',102],['1.234',null],['-1',null],['+1',null],['1e3',null],['',null],['.5',null],['1.',null],['Infinity',null],['1,000',null],[null,null],[1,null],['90071992547409.91',9007199254740991],['90071992547409.92',null]]; for (const [input,want] of cases) if(parseCents(input)!==want) throw Error('Failed '+JSON.stringify(input));
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "写 JavaScript 函数 parseCents(value)。value 必须是字符串:允许两端空白;只接受非负十进制金额,整数部分至少一位,小数最多两位;拒绝指数写法、符号、千分位、Infinity、空串、超过两位小数。返回整数分数,超过 Number.MAX_SAFE_INTEGER 则返回 null。非法类型或格式返回 null。不能把非法值四舍五入成合法值。只输出函数代码,不要 Markdown 或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Stable deduplication with special property names · Requested: low · Predetermined checks passed · 3 planned checks

2026-10-24T01:33:51.415Z · Total 4.674s · First content 4.598s · Input / completion / reasoning tokens 159 / 201 / 129 · end_turn

Exact prompt

写 JavaScript 函数 uniqueById(items)。items 是对象数组,每个对象有字符串 id 字段。保留每个 id 首次出现的原对象和原顺序,不修改输入或任何对象;空数组返回空数组。id 可为 __proto__、constructor 或空字符串。只输出函数代码,不要 Markdown 或解释。

Original code

function uniqueById(items) {
  const seen = new Set();
  const result = [];

  for (const item of items) {
    if (!seen.has(item.id)) {
      seen.add(item.id);
      result.push(item);
    }
  }

  return result;
}

Executable checks

const a={id:'__proto__',value:1},b={id:'constructor'},c={id:''},d={id:'x'};const input=Object.freeze([a,b,{id:'__proto__'},c,{id:''},d,{id:'constructor'}]);const got=uniqueById(input);if(got.length!==4||got[0]!==a||got[1]!==b||got[2]!==c||got[3]!==d)throw Error('Wrong identity or order');if(uniqueById([]).length!==0)throw Error('Empty');if(input.length!==7||a.value!==1)throw Error('Mutation');
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "写 JavaScript 函数 uniqueById(items)。items 是对象数组,每个对象有字符串 id 字段。保留每个 id 首次出现的原对象和原顺序,不修改输入或任何对象;空数组返回空数组。id 可为 __proto__、constructor 或空字符串。只输出函数代码,不要 Markdown 或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Interval merging, touching intervals and immutability · Requested: low · Predetermined checks passed · 5 planned checks

2026-10-24T01:33:56.091Z · Total 12.977s · First content 12.082s · Input / completion / reasoning tokens 161 / 583 / 398 · end_turn

Exact prompt

写 JavaScript 函数 mergeIntervals(intervals)。输入为有限数字组成的闭区间 [start,end] 数组,保证 start<=end,输入可能乱序。返回按 start 排序的合并闭区间,相接区间也合并;不要修改输入或任何内层数组,空数组返回空数组。只输出函数代码,不要 Markdown 或解释。

Original code

function mergeIntervals(intervals) {
  if (intervals.length === 0) return [];

  const sorted = intervals.slice().sort((a, b) => a[0] - b[0] || a[1] - b[1]);
  const result = [];
  let start = sorted[0][0];
  let end = sorted[0][1];

  for (let i = 1; i < sorted.length; i++) {
    const [nextStart, nextEnd] = sorted[i];
    if (nextStart <= end) {
      if (nextEnd > end) end = nextEnd;
    } else {
      result.push([start, end]);
      start = nextStart;
      end = nextEnd;
    }
  }

  result.push([start, end]);
  return result;
}

Executable checks

const cases=[[[[5,7],[1,3],[3,5]],[[1,7]]],[[[1,4],[2,3]],[[1,4]]],[[[0,0],[2,2]],[[0,0],[2,2]]],[[[-3,-1],[-2,0],[3,4]],[[-3,0],[3,4]]],[[],[]]];for(const [input,want] of cases){input.forEach(Object.freeze);Object.freeze(input);if(JSON.stringify(mergeIntervals(input))!==JSON.stringify(want))throw Error('Wrong merge');}
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "写 JavaScript 函数 mergeIntervals(intervals)。输入为有限数字组成的闭区间 [start,end] 数组,保证 start<=end,输入可能乱序。返回按 start 排序的合并闭区间,相接区间也合并;不要修改输入或任何内层数组,空数组返回空数组。只输出函数代码,不要 Markdown 或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "low"
  }
}
Money parsing without rounding invalid inputs · Requested: max · Predetermined checks passed · 18 planned checks

2026-10-24T01:39:15.536Z · Total 156.469s · First content 155.854s · Input / completion / reasoning tokens 183 / 9872 / 9706 · end_turn

Exact prompt

写 JavaScript 函数 parseCents(value)。value 必须是字符串:允许两端空白;只接受非负十进制金额,整数部分至少一位,小数最多两位;拒绝指数写法、符号、千分位、Infinity、空串、超过两位小数。返回整数分数,超过 Number.MAX_SAFE_INTEGER 则返回 null。非法类型或格式返回 null。不能把非法值四舍五入成合法值。只输出函数代码,不要 Markdown 或解释。

Original code

function parseCents(value) {
  if (typeof value !== "string") return null;

  const text = value.trim();
  if (!/^[0-9]+(?:\.[0-9]{1,2})?$/.test(text)) return null;

  const [whole, fraction = ""] = text.split(".");
  const cents = (whole + (fraction + "00").slice(0, 2))
    .replace(/^0+(?=[0-9])/, "");
  const max = String(Number.MAX_SAFE_INTEGER);

  if (
    cents.length > max.length ||
    (cents.length === max.length && cents > max)
  ) {
    return null;
  }

  return Number(cents);
}

Executable checks

const cases=[['0',0],[' 12.30 ',1230],['0.29',29],['1.2',120],['0001.02',102],['1.234',null],['-1',null],['+1',null],['1e3',null],['',null],['.5',null],['1.',null],['Infinity',null],['1,000',null],[null,null],[1,null],['90071992547409.91',9007199254740991],['90071992547409.92',null]]; for (const [input,want] of cases) if(parseCents(input)!==want) throw Error('Failed '+JSON.stringify(input));
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "写 JavaScript 函数 parseCents(value)。value 必须是字符串:允许两端空白;只接受非负十进制金额,整数部分至少一位,小数最多两位;拒绝指数写法、符号、千分位、Infinity、空串、超过两位小数。返回整数分数,超过 Number.MAX_SAFE_INTEGER 则返回 null。非法类型或格式返回 null。不能把非法值四舍五入成合法值。只输出函数代码,不要 Markdown 或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}
Stable deduplication with special property names · Requested: max · Quota error (429); no model answer scored · 3 planned checks

2026-10-24T01:41:52.009Z · Total 0.152s · First content — · Input / completion / reasoning tokens — / — / — · error

Exact prompt

写 JavaScript 函数 uniqueById(items)。items 是对象数组,每个对象有字符串 id 字段。保留每个 id 首次出现的原对象和原顺序,不修改输入或任何对象;空数组返回空数组。id 可为 __proto__、constructor 或空字符串。只输出函数代码,不要 Markdown 或解释。

Original code

Executable checks

const a={id:'__proto__',value:1},b={id:'constructor'},c={id:''},d={id:'x'};const input=Object.freeze([a,b,{id:'__proto__'},c,{id:''},d,{id:'constructor'}]);const got=uniqueById(input);if(got.length!==4||got[0]!==a||got[1]!==b||got[2]!==c||got[3]!==d)throw Error('Wrong identity or order');if(uniqueById([]).length!==0)throw Error('Empty');if(input.length!==7||a.value!==1)throw Error('Mutation');
Exact API request and budget
{
  "model": "k3.1-pro",
  "messages": [
    {
      "role": "user",
      "content": "写 JavaScript 函数 uniqueById(items)。items 是对象数组,每个对象有字符串 id 字段。保留每个 id 首次出现的原对象和原顺序,不修改输入或任何对象;空数组返回空数组。id 可为 __proto__、constructor 或空字符串。只输出函数代码,不要 Markdown 或解释。"
    }
  ],
  "max_tokens": 12288,
  "stream": true,
  "output_config": {
    "effort": "max"
  }
}

Incomplete response

Frequently asked questions

Is Kimi K3.1 Pro open weight?

As checked on October 24, 2026, the launch announcement promises weight release by November 4. A future release commitment does not establish that weights are downloadable today.

What is the Kimi K3.1 Pro API price?

The international platform lists $2 per million input tokens, $10 per million output tokens and $0.20 per million cache-hit input tokens for Pro. Highspeed lists $4 / $20 / $0.20. Cache writes are billed separately. These are official list prices, not a claim about our test provider's actual charges.

Can thinking be disabled?

Official documentation describes always-on thinking with low, high and max effort and default max. The native thinking.type=disabled probe returned HTTP 400. In our native tests, low/default/max identify requested parameter groups; server-side effort semantics were not independently verified.

Are benchmark figures TOKRACE results?

No. Artificial Analysis figures are independent third-party measurements, Kimi figures are vendor-reported, and TOKRACE original API task evidence is labeled separately with its exact endpoint, parameters and outputs.

Sources, image attribution and related reviews

Kimi K3.1 Pro official launch · Artificial Analysis launch analysis · Image sources, dimensions and SHA-256 manifest

AA figures belong to Artificial Analysis; official figures belong to Kimi / Moonshot AI. Original image files are reproduced for the requested model review with attribution; they are not TOKRACE-generated charts. The dataset license covers our own evidence, not these third-party images.

Compare the same task format: DeepSeek V4.1 Flash 1017 · MiniMax M3.1 Flash · Kimi K3.1 historical teaser

← All reports