Skip to main content
Synap publishes very few hard numbers. The two below are the ones the SDK actually enforces. Everything else (latency, throughput, rate-limit ceilings) depends on your Instance, your use-case, and your workload, and is best read off the Dashboard as you run.

​
SDK timeouts

The SDK ships with two default timeouts, one per retrieval mode: Both are configurable per call via SDKConfig.timeouts.

​
Retrieval modes

sdk.conversation.context.fetch() accepts mode="fast" (default) or mode="accurate".
  • fast: lower-latency path. Searches the vector store only; it never traverses the graph.
  • accurate: higher-quality path. Searches the vector store, traverses the graph, and additionally runs LLM subquery decomposition and reranking on the candidate set.
Both modes pull from the same underlying memory; accurate simply spends more compute to widen and re-order the result set. On either mode, passing precision_level="medium" further reduces response time by skipping an additional relevance-refinement pass, trading some precision. Recall isn’t impacted, since the same candidate memories are searched, but outputs are less precisely filtered.

​
Where to see live numbers

Per-Instance latency, request volume, and rate-limit headroom are visible in Dashboard → Usage. Use that view for capacity planning rather than any number quoted in docs. Your workload is the source of truth. Document/message size and rate ceilings are likewise per-Instance rather than fixed platform constants, and are read off the same Dashboard → Usage view. If you need a ceiling raised, contact [email protected].

​
Behavior under load

  • The SDK auto-retries transient errors (rate limits, service-unavailable) using RetryPolicy with exponential backoff. You generally don’t need to wrap calls in your own retry loop.
  • When retries are exhausted on a rate-limited call, the SDK raises RateLimitError. Catch it to fall back gracefully or surface a user-visible error.
  • If you consistently hit RateLimitError for an Instance, your per-Instance ceiling is tuneable. Contact [email protected].

​
Status and monitoring