菜单
The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Biznomad/agent-skills --skill agentmemory-rest-api命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Generate brand-faithful paid-ad creative for client products where the product label carries critical detail (ingredients, dose, claims, brand wordmark, certification badges). Pulls real product photos from the client's storefront, builds a 3-image reference stack including a label-tight crop, generates via Higgsfield Nano Banana Pro with character-level spelling locks, and verifies label fidelity at full resolution before approval. Use when: "make an ad", "ad creative", "Meta creative", "product hero", "lifestyle shot", "BOGO promo", "X for $Y promo", "Stories asset", "Reels creative", "client brand ad", "supplement ad", "skincare ad", "wellness brand ad", "label-perfect product photo". Required upfront: a client product visual specs memory file (`project_<client>_product_visual_specs.md`). If none exists, invoke the bootstrap step to create one before generating. Built from the May 2026 Example Brand BOGO + Mix-and-Match build, where Nano Banana Pro hit ~50% label fidelity on first try until the master prom
Build HTML-based social media carousel/post templates by iterating from a reference profile's aesthetic. Used when the user wants custom visual templates for Instagram/LinkedIn/Twitter content.
Reapply local modifications after a GSD update
基于 SOC 职业分类
正在显示 SKILL.md
| name | agentmemory-rest-api |
| description | The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP. |
| user-invocable | false |
REST is agentmemory's primary surface. MCP is a bridge on top of it. Every memory operation has an HTTP endpoint under http://localhost:3111/agentmemory/*.
# liveness
curl -fsS http://localhost:3111/agentmemory/livez
# save
curl -X POST http://localhost:3111/agentmemory/remember \
-H "Content-Type: application/json" \
-d '{"content":"chose JWT refresh rotation","concepts":["jwt-refresh-rotation"]}'
# recall
curl -X POST http://localhost:3111/agentmemory/smart-search \
-H "Content-Type: application/json" \
-d '{"query":"auth token strategy","limit":5}'
By default localhost is open and no auth is needed. When AGENTMEMORY_SECRET is set, every request needs Authorization: Bearer $AGENTMEMORY_SECRET. See agentmemory-config.
201, reads return 200, validation errors return 400.--port or --instance; streams, viewer, and engine derive from it.The full endpoint list with methods lives in REFERENCE.md, generated from src/triggers/api.ts.