Start free, then move to monthly plans when your memory API traffic grows. Credits cover adds and searches from the same workspace balance. Reads are always free.
Prototype on Hobby, then move to monthly Stripe plans with higher included memory operations. Reads are always free.
| Plan | Hobby Freeno card required | StarterMost popular $19per month | Growth $79per month | Pro $249per month | Enterprise Customannual commitment |
|---|---|---|---|---|---|
| Credits | 10,000 add requests and 1,000 retrieval requests per month | 50,000 add requests and 5,000 retrieval requests per month | 200,000 add requests and 20,000 retrieval requests per month | 500,000 add requests and 50,000 retrieval requests per month | Committed-use credit pricing with volume discounts |
| Best for | Prototyping memory for a single agent or side project | Small apps moving from prototype to live traffic | Teams scaling memory across production users | Higher-volume apps that need advanced usage visibility | Teams with compliance, scale, or data-residency requirements |
| Metering | Full API access from day one: adds, search, and free reads | Operation-level usage and credit balance in the dashboard | Usage analytics, API keys, webhooks, and billing controls | Advanced analytics and higher included monthly capacity | Dedicated capacity, SLAs, and priority on the roadmap |
| Support | Community support on GitHub issues and discussions | Community support | Email support from the engineers who built the engine | Private Slack support | Private channel, onboarding help, and migration assistance |
| Platform access | mem0-compatible REST API, dashboard, and one workspace | Hosted FishMem API, dashboard, and one workspace | Multiple projects, hybrid retrieval, graph and temporal recall | Unlimited projects with production-ready controls | Everything in Pro, plus SSO and audit controls |
| Data ownership | Memories stay workspace-scoped; export or delete them at any time. | Memories stay workspace-scoped; export or delete them at any time. | Memories stay workspace-scoped; export or delete them at any time. | Memories stay workspace-scoped; export or delete them at any time. | Memories stay workspace-scoped; export or delete them at any time. |
Credits are consumed per API operation: 2 for an inferred add, 1 for a raw add or search, and reads are free. Self-hosting the open-source engine costs nothing.
Cost depends on the operation. Inferred adds run the fact-extraction pipeline; raw adds store as-is. Reads and lists are free.
memories.add (inferred)
per request
2
memories.add (raw)
per request
1
memories.search
per request
1
memories.get / list
per request
0
| Operation | Unit | Credits per request |
|---|---|---|
| memories.add (inferred) | per request | 2 |
| memories.add (raw) | per request | 1 |
| memories.search | per request | 1 |
| memories.get / list | per request | 0 |
Reads and list operations are always free, so retrieval-heavy agents stay cheap. Operation-by-operation usage is broken out in the dashboard.
Common questions about credits, billing, refunds, and the open-source engine.
Each plan includes a monthly credit bucket. Credits are deducted per API operation: 2 for an inferred add, 1 for a raw add, 1 for a search, and 0 for reads and lists. Failed requests are not billed.
Yes. Starter, Growth, and Pro are monthly Stripe subscriptions. Hobby remains free and does not require a card.
Hobby is free. Starter, Growth, and Pro add higher monthly capacity, support, and usage visibility. Enterprise is available for custom limits, SSO, and compliance needs.
Monthly subscription credits reset each billing period. Reads and list operations remain free.
Payments are processed through Stripe — credit cards, Apple Pay, Google Pay, and region-specific methods like WeChat Pay / Alipay where available.
Payment issues and refund requests are reviewed by support. Credits already spent on completed API requests are not refundable.
No. The open-source memory engine is free to self-host on your own infrastructure. Paid plans meter the hosted FishMem API, dashboard, keys, and billing layer.
Metered API requests return a 402 Payment Required when your balance reaches zero — reads keep working. Upgrade your plan or contact support to resume adds and searches.
