Stage R trigger dry-run: would this description surface for these prompts
Score prompts through the SAME hybrid retrieval smart_route uses (RRF over
dense pgvector + sparse tsvector — shared code, not a re-implementation) against
your org’s live index PLUS the candidate. Per prompt: {score, rank, would_surface} where would_surface means the candidate lands in top_k.
This is the measured half of the description-revision loop: revise the
description, dry-run the trigger prompts, publish when recall holds. Embedding
calls are cost-tagged trigger_dryrun in the usage ledger.
Authorizations
Enter your API key (e.g. dai_sk_test_key_001)
Headers
Cookies
Body
{"prompts": [str, ...] (≤25, each ≤2000 chars), and EITHER "skill_id" (live skill — its stored description/embedding; add "description" to test a REVISED description against the live index) OR "description" (+ optional "name") for an ad-hoc/unpublished candidate. Optional "top_k" (default = the router's production top_k).
Response
Successful Response