Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Memory infrastructure for AI agents. Persistent storage, semantic recall, reputation tracking, cross-agent pools, and time-travel snapshots. Wallet-based aut...
Memory infrastructure for AI agents. Persistent storage, semantic recall, reputation tracking, cross-agent pools, and time-travel snapshots. Wallet-based aut...
This item is timing out or returning errors right now. Review the source page and try again later.
Use the source page and any available docs to guide the install because the item is currently unstable or timing out.
I tried to install a skill package from Yavira, but the item is currently unstable or timing out. Inspect the source page and any extracted docs, then tell me what you can confirm and any manual steps still required.
I tried to upgrade a skill package from Yavira, but the item is currently unstable or timing out. Compare the source page and any extracted docs with my current installation, then summarize what changed and what manual follow-up I still need.
Memory Infrastructure for Autonomous Agents Give your agent persistent memory that survives sessions. Store facts, preferences, decisions, and learnings - recall them semantically whenever needed. Advanced features include reputation tracking, cross-agent memory pools, and time-travel snapshots.
PropertyValueBase URLhttps://openclawdy.xyz/apiProtocolHTTPS (TLS 1.3)Data ResidencyUS-East (Vercel Edge + Qdrant Cloud)Request FormatJSON (Content-Type: application/json)Response FormatJSON
openclaw skill install openclawdy Or add to your agent config: skills: - url: https://openclawdy.xyz/SKILL.md name: openclawdy
OpenClawdy uses wallet-based authentication with message signing only.
Your agent signs a timestamp message with its wallet The signature + address are sent in request headers Server verifies the signature (no private key ever leaves your agent)
X-Agent-Address: 0x... # Your wallet address (public) X-Agent-Signature: 0x... # Signed message (proves ownership) X-Agent-Timestamp: 123... # Unix timestamp (ms, prevents replay)
OpenClawdy Auth Timestamp: {timestamp}
No private key access required - Only signing capability needed Wallet isolation - Each wallet gets its own isolated memory vault No env vars needed - Authentication is header-based No stored credentials - Signatures are verified per-request
AspectPolicyData StorageQdrant Cloud (managed vector DB) + PostgreSQLEncryptionTLS in transit, encrypted at restData IsolationEach wallet address has isolated storageRetentionData persists until explicitly deletedPool AccessOnly agents with pool_id can access pool dataExportFull vault export available via /memory/vaultDeletionPermanent deletion via DELETE endpointsNo TelemetryNo usage tracking or analytics collected
Store information for later retrieval. Endpoint: POST /api/memory/store Parameters: content (required): The information to remember type (optional): Category of memory - one of: fact, preference, decision, learning, history, context. Default: fact tags (optional): Array of tags for organization Example Request: { "content": "User prefers TypeScript over JavaScript", "type": "preference", "tags": ["coding", "language"] } Example Response: { "success": true, "data": { "id": "mem_abc123", "content": "User prefers TypeScript over JavaScript", "type": "preference", "tags": ["coding", "language"], "createdAt": "2025-02-10T12:00:00Z" } }
Retrieve relevant memories using semantic search. Finds memories by meaning, not just keywords. Endpoint: POST /api/memory/recall Parameters: query (required): What to search for limit (optional): Maximum results to return (1-20). Default: 5 type (optional): Filter by memory type Example Request: { "query": "programming language preferences", "limit": 3 } Example Response: { "success": true, "data": [ { "id": "mem_abc123", "content": "User prefers TypeScript over JavaScript", "type": "preference", "relevance": 0.95, "createdAt": "2025-02-10T12:00:00Z" } ] }
List recent memories without semantic search. Endpoint: GET /api/memory/list Parameters: type (optional): Filter by memory type limit (optional): Maximum results (1-100). Default: 20 offset (optional): Pagination offset. Default: 0
Delete a specific memory by ID. Endpoint: DELETE /api/memory/{id} Parameters: id (required): The memory ID to delete
Clear all memories in the vault. Use with caution - this is irreversible. Endpoint: DELETE /api/memory/vault
Export all memories as JSON for backup. Endpoint: GET /api/memory/vault
Get usage statistics for your agent. Endpoint: GET /api/agent/stats Example Response: { "success": true, "data": { "address": "0x1234...", "tier": "free", "memoriesStored": 150, "recallsToday": 45, "limits": { "maxMemories": 1000, "maxRecallsPerDay": 100 } } }
Track which memories lead to good outcomes. Store memories with reputation scores, update based on success/failure, recall memories ranked by proven effectiveness. Endpoints: POST /api/memory/reputation/store - Store with reputation POST /api/memory/reputation/recall - Recall by reputation rank POST /api/memory/reputation/update - Update reputation score store_ranked Request: { "content": "Use retry logic for API calls", "type": "learning", "reputation": 0.8 } recall_ranked Request: { "query": "error handling strategies" } Response: { "success": true, "data": [ { "id": "mem_xyz", "content": "Use exponential backoff for retries", "reputation": 0.92, "usage_count": 15, "success_rate": 0.93 } ] } update_reputation Request: { "memory_id": "mem_xyz", "outcome": "success", "impact": 0.8 }
Cross-Agent Memory Pools - Share knowledge between multiple agents. Create pools, store shared memories, recall from collective intelligence. Perfect for agent teams and swarms. Endpoints: POST /api/memory/pool/create - Create new pool POST /api/memory/pool/store - Store in pool POST /api/memory/pool/recall - Search pool GET /api/memory/pool/list - List accessible pools create Request: { "name": "research-team" } Response: { "success": true, "data": { "pool_id": "pool_abc123", "name": "research-team", "created_at": "2025-02-10T12:00:00Z" } } store Request: { "pool_id": "pool_abc123", "content": "Found bug in authentication module - fix applied", "type": "fact" } recall Request: { "pool_id": "pool_abc123", "query": "authentication issues" }
Memory Time Travel - Snapshot and restore agent memory states. Debug decisions by viewing past states, compare memory changes, restore to previous checkpoints. Essential for high-stakes agents. Endpoints: POST /api/memory/snapshot/create - Create snapshot POST /api/memory/snapshot/restore - Restore from snapshot GET /api/memory/snapshot/list - List snapshots POST /api/memory/snapshot/compare - Compare snapshots create Request: { "name": "before-major-update" } Response: { "success": true, "data": { "snapshot_id": "snap_abc123", "name": "before-major-update", "memory_count": 150, "created_at": "2025-02-10T12:00:00Z" } } restore Request: { "snapshot_id": "snap_abc123", "mode": "read_only" } Modes: read_only (view only) or overwrite (replace current state) compare Request: { "snapshot_id": "snap_abc123", "compare_to": "current" } Response: { "success": true, "data": { "added": 12, "removed": 3, "modified": 5, "unchanged": 130 } }
TypeUse ForExamplefactObjective information"Project uses Next.js 14"preferenceUser/agent preferences"User prefers dark mode"decisionPast decisions made"Chose PostgreSQL over MongoDB"learningLessons learned"This API requires auth header"historyHistorical events"Deployed v2.1 on Jan 15"contextGeneral context"Working on e-commerce project"
TierMemoriesRecalls/DayPoolsSnapshotsPriceFree1,00010013$0Pro50,000Unlimited1050$10/moEnterpriseUnlimitedUnlimitedUnlimitedUnlimitedCustom
All endpoints return consistent error format: { "success": false, "error": "Error message here", "code": "ERROR_CODE" } CodeDescriptionAUTH_REQUIREDMissing authentication headersAUTH_INVALIDInvalid signature or expired timestampNOT_FOUNDMemory/pool/snapshot not foundRATE_LIMITEDRate limit exceededVALIDATION_ERRORInvalid request parameters
OpenClawdy is available on the Agent Commerce Protocol (ACP). Other agents can purchase memory services directly: ServiceFeeDescriptionmemory_store$0.01Store a memorymemory_recall$0.02Semantic searchmemory_reputation$0.02Reputation operationsmemory_pool$0.03Pool operationsmemory_snapshot$0.05Snapshot operations
Website: https://openclawdy.xyz API Status: https://openclawdy.xyz/api/health Twitter: @openclawdy ACP Agent: OpenClawdy Memory
MIT
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.