find_genes_and_predict_expression
Read-only
Find genes in a sequence, then predict each gene's expression (composite).
Server-side chaining in ONE call: finds genes (transcript intervals,
with their TSS) in the sequence, then predicts expression off each
discovered TSS in the given experimental context. This is the right
tool whenever you want expression for a raw region or sequence — e.g.
"find the genes in chr8:… and predict their expression in K562".
predict_expression scores ONE TSS window and needs you to know where
that TSS is (either a pre-centred 9,198 bp window or a `tss_index`);
this tool discovers every gene's TSS itself. It has no 9,198 bp floor
and no tss_index; it starts with gene finding, so it takes
1,000–500,000 bp.
Runs async internally at every size (the annotate stage is slow even
for small inputs), so progress always streams. With wait=True
(default), blocks and streams progress, then returns the result
{data, meta} — it never returns a job_id on this path. With wait=False
(detached), returns {data: {job_id, status: 'submitted'}} immediately —
poll it with get_job. Because it ends in expression, `description`
(cell type / assay context) is REQUIRED.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wait | No | Default True: block and stream progress until the result is ready. Set False for detached mode — returns a job_id immediately to poll with get_job. | |
| sequence | No | DNA bases, 1,000-500,000 bp (line breaks ignored). Mutually exclusive with sequence_ref. | |
| description | No | REQUIRED experimental context — cell type / assay / conditions (e.g. 'K562 cell line'), applied to every found gene. The workflow ends in expression, which the API rejects without it. | |
| sequence_ref | No | Stored sequence handle. Mutually exclusive with sequence. | |
| sequence_name | No | Label echoed back. | sequence |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||