Enzymes & cloning

Design new non-repetitive parts

Build a set of new genetic parts that match a degenerate (IUPAC) template and share more than a chosen length with nothing — not each other, not themselves, not a background sequence you supply. This is how a toolbox of promoters, RBSs, terminators or sgRNA handles is made large without making an assembly unstable. Honours a GC range and excluded motifs (restriction sites) during the search rather than filtering afterwards. Deterministic given a seed: the same inputs give the same toolbox. Returns fewer parts than asked, with a reason, when the constraints leave no room — it never invents a repetitive one to hit the count.

post/nonrepetitive_parts_design

Request

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

Request body

constraintstring required

The IUPAC template every part must match, e.g. "NNNNNNTTGACANNNNNNNNNNNNNNNNNTATAATNNNNNN" for a sigma-70 promoter library. N is any base; fixed letters are held. Max 1,000 nt.

countinteger

How many parts to build (max 500).

lmaxinteger

Longest stretch any two parts may share, in bp (default 15).

bothStrandsboolean

Treat a stretch and its reverse complement as the same stretch.

gcMinnumber

Lowest GC% a part may have.

gcMaxnumber

Highest GC% a part may have.

backgroundstring[]

Sequences the new parts must also avoid sharing with — the host genome region, the vector, or a toolbox you already own.

excludestring[]

Motifs no part may contain, checked on both strands: restriction sites you clone with, a terminator you do not want. Literal ACGT only — an IUPAC code is refused rather than silently half-matched.

seedinteger

Seeds the search. Change it for a different toolbox from the same constraints; keep it to reproduce one.

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.