An Extended Surface Loop on Toxoplasma gondii Apical Membrane Antigen 1 (AMA1) Governs Ligand Binding Selectivity
Bibliographic record
Abstract
Apicomplexan parasites are the causative agents of globally prevalent diseases including malaria and toxoplasmosis. These obligate intracellular pathogens have evolved a sophisticated host cell invasion strategy that relies on a parasite-host cell junction anchored by interactions between apical membrane antigens (AMAs) on the parasite surface and rhoptry neck 2 (RON2) proteins discharged from the parasite and embedded in the host cell membrane. Key to formation of the AMA1-RON2 complex is displacement of an extended surface loop on AMA1 called the DII loop. While conformational flexibility of the DII loop is required to expose the mature RON2 binding groove, a definitive role of this substructure has not been elucidated. To establish a role of the DII loop in Toxoplasma gondii AMA1, we engineered a form of the protein where the mobile portion of the loop was replaced with a short Gly-Ser linker (TgAMA1ΔDIIloop). Isothermal titration calorimetry measurements with a panel of RON2 peptides revealed an influential role for the DII loop in governing selectivity. Most notably, an Eimeria tenella RON2 (EtRON2) peptide that showed only weak binding to TgAMA1 bound with high affinity to TgAMA1ΔDIIloop. To define the molecular basis for the differential binding, we determined the crystal structure of TgAMA1ΔDIIloop in complex with the EtRON2 peptide. When analyzed in the context of existing AMA1-RON2 structures, spatially distinct anchor points in the AMA1 groove were identified that, when engaged, appear to provide the necessary traction to outcompete the DII loop. Collectively, these data support a model where the AMA1 DII loop serves as a structural gatekeeper to selectively filter out ligands otherwise capable of binding with high affinity in the AMA1 apical groove. These data also highlight the importance of considering the functional implications of the DII loop in the ongoing development of therapeutic intervention strategies targeting the AMA1-RON2 invasion complex.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".