All capabilities
Every capability is one POST to https://api.milliseconds.ai, with text or texts in the body. No API key is required during the launch period.
The seven capabilities
Latencies are wall-clock curl measurements from a laptop on 2026-09-16, over short inputs of 55 to 198 characters. They include TLS and internet transit. The two model families set the split: classifier calls land near 1 s, extractor calls near 0.5 s. How it works names the two models and gives the measured capacity table.
The routing rules
- You need a true or false verdict on one claim: use yes-no.
- You need exactly one label from a fixed set: use classify.
- You need an ordered level, such as severity or sentiment: use rate.
- You need a value that the text states, with its offsets: use answer for one question. Use extract for a whole record, or entities for every occurrence.
- You already hold a value and must check it against the text: use verify.
Choosing a capability works through the near-miss pairs, such as yes-no against classify with two labels.
What every capability shares
Send text up to 20,000 characters, or texts with up to 32 items. Send one key, never both.
texts returns {"results":[...]} in input order. statements and questions batch inside one call.
Probabilities, confidence as 1 minus normalized entropy, scores, and character offsets.
Pick an act, confirm, or escalate band per action. Raise the bar with the blast radius.
Each capability response carries two headers: x-input-chars, the number of input characters, and x-input-tokens, the input tokens billed for this call. Cost scales with everything you send: the text plus the labels, statements, questions, or schema. See Pricing.
Writing the labels and statements
The label text is what the model reads. "yes" and "no" carry no meaning for it. Write text that describes the case.
A when_true of "yes" with a when_false of "no" measurably flipped a correct yes-no answer to wrong. The probability fell from 1 to 0.004 on the same input. Writing good statements and labels shows the wording that works.
Try each one
Open the API Reference tab and use the Try it panel on any endpoint page. The panel needs no key and no setup. The Playground guide gives a worked example per capability and names what to read in each response.