KnowledgeMemory PricingBlogDocs DiscordGitHub Dashboard

Knowledge vs Memory

Ragionex ships two products through one API. They look similar - both answer questions semantically - but they solve opposite problems. Pick by asking one question: is the content fixed and shared, or does it grow as you work?

  • Knowledge is your documentation, pre-processed once and queried at runtime. It is shared, read-only, and the same for everyone using the key.
  • Memory is per-user context your agent writes as it goes. It is private to your key, persistent across sessions, and scoped by project.

Side by side

KnowledgeMemory
What it holdsPre-processed documentationFacts your agent saves at runtime
Who writes itPrepared ahead of timeYou / your agent, on the fly
Read or writeRead-only at query timeRead and write
Who can see itShared across the keyPrivate, per-user
LifetimeFixed until re-processedPersistent, grows over time
ScopingBy projectBy project
Auth keyShared rgx_knowledge_demo_ keyPer-user rgx_memory_ key
Main endpointPOST /v1/knowledge/searchPOST /v1/memory/write + /search

When to use Knowledge

Reach for Knowledge when the answer already exists in a document and you want ground truth, not a guess:

  • A support agent answering from your product docs.
  • A coding assistant grounded in a framework’s documentation.
  • Any case where you want a prepared, citeable answer with a source.

When to use Memory

Reach for Memory when the useful context is created during the work itself and must outlive the session:

  • Remembering a user’s preferences, decisions, and dead-ends.
  • Keeping per-project conventions an agent should follow next time.
  • Carrying context across sessions, projects, and different AI tools.

Use both together

They compose. A coding agent can query Knowledge for how a framework works, and read Memory for how this project chose to use it. One is the manual; the other is the project’s own history.

Start here

Try Quickstart: Knowledge to ask your first question, or Quickstart: Memory to save and recall your first fact.