Recipes
A pattern is a shape you apply to your own problem. A recipe is a finished job. Each page below names the capability, the exact labels or schema, the thresholds, and the code that ties them together.
Pick a recipe by the problem
The recipes
Three independent calls return a queue, a priority score, and an urgency flag for one ticket.
Extract the invoice header fields, verify the number and total, build a review queue.
Rate harm on a described scale. Route the uncertain band to a human reviewer.
Score every retrieved passage against the question. Keep, drop, or flag by probability.
Describe each PII type, then redact with the start and end offsets the response returns.
Classify level by level. Stop the descent when confidence drops below your bar.
By capability
Use this index when you already know the capability and want a worked example.
By input type
Every recipe runs against https://api.milliseconds.ai as written. No API key is required during the launch period.
Before you copy one
Three things change per deployment. Read them once, then adapt each recipe.
- Your label and statement wording drives accuracy. Writing good statements and labels gives the rules.
- The thresholds in each recipe are starting points, not defaults. Set your own bands with thresholds and confidence routing.
- A
textholds at most 20,000 characters, andtextsholds at most 32 items. Limits and rate limits lists every other field limit.