Memori Advanced Augmentation uses a quota system to manage memory storage and API usage. Understanding and managing your quota ensures uninterrupted service and optimal performance.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/MemoriLabs/Memori/llms.txt
Use this file to discover all available pages before exploring further.
Understanding Quotas
What Counts Toward Your Quota
Your quota tracks the number of memories stored across all entities, processes, and sessions:- Conversation turns - Each LLM interaction
- Augmented memories - Extracted facts, preferences, events, etc.
- Session data - Grouped interactions
- Embeddings - Vector representations for semantic search
Quota Tiers
Memori provides different quota tiers based on your authentication method:| Tier | Authentication | Max Memories | Best For |
|---|---|---|---|
| IP-Based | None (anonymous) | 1,000 | Testing, evaluation |
| Free Developer | API key | 100,000 | Development, small projects |
| Enterprise | Custom | Unlimited | Production deployments |
Checking Your Quota
Using the CLI
The fastest way to check your quota:Using the Dashboard
Visit app.memorilabs.ai to:- View real-time quota usage
- Browse all stored memories
- Analyze memory distribution by entity and process
- Track usage trends over time
- Export memory data
Programmatic Quota Checking
You can check quota programmatically by calling the Memori API:Quota Optimization Strategies
1. Efficient Entity and Process Attribution
Proper attribution prevents duplicate memories and improves organization:2. Session Management
Group related interactions into sessions to optimize memory storage:3. Recall Limits and Thresholds
Configure recall settings to balance performance and quota usage:Configuration options explained
Configuration options explained
- recall_embeddings_limit: Maximum number of embeddings to search during recall. Lower values = faster queries, potentially less accurate recall.
- recall_facts_limit: Maximum number of facts to include in augmentation. Lower values = less context, faster processing.
- recall_relevance_threshold: Minimum similarity score (0-1) for memories to be recalled. Higher values = more selective recall.
4. Environment Variables for Global Configuration
Set quota-related configuration via environment variables:Monitoring Quota Usage
Set Up Alerts
Create a monitoring script to alert when approaching quota limits:Integrate with CI/CD
Add quota checks to your deployment pipeline:Handling Quota Limits
What Happens When You Reach Your Quota
When you reach your quota limit:- Existing memories continue to be recalled normally
- New memories are not created (no errors, graceful degradation)
- You receive email notification (for API key holders)
- LLM interactions continue but without memory augmentation
Increasing Your Quota
Sign up for an API key
If you’re using IP-based quota, sign up for a free developer account:This increases your quota from 1,000 to 100,000 memories.
Request enterprise quota
For production deployments requiring >100,000 memories, contact the Memori team:
- Email: noc@memorilabs.ai
- Discord: discord.gg/abD4eGym6v
Use BYODB for unlimited storage
Deploy Memori BYODB (Bring Your Own Database) for unlimited memory storage:See BYODB Documentation for details.
Quota Best Practices
Do’s
✅ Use specific entity and process IDs - Better organization, easier monitoring ✅ Implement session management - Group related interactions efficiently ✅ Monitor quota regularly - Set up automated alerts at 80-90% usage ✅ Test with IP-based quota - Validate before committing to production ✅ Consider BYODB for production - Unlimited storage, full controlDon’ts
❌ Don’t use generic IDs - Avoidentity_id="user" or process_id="agent"
❌ Don’t ignore quota warnings - Plan ahead before hitting limits
❌ Don’t create unnecessary sessions - Each session consumes quota
❌ Don’t forget to claim CockroachDB clusters - 7-day expiration for unclaimed clusters
Troubleshooting Quota Issues
Quota Not Updating
Quota appears frozen or incorrect
Quota appears frozen or incorrect
Problem: The quota command shows outdated numbers.Solutions:
- Quota updates may have a brief delay (typically less than 1 minute)
- Check the dashboard for real-time data: app.memorilabs.ai
- Verify you’re checking the correct account:
Unexpected High Usage
Quota usage is higher than expected
Quota usage is higher than expected
Problem: Using more memories than anticipated.Investigation:
- Check the dashboard to see memory distribution by entity/process
- Look for generic IDs that might be capturing too much
- Review session management - are you creating too many sessions?
- Verify attribution is set correctly:
API Key Not Increasing Quota
Still seeing IP-based quota limits after setting API key
Still seeing IP-based quota limits after setting API key
Problem: API key doesn’t seem to increase quota.Solutions:
- Verify API key is set correctly:
- Ensure API key has no extra whitespace:
- Check for typos in the environment variable name
- Restart your application after setting the key
- Verify API key is valid:
Next Steps
CLI Usage
Learn all CLI commands for quota management
Performance Tuning
Optimize memory recall and quota efficiency
Dashboard
Monitor your quota in real-time
BYODB Setup
Deploy with unlimited storage