API Typed Decisions

Typed Decisions API

Use a validated decision profile in the Panel, or a separate qualified engine scorer, to request a typed result rather than free-form prose. These are distinct routes and contracts.

Panel decision profile

1. In API workbench (/rust/api), inspect GET /api/decisions. Its profiles array provides saved profiles, which must have a validated, active artifact before inference.
2. Choose POST /v1/decisions in Endpoint catalog, open its link under Browse every endpoint (generated from route registration) (administrators can also use Generate examples). Replace PROFILE_ID with the selected profile ID, and supply a state value. The state union uses kind of text or json, together with the corresponding value.
3. For administrator testing, select the same route in In-page tester, enter the JSON, and press Send test request. The Panel calls its real decision-profile owner. An inactive or absent profile returns a refusal instead of fabricated probabilities.
4. Use Run guided checks, choose Typed decision from script, enter Profile ID and Decision state, then Check guide. The guide verifies profile inventory and sends the request. The manual script-preparation step remains outstanding.

{"id":"PROFILE_ID","state":{"kind":"text","value":"Sample"}}

A successful Panel response includes profile, decision and action_allowed; the score is meaningful only for the profile's currently selected, validated artifact. A missing profile, unloaded engine or unvalidated artifact must not be treated as a valid decision.

Separate engine scorer

POST /v1/decide uses an engine-side scorer. It accepts a decision kind such as choice, a state, a question and options. The Panel workbench provides copyable examples under ENGINE_URL, but this route is not in the native Panel gateway or its in-page tester. See Panel API.

Control reference

Control	Help text
Typed decisions (api.decide)	Use a validated active Panel profile or a separately qualified engine scorer; unbound calls fail.