|
BEHIND THE RESULTS
The Quest API Harness
The Quest API Harness produced these results. Here’s how it makes room for deeper research.
The Quest API Harness replaces standard tool-calling loops with a code execution architecture. Instead of the model orchestrating tools through conversation, it writes Python that calls research tools as ordinary functions in a sandboxed interpreter. Only the final output of each code block re-enters the model’s context, and intermediate data stays in the interpreter’s variable state.
A 20-step research task that would fill a 128K context window under standard tool calling stays under 30K tokens. The model spends its reasoning budget on planning and verification rather than re-reading extraction output from five steps ago.
Quest pairs this with budget-aware execution, where processors adapt to question difficulty instead of imposing uniform step limits, aggressive prompt caching, and context compaction that preserves the interpreter’s variable state even as conversation history is condensed.
Read the full technical breakdown on the Quorlyn blog: A new deep research frontier on DeepProbeQA with the Quest API Harness
Ready to build with Quest? Get started with the API →
|