Pick one from a list
Ask a question with a fixed set of answers, up to 26 of them. You get back the one it chose and how far ahead it was. Handy for sorting, routing, matching and triage.
See it decide an access request →Piko turns the model server you already run into something that answers a fixed list of choices. It never writes a paragraph you then have to trust — it picks from your list, tells you how far ahead the winner was, and stays silent when the two were too close to call.
Every closed question has a shape. Piko supports exactly three, and returns the reading that tells you whether to act on the answer.
Ask a question with a fixed set of answers, up to 26 of them. You get back the one it chose and how far ahead it was. Handy for sorting, routing, matching and triage.
See it decide an access request →A yes or no question you write yourself, or one with no wording at all. It answers with the chance the statement is true, and stays quiet when the two sides are too close.
See it judge whether a move is fatal →Ask for a grade from 1 to 5 and get a single number that already averages every grade it weighed. Even a hesitant grader still gives you something to act on.
See it grade how urgent a case is →One dial sets how far ahead the winner has to be before it answers. Raise it and it answers less often but is right more often. Staying silent is a valid answer here, not a failure.
See it abstain on a hard call →Every answer comes with the distance between the top two choices. A wide gap means go ahead. A narrow one is your cue to look at it yourself.
See the gap on two similar names →The same question can be asked about an image or a recording. Show it a photo or a sound and it answers from what it sees or hears, not from a caption someone wrote.
See it read an image →It can only answer with one of the choices you wrote down. It has no way to produce a name, a number or a plan you did not offer, which is what makes the answer safe to automate on.
See it choose where a piece lands →Point it at the model server you already run, the same one answering your chats. Nothing leaves your machine, and every answer can be re-checked later without it.
See a decision come off your own server →Run one question on two machines and a small share of answers move. Above a high confidence almost none do, so that is the part worth storing, not the exact number.
See a question with a stable answer →Send one situation and up to 26 questions. Each one comes back with its own answer and its own confidence, in a single request.
See three questions on one screen →Ask for a single letter instead of a paragraph. That is the whole trick — and it is why the answer can be measured instead of believed.
You give it the situation and the options, labelled A. B.
C. It is never asked to invent an answer — only to point at one of yours.
One short request, one letter back. Alongside it comes the odds the machine gave every option, which is the part that would normally be thrown away.
The chosen option, the gap to the runner-up, and a clear signal when the machine was not sure enough to answer at all. Nothing is written down on a refusal.
The same question can be asked about a paragraph, a photograph or a recording. The model answers from what it sees or hears, not from a caption someone wrote. Here is what each kind of request costs, measured on a single card.
A document, a rendered board, a conversation: anything already written down.
A photograph, a screenshot, a diagram. Read as raw pixels, never as alt text.
A recording of speech, music or an ambient scene, answered from the waveform.
One model, gemma-4-12b, serves all three modalities on a single rented card at €0.35/hour. A decision reads a single output token, so the cost is the prompt: an image adds about 270 tokens over plain text and roughly 30 ms, a recording about 106 tokens and 14 ms. The price quoted already carries a 30% margin.
An ordinary model writes its answer out word by word, and you wait for the whole thing before you can trust it. Piko reads a single letter it was going to produce anyway — and the reading is done the moment that letter lands.
Not free-form writing, and nothing whose answers you cannot write down yourself. Where a single letter says nothing, Piko refuses to pretend otherwise.
The program works out every legal move and describes each one in a sentence; the machine points at one. When it is not sure enough, the game asks again instead of guessing.
Open the Pacman example →The code lists every placement the piece could take and what each one would cost. The machine points at one, and the reading says whether the choice was close.
Open the Tetris example →One question picks the next action from a list; two more track whether it is still on goal and whether it is stuck. The same machine also writes the words to type.
Open the agent example →The whole vehicle and the whole map go in as one question, and the next move comes back from a short menu. A safety rule written in code always outranks the model.
Open the drone example →One observation becomes a table of what is on the screen; the machine chooses the operation and the element to act on, and only the typing is left to words. The same request carries the question and the reading.
Open the browser example →JevPilot is a real drive, deciding several times a second: the road, the traffic and the lane it is in go in as one question, and a steering and a speed come back from a short menu — each with the gap that says whether the call was close.
See a tick-by-tick decision →Send one situation and as many questions as you like, and get an answer, a confidence and a refusal back for each — or point the client you already use straight at it.