everos SDK, including async/await, error handling, and best practices.
Installation
Basic Usage (Sync)
Get started with the synchronous client:Async Client
For production applications handling concurrent requests:Async Mode with Task Polling
For long-running operations, useasync_mode=True to get a task ID and poll for completion:
Error Handling
The SDK provides typed exceptions for different error scenarios:Fire-and-Forget Message Storage
For non-critical message storage that should not block your main flow:Logging and Monitoring
Add observability to your EverOS integration:Best Practices Summary
Client Management
Client Management
- Create a single
EverOSorAsyncEverOSinstance and reuse it across your application - The SDK handles connection pooling and session management internally
- Use
AsyncEverOSfor production applications handling concurrent requests
Error Handling
Error Handling
- Use typed exceptions (
BadRequestError,NotFoundError,InternalServerError) for structured handling - The SDK includes built-in retry logic for transient failures
- Log failures with context for debugging
Performance
Performance
- Use
AsyncEverOSwithasyncio.gatherfor concurrent operations - Use fire-and-forget patterns for non-critical storage
- Use
async_mode=Truefor bulk imports to avoid blocking on memory extraction
Search
Search
- Use
method="vector"for semantic similarity search - Use
method="keyword"for exact term matching - Use
method="agentic"for LLM-guided search (may need longer timeouts) - Filter by
memory_typesto narrow results (e.g.,["episodic_memory", "profile"])
Next Steps
Batch Processing
Import conversation history at scale
Agentic Retrieval
LLM-guided search with longer timeouts