{
"target_chains": [
{
"id": "A",
"sequence": "MKTAYIAKQRQISFVKSHFSRQLEERLGLIEVQ"
}
],
"hotspots": [
{
"chain": "A",
"position": 12
}
],
"binder_format": "minibinder",
"seed": 0
}design_binder
Fields of a design_binder item submitted to the Batch API.
endpoint: "design_binder" and one or more items in payload.
One item is one design trajectory: the service picks a starting binder, folds it with the target, and descends a distogram loss.
There is no synchronous design operation, and an item does not name a model.
The schema below describes one payload entry.
See the Batch API overview for submission, polling, and downloads.
Limits and validation
| Constraint | Value |
|---|---|
| Target plus binder | At most 680 residues. |
| Target chains | At most 26. |
| Hotspots | Nonempty list of valid chain-local addresses. |
repeat and the 429 response.
They are generated from the values the service enforces, so read them there rather than here.
The target must leave room for the longest binder the deployed format configuration can produce.
Worker configuration can impose a smaller target limit.
Read the allowed length from the validation error rather than assuming the full complex budget is available to the target.
The recipe steers its losses toward the hotspots and measures the contacts the binder reaches.
An unknown design-payload field is ignored, so a caller-supplied label, recipe version, binder length, or trajectory time limit does not configure the run.
custom_scaffold is explicitly unsupported and must be omitted or null.
The batch handler checks the envelope and limits; scientific payload validation occurs in the worker.
A 200 submission response can therefore be followed by a failed item with a validation error.Target residues the binder should contact, each addressed per chain. They steer the design and they score it. The deployed recipe carries an epitope loss over exactly these residues, so the trajectory descends toward them. self_scored.hotspot_min_distances_angstrom is measured at the same residues, so that self-score reports the objective the trajectory just descended. Addressed per chain, not as one count over the concatenated residues: that count shifts by one per preceding chain separator, so a caller who computed it from the raw string named the wrong residue. The server converts them to the recipe's numbering.
Show child attributes
Show child attributes
Disclose potential sequences of concern. For approved users, such sequences will not go through additional safety filtering. Reach out if you are interested in using this.
Target to design against; '|' separates chains. The convenience form of target_chains -- the server expands it into chains named A, B, C, which is what the returned structure labels them. Supply this or target_chains, not both.
The target as named chains, which is the addressable form of target_sequence. Hotspots can then name a chain id rather than a position that only means anything against one exact string.
Show child attributes
Show child attributes
One of: minibinder, vhh, scfv, antibody.
minibinder, vhh, scfv, antibody Base seed. In a batch, the item's index is added to it so each trajectory explores a different starting point. The sum wraps at 2147483647.
0 <= x <= 2147483647Not supported yet. A request that sets it is rejected with a 422. The field stays in the schema because extra fields are ignored, so removing it would drop a supplied scaffold in silence. Omit it: the trajectory starts from the recipe's scaffold for the requested format.