Introducing the Batch API for large-scale async workloads like offline corpus indexing and evals. Key benefits: - Simpler workflows: No queue, retry, and rate limit management with a 12-hour completion window - Higher throughput and limits: Up to 1 GB files, 100K inputs per batch, and 1B tokens per org - Cost savings: 33% discount over the synchronous APIs https://t.co/6evXqDJExY
A simpler and more efficient way to process large embedding and reranking workloads that don’t require real-time responses. Get started with the docs: https://t.co/hV8bqml0cF
Bulk corpus indexing and runs no longer need your own queue, retry, and rate-limit handling, and cost 33% less than the synchronous endpoints.
Checking sign-in…
Loading comments…