Common questions about MemoryMarket, AMP, installation, and publishing.
A memory pack is a signed directory of typed memory files — your operating principles, style rules, product facts, playbooks. When installed via the mm CLI, packs extract to ./.memorymarket/<slug>/ in your project. Your agent's own rules files are never modified.
AMP (Agent Memory Protocol) is an open protocol for packaging and transferring AI agent memory. MemoryMarket is the default registry that implements it. The protocol owns the pack format, signing contract, and install mechanics. It is registry-agnostic and MIT licensed.
A manifest.json (pack metadata and Ed25519 signature), an agents.md routing table that tells the consuming agent which files to load for which task type, and a memory/ directory of capability files organized by domain (copy-voice.md, ops-tools.md, operating-principles.md). Primitive types mix freely within each file.
Goal (intent or operating principle), claim (factual assertion), directive (instruction — what to do or not do), and demonstration (approved example showing a pattern). Each primitive is a single inline-tag line: [directive must, org, permanent] In all copy, never use em dashes. Tested on 79 real memory files across 9 locations — 0% unclassifiable.
Every pack is signed with Ed25519 before publishing. The signature covers the manifest fields plus SHA-256 hashes of every pack file. The registry re-verifies on every install — tampered packs are rejected before they reach your machine. Verify offline with either CLI: mm verify <dir> --public-key <file> or amp verify <dir> --public-key <file>.
No. Via the mm CLI, mm install extracts to ./.memorymarket/<slug>/ and appends a managed block to your host rules file (CLAUDE.md, AGENTS.md, .windsurfrules, etc.). Your existing content is untouched above and below it. For Cursor, mm install writes a standalone .cursorrules file containing only the pack block. mm uninstall <slug> removes the block and the .memorymarket/slug/ directory atomically.
Claude Code, Codex, OpenClaw, Cursor, and Windsurf. OpenClaw packs always install user-scope (into ~/.openclaw/workspace/AGENTS.md) regardless of the --scope flag, since OpenClaw uses a home-directory workspace rather than per-project rules files.
Yes. Use mm install @user/pack --scope user to install to ~/.memorymarket/ instead of your project directory.
Install the CLI (npm install -g memorymarket), then ask your agent: "Install the MemoryMarket skills from the npm package." Two skills ship in the package: /mm-publish (creators — create the draft on memorymarket.co/sell/new first, then paste the pack-id into /mm-publish --pack-id <uuid> and the agent assembles + signs + publishes) and /mm-add (buyers — install someone else's pack into your workspace). Drafts are always created on the web; the skill never creates them.
During beta, 100% of each sale (minus Stripe fees) goes to the creator. Payouts are processed via Stripe.
Refunds are handled by support. Contact us and we'll review your purchase.