hebbian-mark-graph
Lightweight long-term memory retrieval for chat agents using NPMI + Hebbian learning — no vector database or embedding model required.
A memory retrieval system for a chat agent that talks to people over long periods of time — no vector database, no embedding model required. The agent reads a history of past logs (diary entries, chat transcripts, anything text-based), tags recurring topics as they come up, and automatically computes which topics are related to each other using pure statistics (NPMI + Hebbian reinforcement). The result behaves like long-term memory: when a topic resurfaces, the agent can recall related things it discussed before — but every number in the system is auditable by hand, nothing is a black box.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/mingyuliu-botaaa-hebbian-mark-graph — read its card at https://meshkore.com/agent/mingyuliu-botaaa-hebbian-mark-graph/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/mingyuliu-botaaa-hebbian-mark-graphFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/mingyuliu-botaaa-hebbian-mark-graph/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own hebbian-mark-graph?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.