Mem0 Platform ↗
Save useful context and recall it across your sessions.
Before you connect
Provision an API key and decide which user or agent owns each memory.
Our integration playbook
Design memory boundaries before saving context
INFRASTRUCTURE FOR THE AGENT ECONOMY
Agent memory services for AI agents
Retain useful information between sessions.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
100 available services15 capability categoriesOpen discovery · no login
Choosing agent memory for your task
Choose a memory scope and retention policy before saving data. Test retrieval in the intended user or agent context.
Before you proceed: A recalled fact may be stale; verify it against current evidence when needed.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with Agent memory
3 services · Catalog updated 2026-10-27 · See each listing’s review date
Zep ↗
Build persistent context from conversations and business activity.
Before you connect
Create a Zep account and API key; map application users and authorize which records may be ingested.
Our integration playbook
Check that memory changes when the underlying facts change
Upstash Redis ↗
Maintain shared task state in a managed Redis database.
Before you connect
Create and authorize a database, or use the documented agent scratch-database route. Scratch databases expire after 72 hours unless claimed through an Upstash account.
Our integration playbook
Define key ownership and expiry before sharing agent state
Explore related capabilities
Browse all service tags →NO BROWSER REQUIRED
Discover. Inspect.
Connect.
Search for a capability, then follow the listing’s siteGuide link for our original integration playbook: selection advice, workflow, acceptance checks and recovery steps. The complete playbook is in the page HTML, so you can fetch it without JavaScript or a login.
GET /api/agent-services?capability=email GET /api/agent-services?interface=mcp GET /api/agent-services?payment=x402-wallet GET /api/agent-services?payment=mpp-wallet GET /api/agent-services?payment=no-payment GET /api/agent-services?id=e2b
Full catalog: /data/agent-services.json
Manifest: /.well-known/agent-services.json
Choose your next service with the facts in hand.
Find the tools you need
You are here to get something done. Find a mailbox for your messages, a browser for your web tasks, a sandbox for your code, or a wallet for approved payments.
Check what you need from your owner
Inspect the setup requirements before connecting. You may need your owner to create an account, grant OAuth consent, fund a wallet, or provide a website login.
Confirm your payment path
Check whether usage is free, billed to a provider account or uses a documented x402 or MPP wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.