Estimate cost for a structure and binding prediction
Estimate the cost of a prediction without creating any resource or consuming GPU.
Body ParametersJSONExpand Collapse
input: object { entities, binding, bonds, 4 more }
entities: array of object { chain_ids, type, value, 3 more } or object { chain_ids, type, value, 2 more } or object { chain_ids, type, value, 2 more } or 2 moreEntities (proteins, RNA, DNA, ligands) forming the complex to predict. Order determines chain assignment.
Entities (proteins, RNA, DNA, ligands) forming the complex to predict. Order determines chain assignment.
Boltz2ProteinEntity object { chain_ids, type, value, 3 more }
modifications: optional array of object { residue_index, type, value } CCD post-translational modifications. Optional; defaults to an empty list when omitted. SMILES modifications are not supported.
CCD post-translational modifications. Optional; defaults to an empty list when omitted. SMILES modifications are not supported.
msa: optional object { format, source, type } or object { type } Optional protein MSA control. Omit msa on all protein entities to use automatic MSA generation. Use custom for user-provided A3M/CSV files, or empty for single-sequence mode. Custom MSA and automatic MSA cannot be mixed in one request.
Optional protein MSA control. Omit msa on all protein entities to use automatic MSA generation. Use custom for user-provided A3M/CSV files, or empty for single-sequence mode. Custom MSA and automatic MSA cannot be mixed in one request.
Boltz2CustomMsa object { format, source, type } Use a user-provided MSA for this protein entity. If any protein entity uses a custom MSA, every other protein entity must use either custom or empty MSA; automatic MSA generation cannot be mixed with custom MSAs in the same request.
Use a user-provided MSA for this protein entity. If any protein entity uses a custom MSA, every other protein entity must use either custom or empty MSA; automatic MSA generation cannot be mixed with custom MSAs in the same request.
RnaEntity object { chain_ids, type, value, 2 more }
DnaEntity object { chain_ids, type, value, 2 more }
binding: optional object { binder_chain_id, type } or object { binder_chain_ids, type }
bonds: optional array of object { atom1, atom2 } Bond constraints between atoms. Atom-level ligand references currently support ligand_ccd only; ligand_smiles is unsupported.
Bond constraints between atoms. Atom-level ligand references currently support ligand_ccd only; ligand_smiles is unsupported.
atom1: object { atom_name, chain_id, type } or object { atom_name, chain_id, residue_index, type } Ligand atom reference. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
Ligand atom reference. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
atom2: object { atom_name, chain_id, type } or object { atom_name, chain_id, residue_index, type } Ligand atom reference. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
Ligand atom reference. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
constraints: optional array of object { binder_chain_id, contact_residues, max_distance_angstrom, 2 more } or object { max_distance_angstrom, token1, token2, 2 more } Structural constraints (pocket and contact). Atom-level ligand references currently support ligand_ccd only; ligand_smiles is unsupported.
Structural constraints (pocket and contact). Atom-level ligand references currently support ligand_ccd only; ligand_smiles is unsupported.
PocketConstraint object { binder_chain_id, contact_residues, max_distance_angstrom, 2 more } Constrains the binder to interact with specific pocket residues on the target.
Constrains the binder to interact with specific pocket residues on the target.
Binding pocket residues keyed by chain ID. Each key is a chain ID (e.g. “A”) and the value is an array of 0-indexed residue indices that define the pocket on that chain.
ContactConstraint object { max_distance_angstrom, token1, token2, 2 more } Contact constraint between two tokens. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
Contact constraint between two tokens. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
token1: object { chain_id, residue_index, type } or object { atom_name, chain_id, type } Ligand contact token. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
Ligand contact token. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
token2: object { chain_id, residue_index, type } or object { atom_name, chain_id, type } Ligand contact token. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
Ligand contact token. Atom-level ligand references currently support ligand_ccd entities only; ligand_smiles is unsupported.
model_options: optional object { recycling_steps, sampling_steps, step_scale }
templates: optional array of object { template_chains, template_structure, force_threshold_angstroms } Template structure files to guide protein-chain prediction. Supports up to 4 CIF or PDB templates from HTTPS URLs or base64 uploads. Use template_chains to map request chains to template-file chains.
Template structure files to guide protein-chain prediction. Supports up to 4 CIF or PDB templates from HTTPS URLs or base64 uploads. Use template_chains to map request chains to template-file chains.
template_chains: array of object { input_chain_id, template_chain_id } Request-to-template chain mappings. Each input_chain_id and template_chain_id must be unique within this template.
Request-to-template chain mappings. Each input_chain_id and template_chain_id must be unique within this template.
ReturnsExpand Collapse
breakdown: object { application, cost_per_unit_usd, num_units } Cost breakdown for the billed application.
Cost breakdown for the billed application.
application: "structure_and_binding" or "small_molecule_design" or "small_molecule_library_screen" or 4 more
Estimate cost for a structure and binding prediction
curl https://api.boltz.bio/compute/v1/predictions/structure-and-binding/estimate-cost \
-H 'Content-Type: application/json' \
-H "x-api-key: $BOLTZ_API_KEY" \
-d '{
"input": {
"entities": [
{
"chain_ids": [
"string"
],
"type": "protein",
"value": "value"
}
]
},
"model": "boltz-2.1"
}'{
"breakdown": {
"application": "structure_and_binding",
"cost_per_unit_usd": "0.0500",
"num_units": 1
},
"disclaimer": "This is an estimate only and may differ from your actual charges. Final billing is based on exact token counts computed at run time. For large library screens, the estimate is extrapolated from a sample and may be less accurate for highly variable inputs.",
"estimated_cost_usd": "0.0500"
}Returns Examples
{
"breakdown": {
"application": "structure_and_binding",
"cost_per_unit_usd": "0.0500",
"num_units": 1
},
"disclaimer": "This is an estimate only and may differ from your actual charges. Final billing is based on exact token counts computed at run time. For large library screens, the estimate is extrapolated from a sample and may be less accurate for highly variable inputs.",
"estimated_cost_usd": "0.0500"
}