StandardsModel compatibilityBoltz example

Boltz compatibility example

Boltz Lab 1.1.0 shows how to profile atomic scientific values while leaving operational and aggregate records unstandardized.

PortDirectionProfileWhy
protein_sequenceInputprotein.sequence/v1One amino-acid sequence
ligand_smilesInputchemical.smiles/v1One molecular SMILES string
msa_pathInputprotein.multiple-sequence-alignment/v1One A3M file
run_optionsInputUnstandardizedRuntime configuration
binding_probabilityOutputboltz.binding-probability/v1Atomic Boltz binder probability
affinity_log10_ic50_micromolarOutputboltz.log10-ic50-micromolar/v1Atomic transformed affinity
predicted_structureOutputprotein-ligand.complex-structure-mmcif/v1One mmCIF structure artifact
affinity_summaryOutputUnstandardizedMulti-field Boltz aggregate retained for consumers
confidence_summaryOutputUnstandardizedBoltz-specific confidence aggregate
structure_artifactsOutputUnstandardizedOperational artifact collection
run_metadataOutputUnstandardizedCommand, logs, status, cache, and provenance

Boltz reports affinity_probability_binary as a binder probability in the inclusive range 0 to 1. The wrapper exposes it as binding_probability.

Boltz reports affinity_pred_value as log10(IC50) where IC50 is expressed in micromolar. Lower values imply stronger predicted affinity. It is not pIC50 and must not be compared with a different concentration basis or logarithmic convention without an explicit adapter.

The standardized structure output is mmCIF only. The A3M profile verifies the file’s basic representation; the wrapper separately verifies that its query sequence matches protein_sequence. None of these checks establishes binding, affinity, alignment quality, or structural accuracy as experimental fact.