Dedup cross-extractor fragmented entity nodes for the workspace (CORE-GRAPH-CANONICAL-DEDUP-1).
Collapses same-name entity-node fragments (the same entity split across >1 node because two extractors
disagreed on its type -> divergent canonical_key -> the write-time dedup missed them) into one node,
precision-first. Unblocks ensemble alias disambiguation, since a fragmented canonical makes
resolve_aliases(disambiguate=true) abstain. Workspace-scoped (tenant isolation). Opt-in, default-off.
Recommended ensemble sequence: dedup-entities then resolve-aliases?disambiguate=true.
Parameters:
dry_run: If true, report the dedup plan without mutating the graph.require_structural_confirmation: If true (default), a same-name pair merges only on T0 (same Wikidata QID), T1 (same canonical_key), or T2 (>= tau_min shared typed entity-neighbors). If false, exact same-name clusters merge on name alone once T0/T1 fail (riskier disjoint-edge-tail recovery).
Returns:
merged_clusters: same-name fragment (sub-)clusters collapsed into one nodemerged_nodes: total fragment nodes merged awayredirected_edges: external edges moved onto survivors (0 when dry_run)abstained_clusters: clusters left untouched (no confident identity tier, the disjoint-edge tail)dry_run: echoes the request flag- plus scope context (
workspace_id,user_id)
Send Authorization: Bearer <token>. The token is either a Clerk session JWT or a SmartMemory API key (prefix sm_live_, sm_test_, or legacy sk_).
In: header
Query Parameters
Response Body
application/json
application/json
curl -X POST "https://example.com/memory/graph/dedup-entities"null{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}Create Zettel Note
Create a zettel note directly. Bypasses /memory/add's LLM-classification pipeline so the consumer's explicit `memory_type=zettel` intent is preserved. Tags and title land on the [Zettel] row's top-level properties, queryable via /by-tag and /by-property.
Delete Agent
Delete (deactivate) an agent. Removes keys whose stored user_id is the agent ID in this tenant. Keys previously created from the Web Agents page belong to the calling human and are not revoked here. Those keys require separate revocation.