Routing presets, prompts and usage

Configure eligible fallback, system templates, cost tags and datasets; do not treat retries as free replay.

Updated 2026-10-01

Before you start

This reference follows current LINK42 pages and permissions. Feature flags, roles, quotas and upstream state govern availability; changing a URL or model name does not bypass authorization.

Automatic routing and presets

Validate catalogue and key scope. Auto routing and @preset/slug choose eligible models; actual attempts and charges are recorded individually.

Function / field	Action and purpose	Verification and boundary
Auto strategies	Use eligible candidate models	Ranking is not a fixed latency/price guarantee.
Preset / order	Save an intentional fallback sequence	Fallback can change price, context and capability.
Provider preference	Use only exposed operator-supported controls	Hidden provenance does not make API IDs interchangeable.

Prompt templates and versions

Version stable system instructions and bind the needed keys. Validate output/cost before rollout or weight changes; omit passwords/customer secrets/upstream keys.

Function / field	Action and purpose	Verification and boundary
Version / binding	Record content and scope	Templates affect future input tokens and cost.
A/B weights	Compare consistent tasks/definitions	Small samples do not establish reliability.
Rollback	Select a verified version	Keep historical requests and price snapshots unchanged.

Tags, scores and exports

Tags attribute usage without changing prices or access. Only keys enabled for usage reading can access account reports.

Function / field	Action and purpose	Verification and boundary
Cost tags	Attribute project/environment usage	Respect count/length limits; avoid double-counting tag totals.
Scores	Evaluate owned requests/sessions	Follow score update/range rules.
CSV / JSONL	Export for reconciliation/evaluation	No fabricated bodies when capture was off; protect exported data.

Documentation