Change a knowledge learning setting
Store one deployment-wide knowledge learning setting its rule accepts, audited with the value before and after. Requires platform:manage.
v2 compatibility notes
POST /api/v2/knowledge/settings/set with { key, value } stores one learning setting, as Save does on the Console Knowledge › Settings page. It needs platform:manage and answers 200 with the settings in force after the write, the same view as Read the knowledge learning settings. MCP hosts call it through forge_call_operation with operationId setKnowledgeSetting.
key is one of the editable knowledge.* keys (knowledge.gradeRankWeights, knowledge.evidenceLogCap, knowledge.provenThresholds, knowledge.signalPrecedence, knowledge.ratingSignal, knowledge.failedRunSignal, knowledge.distillationMinClusterSize, knowledge.distillationMinScore, knowledge.distillationScopes, knowledge.staleAfterDays, knowledge.memoryPromotionRetrievalThreshold, knowledge.federatedDefaultTrustWeight) or chat.ltmPromotionThreshold. value is required and may be any JSON value the key’s rule accepts. Settings are deployment-wide: the write changes how knowledge learns for every tenant. Changing a proven threshold, the signal precedence, the rating bands or the failed-run setting re-derives every case’s outcome state under the new value.
The write is stamped with the credential and recorded as a platform_setting_set audit event naming platform_setting:<key> and the value before and after. A change made in the Console is recorded the same way.
platform:manage is an approve-and-administer scope: it is in no default scope set, a Personal key carrying it expires sooner, and a Forge agent’s key is never granted it.
Idempotency-Key to retry safely: a repeat writes and audits nothing again. The settings have no home to recheck, so a repeat returns the recorded response while the credential still holds platform:manage, and 403 once it does not. The same key with a different body answers 422 idempotency_key_reuse. See Knowledge settings and re-embed replay.
Authorizations
Headers
1–255 printable ASCII characters. A repeat with the same key and request never runs the write again, a 5xx included. It returns the first response (Idempotency-Replayed: true) only when the route's current authorization policy permits disclosure; otherwise 409 idempotency_result_unavailable. Honoured for External App JWTs and platform and MCP keys; an External App's static companion key is not protected.
1 - 255Body
Response
The learning settings in force after the write
The knowledge learning settings in force, deployment-wide: every value resolved to a valid one, the chat message to long-term memory threshold, which keys carry a stored override (overriddenKeys), a stored value its rule keeps only part of (partlyApplied) or none of (ignoredKeys), and when each stored key was last written.

