[{"data":1,"prerenderedAt":348},["ShallowReactive",2],{"docs-page-en-\u002Fmemos_cloud\u002Fsupport\u002Ffaq":3,"surround-en-\u002Fmemos_cloud\u002Fsupport\u002Ffaq":334},{"id":4,"title":5,"avatar":6,"banner":6,"body":7,"category":6,"desc":326,"description":327,"extension":328,"links":6,"meta":329,"navigation":6,"path":330,"seo":331,"stem":332,"__hash__":333},"docs\u002Fen\u002Fmemos_cloud\u002Fsupport\u002Ffaq.md","Cloud FAQs",null,{"type":8,"value":9,"toc":315},"minimark",[10,20,23,28,31,49,56,58,62,65,68,94,96,100,103,113,116,140,157,159,163,166,187,194,196,200,203,214,221,223,227,230,233,253,255,259,274,280,282,286,289,305],[11,12,13,14,19],"p",{},"This page answers common questions about using MemOS Cloud. If you want to understand MemOS concepts such as RAG, open source deployment, private deployment, or memory scheduling, see ",[15,16,18],"a",{"href":17},"\u002Fmemos_cloud\u002Fintroduction\u002Ffaq","FAQ",".",[21,22],"br",{},[24,25,27],"h2",{"id":26},"which-document-should-a-new-user-read-first","Which document should a new user read first?",[11,29,30],{},"If you have not logged in to the console yet, choose the entry point based on how you plan to use MemOS Cloud:",[32,33,34,42],"ul",{},[35,36,37,38,19],"li",{},"If you want Agent tools such as Claude Code or Cursor to help with integration, start with ",[15,39,41],{"href":40},"\u002Fmemos_cloud\u002Fgetting_started\u002Fagent_usage","Use in Agents",[35,43,44,45,19],{},"If you want to call Cloud APIs from your own application, start with ",[15,46,48],{"href":47},"\u002Fmemos_cloud\u002Fgetting_started\u002Fquick_start","Integrate into Your App",[11,50,51,55],{},[15,52,54],{"href":53},"\u002Fapi_docs\u002Fstart\u002Fconfiguration","Configuration"," is more useful when you need to manage multiple projects, edit or delete projects, or understand how knowledge bases are bound to projects.",[21,57],{},[24,59,61],{"id":60},"what-is-the-relationship-between-api-keys-and-projects","What is the relationship between API Keys and projects?",[11,63,64],{},"Each project has its own API Key. When you call an API with a specific API Key, you can only access memories, messages, knowledge bases, and configuration under that project.",[11,66,67],{},"If data is visible in the console but not returned by the API, check:",[32,69,70,73,80],{},[35,71,72],{},"Whether the console project matches the project that owns the API Key.",[35,74,75,76,19],{},"Whether the request uses the same ",[77,78,79],"code",{},"user_id",[35,81,82,83,86,87,90,91,19],{},"Whether the search request uses an overly narrow ",[77,84,85],{},"filter",", ",[77,88,89],{},"knowledgebase_ids",", or a high ",[77,92,93],{},"relativity",[21,95],{},[24,97,99],{"id":98},"how-do-i-troubleshoot-authentication-or-permission-errors","How do I troubleshoot authentication or permission errors?",[11,101,102],{},"Start by checking the request header:",[104,105,111],"pre",{"className":106,"code":108,"language":109,"meta":110},[107],"language-text","Authorization: Token YOUR_API_KEY\n","text","",[77,112,108],{"__ignoreMap":110},[11,114,115],{},"Common issues include:",[32,117,118,124,131,134,137],{},[35,119,120,121,19],{},"Missing ",[77,122,123],{},"Authorization",[35,125,126,127,130],{},"Missing the ",[77,128,129],{},"Token"," prefix.",[35,132,133],{},"Incomplete API Key copied from the console.",[35,135,136],{},"API Key belongs to another project.",[35,138,139],{},"API Key is invalid, expired, or has no permission for the current resource.",[11,141,142,143,86,146,149,150,153,154,156],{},"If the response returns ",[77,144,145],{},"40100",[77,147,148],{},"40130",", or ",[77,151,152],{},"40132",", go back to ",[15,155,54],{"href":53}," and check the API Key and project.",[21,158],{},[24,160,162],{"id":161},"why-did-search-memory-or-chat-not-recall-knowledge-base-content","Why did Search Memory or Chat not recall knowledge base content?",[11,164,165],{},"First confirm that the knowledge base is bound to the current project and that the files have finished processing. Also check the API request:",[32,167,168,174,179],{},[35,169,170,171,173],{},"If ",[77,172,89],{}," is not provided, knowledge bases are not searched by default.",[35,175,170,176,178],{},[77,177,89],{}," is provided, make sure the IDs belong to knowledge bases accessible from the current project.",[35,180,170,181,183,184,186],{},[77,182,85],{}," is too narrow or ",[77,185,93],{}," is too high, relevant content may be filtered out.",[11,188,189,190,19],{},"For upload, binding, and processing status, see ",[15,191,193],{"href":192},"\u002Fmemos_cloud\u002Ffeatures\u002Fknowledge_base","Knowledge Base",[21,195],{},[24,197,199],{"id":198},"what-should-i-do-when-i-hit-quota-or-rate-limits","What should I do when I hit quota or rate limits?",[11,201,202],{},"First identify which limit was reached:",[32,204,205,208,211],{},[35,206,207],{},"Single input or output is too long: reduce the current input, history, or expected output.",[35,209,210],{},"API call quota is exhausted: wait for quota recovery or request more quota.",[35,212,213],{},"Too many requests in a short period: reduce request frequency and avoid repeated retries.",[11,215,216,217,19],{},"For quota details, see ",[15,218,220],{"href":219},"\u002Fmemos_cloud\u002Fsupport\u002Flimit","Quotas and Limits",[21,222],{},[24,224,226],{"id":225},"why-can-i-not-search-a-memory-immediately-after-writing-it","Why can I not search a memory immediately after writing it?",[11,228,229],{},"After memory is written, it still needs to be extracted, processed, and indexed. If you search immediately after writing, processing may not be finished yet.",[11,231,232],{},"Check:",[32,234,235,240,250],{},[35,236,237,238,19],{},"The write and search requests use the same ",[77,239,79],{},[35,241,242,243,86,246,149,248,19],{},"The request is not restricted by an overly narrow ",[77,244,245],{},"conversation_id",[77,247,85],{},[77,249,89],{},[35,251,252],{},"If asynchronous writing is used, wait for the task to finish before searching.",[21,254],{},[24,256,258],{"id":257},"what-should-i-check-when-delete-memory-fails","What should I check when Delete Memory fails?",[11,260,261,262,265,266,86,268,270,271,19],{},"When deleting individual memories, prefer ",[77,263,264],{},"memory_ids",". Do not use ",[77,267,245],{},[77,269,79],{},", or knowledge base IDs as ",[77,272,273],{},"memory_id",[11,275,276,277,279],{},"Only pass ",[77,278,79],{}," when you need to delete all memories for that user under the current project. This is a high-risk operation, so confirm the API Key, project, and user ID before running it.",[21,281],{},[24,283,285],{"id":284},"why-are-console-and-api-data-ranges-different","Why are console and API data ranges different?",[11,287,288],{},"Both the console and APIs isolate data by project. Inconsistent data ranges are usually caused by:",[32,290,291,294,299,302],{},[35,292,293],{},"The selected console project is different from the project that owns the API Key.",[35,295,296,297,19],{},"The API request uses a different ",[77,298,79],{},[35,300,301],{},"Extra filters are applied in the API request.",[35,303,304],{},"The knowledge base is not authorized for the current project.",[11,306,307,308,310,311,19],{},"If an API response returns a specific ",[77,309,77],{},", see ",[15,312,314],{"href":313},"\u002Fapi_docs\u002Fhelp\u002Ferror_codes","Error Codes",{"title":110,"searchDepth":316,"depth":316,"links":317},2,[318,319,320,321,322,323,324,325],{"id":26,"depth":316,"text":27},{"id":60,"depth":316,"text":61},{"id":98,"depth":316,"text":99},{"id":161,"depth":316,"text":162},{"id":198,"depth":316,"text":199},{"id":225,"depth":316,"text":226},{"id":257,"depth":316,"text":258},{"id":284,"depth":316,"text":285},"Troubleshoot common MemOS Cloud issues related to accounts, projects, API Keys, quotas, knowledge bases, and API calls.","This page answers common questions about using MemOS Cloud. If you want to understand MemOS concepts such as RAG, open source deployment, private deployment, or memory scheduling, see FAQ.","md",{},"\u002Fen\u002Fmemos_cloud\u002Fsupport\u002Ffaq",{"title":5,"description":327},"en\u002Fmemos_cloud\u002Fsupport\u002Ffaq","iqgB_87Pd-LJ397ob_27avGR2hOL3kEthxU_bZImu1Y",[335,343],{"title":336,"path":337,"stem":338,"icon":339,"framework":6,"module":6,"class":340,"target":-1,"active":341,"defaultOpen":341,"children":-1,"description":342},"Tool Memory","\u002Fmemos_cloud\u002Ffeatures\u002Ftool_calling","memos_cloud\u002Ffeatures\u002Ftool_calling","i-ri-tools-line",[],false,"Add tool calling information, integrating tool calling decisions, execution results, and usage trajectories into MemOS memory.",{"title":220,"path":219,"stem":344,"icon":345,"framework":6,"module":6,"class":346,"target":-1,"active":341,"defaultOpen":341,"children":-1,"description":347},"memos_cloud\u002Fsupport\u002Flimit","i-ri-shield-line",[],"Register and log in to enjoy free quota, facilitating quick experience and verification of memory functions.",1781768002888]