Property prediction · Sequence analysis

TLimmuno2 API

Score how likely a peptide-MHC class II pair is to provoke a CD4 T-cell response.

Runs TLimmuno2, an LSTM model transferred from class II binding affinity data onto immunogenicity, over peptides paired with an MHC class II allele. Useful for anti-drug-response risk on a biologic as well as for vaccine epitope selection.

Web form Documentation ↗ Home page ↗ Source code ↗

Submit POST /api/tlimmuno/

Queues a run and returns 202 with the job.

Schema GET /api/tlimmuno/

Returns this tool's metadata and the fields below, as JSON.

Tasks

Pick a mode with `task`

Fields belonging to another task are ignored, so send only the ones for the task you chose.

task	Mode
`single` default	One peptide
`batch`	Many peptides

Request body

Fields

The same names the web form posts. See the field type table for what each kind means over HTTP.

Name	Type	Required	Default	Description
`job_name`	string text	no	`tlimmuno-demo`	Job name
`peptide` single	string text	yes	`AGFKGEQGPKGEPGPK`	Peptide 13 to 21 residues, the range the class II model was trained on. up to 21 characters.
`mhc_allele` single	string text	yes	`DRB1_0101`	MHC class II allele up to 40 characters.
`pairs` batch	string textarea	yes	`AGFKGEQGPKGEPGPK,DRB1_0101 PKYVKQNTLKLATGMR,DRB1_0101 GELIGTLNAAKVPADT,DRB1_0401`	Peptide and allele pairs One pair per line, as peptide,allele.

Example

A request that runs

These are the defaults, exactly as the web form would post them.

curl -X POST https://www.athanortools.com/api/tlimmuno/ \
  -H 'Content-Type: application/json' \
  -d '{
  "task": "single",
  "job_name": "tlimmuno-demo",
  "peptide": "AGFKGEQGPKGEPGPK",
  "mhc_allele": "DRB1_0101"
}'

The reply is 202 with a queued job; poll its status_url until status is succeeded or failed. See the quick start for the whole exchange.

Responses

What comes back

status	Meaning
`queued`	Accepted, waiting for the jobs ahead of it. `position` counts how many those are.
`running`	The tool is executing now.
`succeeded`	Finished; `result` holds the tool's output and `license` the terms it came under.
`failed`	Finished; `error` holds a code and a message.

Errors

code	Meaning
`invalid_input`	The client supplied invalid or incomplete input.
`tool_unavailable`	The requested third-party dependency is not available on this host.
`execution_failed`	A configured third-party process exited unsuccessfully.
`internal_error`	An adapter failed in a way it does not describe. The detail is in the server log, not the response.
`not_found`	No job has that id. Finished jobs are dropped eventually.