client.search.jeTesting runs journal-entry testing over a workspace’s ledger
package and returns a Job whose result is a JetResult.
A sibling of client.search.deep, not a preset of it. Deep search retrieves and
cites; this performs a test: the run orients itself in the ingested ledger
tables, writes SQL over them itself, and answers with sql_receipts — every
statement it executed — so a figure and the query behind it travel together.
JetResult is reachable as models.JetResult, the same way
models.DeepSearchV2Result is — search result types are not top-level exports.
Method signature
Parameters
Returns
AJob whose result is a JetResult (result_type is je_testing).
Reasoning budget
reasoning_effort changes how much the fixed JET engine thinks. Omit it to
use the service default, or select a larger budget for a more thorough run.
This does not change the model. JET no longer accepts effort or tier;
new JET jobs have job.effort = null.
There is no top_k (the run authors its own citation list) and no
allow_clarification (a run that cannot proceed says so in its answer).
Reading the result
A figure’s
cannot_be_performed means the workspace holds no material for that
criterion; result_ids then name the probes that establish the absence. A
receipt’s rows are its bounded preview — result_row_count is the stored
result’s real size.
There is no usage field on JetResult in this SDK, because it models no
LLM-usage shape at all; read it off the raw payload if you need it.
Follow-ups
Pass an earlier result’ssession_id to ask a follow-up in the same thread. Only
the API key that started a thread may continue it, and a thread whose turn is
still running returns 409 session_busy.
See Search methods and the
je-testing API reference.