API Reference / Strategy - Semantic Matcher Eval
Recompute calibration and persist a snapshot
post
https://api.intelig.ai/api/v1/intelig/strategy/initiatives/semantic-eval/confidence-calibration/recompute
Auth: Authorization: ApiKey <key> (an API key sent as
Bearer is rejected) or Authorization: Bearer <jwt>
for a dashboard session. operationId: recomputeCalibration
Runs the calibration above and stores the result. Unlike the read, this has an effect on live behaviour: the persisted threshold is the one the abstention gate applies to new proposals, and the stored snapshots are what the monthly adaptation loop trends over time.
Example request
curl -X POST "https://api.intelig.ai/api/v1/intelig/strategy/initiatives/semantic-eval/confidence-calibration/recompute" \
-H "Authorization: ApiKey $INTELIG_API_KEY"Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
matchType | string | no | — |
targetAccuracy | number (double) | no | — |
Response 200
application/json · ApiResponseLinkCalibrationSnapshot
| Field | Type | Description |
|---|---|---|
success | boolean | — |
message | string | — |
data | LinkCalibrationSnapshot | — |
Status codes
200— OK401— —429— —
Every response is wrapped in { success, message, data }. A 4xx means the request
is wrong — do not retry it unchanged. A 429 carries Retry-After in seconds.