Get collector/dedup settings
const url = 'http://localhost:11044/api/v1/config/collector';const options = {method: 'GET', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url http://localhost:11044/api/v1/config/collector \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'Returns the effective memory-dedup collector settings for this world: enabled, dryRun, matcher, similarityThreshold and cron are resolved against the deployment defaults (never null); the five multi-signal weights are returned as stored (null means the matcher’s own default applies).
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”Effective collector settings
The memory-dedup collector settings in force for this world. The first five are resolved against the deployment defaults and are never null; the five weights are returned as stored, where null means the matcher’s own default applies.
object
When the sweep runs, as a Spring six-field cron expression
Whether the sweep reports what it would merge instead of merging it
Whether the dedup sweep runs at all
Weight of shared entities. Null means the matcher’s own default
Weight of shared grounding. Null means the matcher’s own default
Weight of lexical overlap. Null means the matcher’s own default
Which matcher decides that two memories are the same
Example
multi-signalWeight of shared provenance. Null means the matcher’s own default
How similar two memories must be to merge, in [0, 1]
Weight of vector similarity. Null means the matcher’s own default

