It appears that any requests made via the memory router are stored without an option to delete them -
url: 'https://api.supermemory.ai/v3/https://generativelanguage.googleapis.com/v1beta/models/gemini-2.5-flash:generateContent?key=${geminiApiKey}' method: 'POST', headers: { 'x-supermemory-api-key': supermemoryApiKey, 'x-sm-user-id': uniqueID, 'x-sm-conversation-id': uniqueID, 'Content-Type': 'application/json', }, body: { contents: contents, systemInstruction: { parts: [{ text: systemPrompt }] }, }, });
In order to start afresh, the conversation-id has to be rotated.
In the above case, I deleted all the memories and documents associated with the container tag 'uniqueID' (my supermemory dashboard had 0 memories/0 documents) however when I sent a new message via memory router, the older chat messages with the same conversationID were populated into supermemory (suspect this is from the memory router).
It appears that any requests made via the memory router are stored without an option to delete them -
url: 'https://api.supermemory.ai/v3/https://generativelanguage.googleapis.com/v1beta/models/gemini-2.5-flash:generateContent?key=${geminiApiKey}' method: 'POST', headers: { 'x-supermemory-api-key': supermemoryApiKey, 'x-sm-user-id': uniqueID, 'x-sm-conversation-id': uniqueID, 'Content-Type': 'application/json', }, body: { contents: contents, systemInstruction: { parts: [{ text: systemPrompt }] }, }, });In order to start afresh, the conversation-id has to be rotated.
In the above case, I deleted all the memories and documents associated with the container tag 'uniqueID' (my supermemory dashboard had 0 memories/0 documents) however when I sent a new message via memory router, the older chat messages with the same conversationID were populated into supermemory (suspect this is from the memory router).