Troubleshooting
Limits
This page outlines the technical limitations and supported formats in the Mixpeek platform. Understanding these constraints will help you optimize your implementation and plan resource usage effectively.
Supported File Types
Mixpeek supports a wide range of file formats across different media types for both object storage and query inputs.| Format | Extensions | Max Size | Notes |
|---|---|---|---|
| Plain Text | .txt, .md, .csv | 100MB | UTF-8 encoding recommended |
| Rich Text | .rtf, .docx, .odt | 100MB | Formatting is preserved during processing |
| Markup | .html, .xml, .json | 50MB | Structure is parsed and indexed |
| Code | .py, .js, .java, etc. | 25MB | Language-specific tokenization is applied |
Rate Limits
API rate limits are in place to ensure fair usage and system stability. Different tiers provide varying levels of access.Free Tier
500 requests per day
100 requests per hour
5 concurrent requests
Business Tier
50,000 requests per day
5,000 requests per hour
100 concurrent requests
Enterprise Tier
Custom limits
Priority processing
Dedicated resources
Rate Limit Headers
Rate Limit Headers
All API responses include rate limit information in the headers:The
X-RateLimit-Reset value is a Unix timestamp indicating when the rate limit window resets.Rate Limit By Endpoint
Rate Limit By Endpoint
Some endpoints have specific rate limits:
| Endpoint | Max Requests (Free) | Max Requests (Developer) | Max Requests (Business) |
|---|---|---|---|
/search | 100/hour | 500/hour | 2,500/hour |
/upload | 50/hour | 250/hour | 1,000/hour |
/processing | 20/hour | 100/hour | 500/hour |
Rate Limit Exceeded
Rate Limit Exceeded
When rate limits are exceeded, the API returns a
429 Too Many Requests response with a Retry-After header indicating the number of seconds to wait before retrying.Size Limits
Storage Limits
Free Tier: 5GB storage
Developer Tier: 100GB storage
Business Tier: 1TB storage
Enterprise Tier: Custom storage limits
Processing Limits
Maximum batch size: 100 objects
Maximum pipeline complexity: 10 extractors
Maximum processing time: 30 minutes per object
Namespace & Collection Limits
Query Limits
Search Query Limits
Search Query Limits
| Parameter | Free Tier | Developer Tier | Business Tier | Enterprise Tier |
|---|---|---|---|---|
| Max query length | 256 chars | 1,024 chars | 4,096 chars | 8,192 chars |
| Max results per query | 100 | 500 | 1,000 | 5,000 |
| Max filter complexity | 3 conditions | 10 conditions | 25 conditions | 50 conditions |
Batch Processing Limits
Batch Processing Limits
| Operation | Free Tier | Developer Tier | Business Tier | Enterprise Tier |
|---|---|---|---|---|
| Max batch upload size | 10 objects | 50 objects | 100 objects | 500 objects |
| Max batch processing | 5 objects | 25 objects | 100 objects | Custom |
| Max parallel pipelines | 2 | 5 | 10 | Custom |
Best Practices
Optimize File Sizes
Compress files when possible before uploading to reduce storage usage and processing time.
Batch Operations
Use batch operations whenever possible to minimize API calls and stay within rate limits.
Implement Retry Logic
Add exponential backoff retry logic to handle rate limit errors gracefully.
Monitor Usage
Regularly check your usage metrics to avoid hitting limits unexpectedly.
Exceeding storage or rate limits may result in temporary service restrictions. If you anticipate higher usage, consider upgrading your plan or contacting support for temporary limit increases.