Launched this week
AgentPrizm
AI agent memory + skills; API over REST + MCP
10 followers
AI agent memory + skills; API over REST + MCP
10 followers
AgentPrizm gives AI agents persistent, governed memory, reusable skills, and an audit receipt for every recall over REST and MCP. It resolves contradictions, tracks fact-validity windows, preserves history, and supports right-to-forget. Built for coding, support, sales, and regulated workflows. Try a live recall in the no-signup playground, then connect Claude Code, Cursor, OpenClaw, or any MCP-capable agent. Plus, it is already available as an OpenClaw skill on ClawHub.
honestly the fact-validity windows thing is super useful, but i'd love to see a visual diff tool in the playground so you can see how the memory evolves over time as new info comes in. would make debugging weird agent behavior way easier.
@dorttepeil49832 Thanks, İlyas — Gene here, founder and CEO of AgentPrizm. I’m imagining something similar to GitHub’s contribution map, but for an agent’s memory.
The map could show memory subjects across time, with different colors for different subjects and darker blocks showing greater activity or frequency. Clicking a block could reveal what changed and why a particular memory was used.
For something like competitor research, this could make it much easier to spot which subjects the agent has been following and when its understanding changed. Would you find the frequency of memory updates or the frequency of recalls more useful?
The fact-validity windows and audit receipts for every recall show real thought about what agents actually need in regulated environments. Glad someone is finally taking memory governance seriously instead of bolting it on later.
@eyuptozkan87200 Thanks, Eyüp — I appreciate that. This is exactly why we built validity windows and recall receipts into the foundation.
For something like an AI tutor or test-prep app, a student’s level and weak areas keep changing. If an old result is treated as current, the agent can confidently recommend the wrong lesson. The receipt lets a teacher or student see which memories shaped that recommendation.
Which would matter more to you: seeing why a lesson was chosen, or seeing when the student information became outdated?
the fact-validity windows and audit receipts show real thought about regulated use, not just a generic memory layer slapped together.
@abdulkadirgyt6 Thanks, Abdulkadir — I appreciate that. A marketing analytics agent is a good example: the same ROAS number can mean different things depending on the date range, ad account, currency, and attribution model.
Saving the number alone is not enough. The agent also needs to know where it came from, when it was valid, and what later replaced it. That’s where validity windows and recall receipts become useful.
For blended ROAS, would you want to drill down by account and source first, or compare how the metric changed over time?