Kimi K3.1 Pro is here. Give it a small job with a visible finish.

The announcement, in one useful question

Moonshot introduces Kimi K3.1 Pro with a one-million-token context window and a faster Highspeed variant. A context window is the amount of material a model can consider in one interaction. The company highlights coding and 3D work. For a beginner, the useful question is smaller: can this assistant turn a brief into something you can open, inspect and change?

Imagine that your friends keep missing local events because the details are scattered across messages. A simple weekend planner could help: one page with event names, dates and known prices. You could ask for a draft in a normal chat, or ask a tool-capable assistant to make a local page. Both routes start with the same written input and the same checks.

Give it three events, including one missing fact

Use this invented input sheet. Event A is a drawing club on 7 November 2026, admission free. Event B is a film night on 8 November 2026, admission £5. Event C is a repair meetup on 7 November 2026, with admission price not supplied. These are classroom events, not real listings. Keep the labels A, B and C so you can match every output to its input.

Your brief is: make a local page that shows those three events, sorts them by date, and filters them by free, paid or price unknown. For equal dates, keep the input order. Include a visible label when the price is missing. Do not invent venues or booking links. A chat-only assistant can return a table and a page specification; an assistant with suitable tools can create the file in a practice folder.

Check the boring details before the beautiful ones

Before seeing an answer, write the expected order: A, C, B. The free filter should show only A. The paid filter should show only B. The unknown-price filter should show only C. If C appears under free, the page has quietly converted missing information into a promise. A bright design cannot repair that mistake.

Now change just one input: the organiser confirms that C costs £2. The date order should remain A, C, B. The free filter should still show A, while the paid filter should show C and B in that order. The unknown group should be empty. Keep the first input sheet and the revised one. You have created a small repeatable check that another assistant can run after an update.

Turn a token price into a deliberately small worksheet

A token is a piece of text used for model processing and billing; it is not reliably one word. Suppose, purely for this worksheet, that one API attempt bills 10,000 ordinary input tokens and 2,000 output tokens. At USD 2 and USD 10 per million respectively, input costs 10,000 ÷ 1,000,000 × 2 = USD 0.02. Output costs 2,000 ÷ 1,000,000 × 10 = USD 0.02. The two components total USD 0.04.

Using the listed Highspeed rates with exactly those same invented quantities gives USD 0.04 for input and USD 0.04 for output, or USD 0.08. This comparison holds the quantities fixed so you can see the effect of the rates. Actual attempts can use different amounts, including billable reasoning. Tools, cache operations, taxes where applicable and your checking time still belong in a real budget. No call was made to obtain these examples.

Suppose three fictional attempts each incur the first USD 0.04 bill and only the last one produces an acceptable page. The model charges across the attempts would total USD 0.12 for that accepted result. Keep unsuccessful attempts in the calculation. If you already have a suitable subscription, start with its existing allowance; the API worksheet does not describe how that subscription counts use.

A useful first project can stay on your own computer

Ask for the three-event page, not a complete social network. Stop when you can open the output, check each filter and explain the missing-price rule. Save the brief, both input versions, the result and a short list of the checks actually performed. If you only designed the page, label it a specification. If you built it, record which browser and assistant you used.

That little folder is enough to compare a second assistant later. Give it the same task and inputs, and judge the same visible behaviours. A different model may need fewer corrections, produce a clearer interface or cost less to run. Those are observations you can make. You do not have to infer them from a launch slogan, and you do not need to publish a website to find out.