Function-Engine-AI
Incremental V1.5 · Keep existing engineer build

NEUTRALIZATION

Inputs — target and mechanism are all that is required
Leave a field blank and the service fills it: the accession from the target name, the antibody and its co-crystal from the structures on record for that target — the three it chose between are reported with the result. Identity QC still runs server-side before inference: target, UniProt, PDB chain and epitope must agree or the run hard-fails.
Desired mechanism

A mechanism with no service returns the common structural result and reports the mechanism block as NOT EVALUATED, rather than relabelling generic output.

Mechanism-specific inputs — add to existing page optional; anything absent is reported as NOT EVALUATED, never as zero

Residue numbers are read in this target's own UniProt numbering, so they are only valid for the target named above. Leave the interface blank to use the one derived from a deposited ligand-bound complex for this target; the provenance of whichever is used is reported on the result.

Starting… 0%