OpenTusk

- Free (default)— No credit card required. 100 MB hot-cache storage, 10 MB max file size, no Walrus durability. TogglePay per uploadin the upload dialog to send larger files (up to 100 MB) with Walrus durability included, billed per file in WAL on Sui.
- Subscriptions— Developer ($9/mo), Scale ($49/mo), Enterprise ($499/mo) — larger storage, larger file sizes, longer hot retention, and Walrus durability for all files.
- Pay per Upload (PPU)— On the Free plan, opt any individual upload into PPU for that one file. Paid plans don’t expose PPU since storage is included.

OpenTusk is built around a single owner account that controls access for many agents. You set up once, then connect as many AI agents as you need — each with its own identity and scoped permissions.

You (owner) ├── Create account at app.opentusk.ai or via CLI ├── Create vaults (shared or public) ├── Generate invite codes for each agent │ ├── Agent 1 (Claude Code) │ └── opentusk login --invite-code otinv_... │ └── Gets its own API key + Sui keypair │ ├── Agent 2 (Cursor) │ └── opentusk login --invite-code otinv_... │ └── Gets its own API key + Sui keypair │ └── Agent 3 (OpenClaw / CI pipeline / custom bot) └── opentusk login --invite-code otinv_... └── Gets its own API key + Sui keypair

Each agent gets a unique API key and Sui keypair, scoped to your account. You control what each agent can access — specific vaults, specific scopes, with automatic expiry.

- Upload and download files— persist conversation context, generated artifacts, reports, code, or any binary data
- Organize with vaults and folders— each agent can work in its own vault or share vaults with other agents
- Read and write inline content— sandboxed agents (Claude Desktop) that can’t touch the filesystem can still create and read files through inline content tools
- Collaborate through shared vaults— multiple agents and humans can read and write to the same encrypted vault, with access controlled by Sui addresses on-chain
- Manage trash and lifecycle— soft-delete, restore, and track file sync status across hot cache and Walrus

- Vault creation and visibility— only the owner can create and delete vaults
- Access grants— the owner decides which Sui addresses (agents or humans) can access each shared vault
- API key and invite management— create, scope, and revoke agent credentials at any time
- Billing and quotas— all storage usage rolls up to the owner’s plan

Pay-per-call people + life-in-days knowledge API for AI agents (x402 on Base)

Agent Memory as a Service with x402 USDC micropayments on Base blockchain — provides memory_store, memory_recall, memory_forget, and memory_stats tools.

Persistent memory for AI assistants and coding agents across ChatGPT, Claude, Cursor, and other MCP-compatible tools.

Local Work Model for AI agents that learns from real outcomes.

Adaptive MCP memory system for AI applications. Learns which retrieval strategies work for your data, scores results using cognitive science models, builds a knowledge graph automatically, and validates every parameter change against real query history before adopting it. Patent pending.

Auditable, self-improving knowledge & memory for AI agents over MCP — citation-enforced answers and a replayable why-trace, self-hosted on Postgres.

MCP-native memory layer for Claude Code, Cursor, Cline, Continue, and 16 other AI tools. Hybrid search (BM25 + pgvector + graph), self-hosted on Supabase + Vercel, 100% MIT, no paywall.

Paid remote MCP endpoint for persistent AI agent memory, site analytics, pricing, checkout status, and search-readiness operations.

Governed persistent memory for AI agents.