Turbo Mode
Turbo endpoints provide faster responses with reduced processing for time-sensitive applications.
Turbo mode trades some features for speed. Entity extraction, knowledge graph updates, and detailed analytics are disabled.
Turbo Save
POST
/v1/turbo/saveFast content saving with minimal processing.
Request Body
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | Yes | Text content to save |
title | string | No | Content title |
tags | string[] | No | Tags for categorization |
Example
curl -X POST https://api.hypersave.io/v1/turbo/save \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"content": "Quick note: Follow up with client tomorrow",
"title": "Follow-up reminder"
}'Response
{
"success": true,
"documentId": "doc_abc123",
"processingTime": 45
}Turbo Ask
POST
/v1/turbo/askFast question answering with simplified processing.
Request Body
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Your question |
limit | number | No | Max memories to search (default: 5) |
Example
curl -X POST https://api.hypersave.io/v1/turbo/ask \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "What did I need to follow up on?"
}'Response
{
"success": true,
"answer": "You need to follow up with the client tomorrow.",
"processingTime": 120
}Performance Comparison
| Metric | Standard | Turbo |
|---|---|---|
| Save latency | ~500ms | ~50ms |
| Ask latency | ~2000ms | ~500ms |
| Entity extraction | ✅ | ❌ |
| Knowledge graph | ✅ | ❌ |
| Fact extraction | ✅ | ❌ |
| Full analytics | ✅ | ❌ |
When to Use Turbo Mode
Use Turbo Mode for:
- Real-time chat applications
- Quick note-taking
- High-frequency logging
- Time-sensitive operations
Use Standard Mode for:
- Important documents
- Content requiring entity extraction
- Building knowledge graphs
- Detailed analytics needs
⚠️
Content saved with Turbo mode can be enhanced later by re-processing, but this counts as additional API usage.