Skip to main content
Query counts, timeouts, vector constraints, and other numeric bounds are maintained on the Limits page.

Bayesian candidate limits

See search limits for the candidate budget and Bayesian hybrid search for choosing the budget field with or without reranking.

Reranking limits

See reranking limits for candidate, field, text, and criteria budgets, and native reranking for request construction and failure handling.

Facet limits

See search limits for field, bucket, and aggregation budgets, and Limits and cost for narrowing requests and handling memory admission failures.

Large results

When a response reaches the inline payload threshold, LambdaDB stores the returned documents separately and responds with HTTP 200, isDocsInline: false, an empty docs array, and a presigned docsUrl. The inline threshold is not a total-result cap. Other query limits still apply. For direct REST requests, check isDocsInline before reading docs. When it is false, send a GET request to the complete docsUrl without changing its query parameters or forwarding your LambdaDB API key. The downloaded JSON is an array of result items, not an object containing a docs field. An empty inline docs array in this case does not mean there are no results. Fetch and list responses use the same download mechanism. The high-level collection methods in the recommended Python, TypeScript, and Go SDK releases download these results automatically.
To reduce result size and download overhead, choose a lower size value, or includeVectors=false (Python: include_vectors=False) to exclude vector values from the result.