Get the cheaper context recipe the outcomes support
The last recipe-tuning run of the active version. Once a
version’s calibration is fitted, and then at most every 30 days, a
run tests cheaper variants of the recipe against your labelled
outcomes, using the contexts already stored with your evaluations,
sent to the same engine on the same terms. A smaller recipe is
cheaper only where it moves answers to a smaller size class: trimming
tokens within a class saves nothing. A variant qualifies only when it
is meaningfully cheaper and neither its held-out log loss nor its
accuracy is worse beyond noise. suggestion is the cheapest that
qualifies, with the exact definition to post as a new version;
nothing is applied for you. On a template prefix, the template’s
judgment, tuned on its tenants’ pooled outcomes.
On every plan. Below Team the numbers are shown, and recipe,
removed and definition are null with plan_required beside
them.
Authorizations
An organization API key. Keys carry a role (read_write or
read_only) and may be restricted to a namespace prefix such as
acme/*, or to one namespace such as acme/prod/tenant_1. A prefix
matches on a / boundary: acme/prod/tenant_1* covers
acme/prod/tenant_1 and everything under acme/prod/tenant_1/,
never acme/prod/tenant_12.
Path Parameters
A namespace name, or a template prefix ending in /*, with any
/ sent as %2F: acme%2Fprod%2Ftenant_123 or acme%2Fprod%2F*.
A namespace name, or a template prefix: a namespace path ending in
/*, such as acme/prod/*, which every namespace under acme/prod/
inherits judgments from. Up to 256 bytes. Never exactly
. or .., which a URL path can't carry.
1 - 256^(?!\.\.?$)[A-Za-z0-9._:/-]+(/\*)?$A judgment, attribute or threshold name. Names are path segments in field references, so they never contain ..
1 - 128^[A-Za-z0-9_-]+$Response
The suggestion, or why there is none; status says which.
The cheaper context recipe a version's outcomes support, from its last recipe-tuning run, or why there is none.
x >= 1not_run: no run yet;reasonsays why.running: a run is testing smaller recipes.ready:suggestionholds a cheaper recipe.none: the last run found none;reasonsays why.
not_run, running, ready, none Why there is no suggestion. Not run: awaiting_run (the next
calibration run starts it), too_few_outcomes (no calibration fit
yet), no_recipe, no_smaller_recipe (nothing to drop or halve,
such as a single field), composite, inherited (the template has
the suggestion). None: nothing_to_save (every answer is already
standard, the smallest size class),
no_cheaper_recipe (nothing moves enough answers to a smaller size
class to be meaningfully cheaper), accuracy_would_drop,
too_few_outcomes,
cost_cap (the run stopped at this month's limit) or
superseded (the engine's model changed during the run). Null
while running and when ready.
awaiting_run, too_few_outcomes, no_recipe, composite, inherited, nothing_to_save, no_smaller_recipe, no_cheaper_recipe, accuracy_would_drop, cost_cap, superseded What status and reason mean, in a sentence.
One sentence when ready, such as "A context recipe 42% cheaper per answer, with accuracy unchanged within noise on 312 labelled answers."
One smaller recipe, measured against the current one on the same
labelled answers and engine epoch. Apply it by posting definition
as a new version and activating it through its shadow report.
When the last run ended. Null before one has.
The earliest the nightly calibration starts the next run, 30 days after the last started. Null before one has.
Set below Team, where the recipe itself is withheld.