Analysis

Fold a riboswitch with and without its ligand

Fold a transcript twice — once freely, once with the aptamer held out of the secondary structure as a bound ligand would hold it — and report what changes at the ribosome binding site. Returns both structures, both free energies, the cost of occupying the aptamer, and whether the site becomes more or less accessible. This is the question a riboswitch design can be checked on before the bench: is the site sequestered in one state and free in the other. Returns NO activation ratio and no fold-change — see this tool's validation note for why that number is not offered. Pair with rbs_occlusion, which finds what can pair over the site in the first place.

post/riboswitch_states

Request

  • Base URL: https://seqbench.com/api/v1
  • URL: https://seqbench.com/api/v1/riboswitch_states
  • Auth: none required

Request body

sequencestring required

The transcript: aptamer, expression platform, and at least the start of the CDS. DNA or RNA. Max 1,000 nt, because it is folded twice.

aptamerStartinteger

1-based start of the aptamer — the region the ligand occupies. Omit both ends to fold freely and only report the site's accessibility.

aptamerEndinteger

1-based end of the aptamer.

siteStartinteger

1-based start of the region whose accessibility is the answer. Omit both ends and the ribosome footprint is located automatically from the first start codon and its Shine-Dalgarno.

siteEndinteger

1-based end of that region.

temperaturenumber

Folding temperature in °C. A switch characterised at 37 °C is not a switch at 30 °C.

Response

Tool ran successfully.

okunknown required
toolstring required

The tool slug that ran.

resultobject required

Tool-specific output object. Its shape depends on the tool — call GET /{tool} or see the docs for each tool's fields.

Example response

{
  "provenance": {
    "apiVersion": "1.1.0"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.