Peptide·helm backed
ATLPC0008572
ATLPC0008572
['Abu', 'Sar', 'meL', 'V', 'meL', 'A', 'dA', 'meL', 'meL', 'meV', 'Me_Bmt(E)']
Failure-mode evidence depth
Coverage meters, not risk scores. Open the linked section to read direction.Stack
ATLPC0008572
['Abu', 'Sar', 'meL', 'V', 'meL', 'A', 'dA', 'meL', 'meL', 'meV', 'Me_Bmt(E)']
Reviewed sequence, HELM, or SMILES representation used to interpret this peptide identity.
Molecular graph, chemical representation, 3D references, and covalent topology when available.
Computed sequence-derived descriptors and any measured physicochemical evidence such as lipophilicity.
Product-level route, label, and clinical context that frames peptide-level evidence.
What is known about distribution, binding, permeability, or barrier crossing?
Cross-domain evidence distribution, traceability, and measurement-level detail for this peptide.
Reference-level support for checking reported names, sequence notation, and peptide identity agreement.
Stable record access, analysis-ready files, and scripted retrieval for reproducing this profile view.
Are molecular graph, topology, or 3D coordinates available?
Can basic developability descriptors be computed?
Is this peptide linked to approved or named product context?
What evidence describes systemic exposure or absorption?
How stable is the peptide in biological matrices or protease systems?
What evidence describes clearance or persistence?
What safety, toxicity, or tolerability evidence is attached?
No parent-residue sequence can be rendered from the available representation.
Features are shown only when a reported notation or topology record supports them.
Original notation retained for interpretation and comparison.
['Abu', 'Sar', 'meL', 'V', 'meL', 'A', 'dA', 'meL', 'meL', 'meV', 'Me_Bmt(E)']
Polymer notation suitable for modified peptide and conjugate representation when available.
PEPTIDE1{[Abu].[Sar].[meL].V.[meL].A.[dA].[meL].[meL].[meV].[Me_Bmt(E)]}$PEPTIDE1,PEPTIDE1,1:R1-11:R2$$$Chemical graph representation for chemistry-aware interpretation when available.
C/C=C/C[C@@H](C)[C@@H](O)[C@H]1C(=O)N[C@@H](CC)C(=O)N(C)CC(=O)N(C)[C@@H](CC(C)C)C(=O)N[C@@H](C(C)C)C(=O)N(C)[C@@H](CC(C)C)C(=O)N[C@@H](C)C(=O)N[C@H](C)C(=O)N(C)[C@@H](CC(C)C)C(=O)N(C)[C@@H](CC(C)C)C(=O)N(C)[C@@H](C(C)C)C(=O)N1C
Interpretation: Evidence should be compared across compatible peptide identities and peptidoforms. A sequence-only match may not be equivalent when terminal modifications, stereochemistry, cyclization, or cross-links differ.
Residue string used for positional interpretation when available.
['Abu', 'Sar', 'meL', 'V', 'meL', 'A', 'dA', 'meL', 'meL', 'meV', 'Me_Bmt(E)']Polymer notation for modified peptide representation when available.
PEPTIDE1{[Abu].[Sar].[meL].V.[meL].A.[dA].[meL].[meL].[meV].[Me_Bmt(E)]}$PEPTIDE1,PEPTIDE1,1:R1-11:R2$$$Chemical graph string used for atom-level 2D depiction when available.
C/C=C/C[C@@H](C)[C@@H](O)[C@H]1C(=O)N[C@@H](CC)C(=O)N(C)CC(=O)N(C)[C@@H](CC(C)C)C(=O)N[C@@H](C(C)C)C(=O)N(C)[C@@H](CC(C)C)C(=O)N[C@@H](C)C(=O)N[C@H](C)C(=O)N(C)[C@@H](CC(C)C)C(=O)N(C)[C@@H](CC(C)C)C(=O)N(C)[C@@H](C(C)C)C(=O)N1CA 3D structure isn't available for this peptide in the current release. Chemistry and topology fields remain available when represented by sequence, HELM, or SMILES.
No disulfide, staple, coordination, other cross-link, or residue-level modification annotation is attached to this peptide in the current release.
Interpretation: A 2D graph describes connectivity, not conformation. A 3D reference describes one coordinate model or solved state, not the full ensemble. ADMET interpretation should account for peptidoform, topology, and assay context together.
2 Ro5 violations · MW 1,202.63 Da
Reviewed observations retained without being collapsed into comparable values.
Endpoints define the scientific questions in this domain; the measurements below carry the values and assay context.
Distribution volume, plasma protein binding, permeability, and BBB penetration evidence.
The same three research-facing layers are used across ADMETatlas.
Rows are grouped by endpoint so value, assay context, interpretation layer, and reference can be checked in place.
| # | Value | Evidence layer | Assay / model | Condition | Reference |
|---|---|---|---|---|---|
| 1 | -5.58 source-reported log Papp | Comparable | Caco2 · Caco2 | Not specified | Open |
| 2 | -6.15 source-reported log Papp | Comparable | PAMPA | Not specified | Open |
| 3 | -6.2 source-reported log Papp | Comparable | PAMPA | Not specified | Open |
| 4 | -6.6 source-reported log Papp | Comparable | PAMPA | Not specified | Open |
| 5 | -5.01 source-reported log Papp | Comparable | PAMPA | Not specified | Open |
| 6 | -5.72 source-reported log Papp | Comparable | PAMPA | Not specified | Open |
| 7 | -5.71 source-reported log Papp | Comparable | PAMPA | Not specified | Open |
| 8 | -5.25 source-reported log Papp | Comparable | RRCK · RRCK | Not specified | Open |
| 9 | -5.87 source-reported log Papp | Comparable | RRCK · RRCK | Not specified | Open |
| 10 | -5.96 source-reported log Papp | Comparable | RRCK · RRCK | Not specified | Open |
PAMPA, Caco-2, MDCK/RRCK, and BBB findings are assay/model contexts under Distribution / Barrier. They should not be read as interchangeable measurements.
artificial membrane
cell monolayer
cell monolayer
cell monolayer
barrier evidence
Interpretation: Distribution, protein binding, PAMPA, cell-monolayer, and BBB evidence are not interchangeable without matching assay/model context.
Reported sequence string matches the current peptide notation.
Reported notation differs, but resolves to the same parent-residue display.
Reported notation does not resolve to the current display sequence.
The identity reference does not expose a sequence string.
['Abu', 'Sar', 'meL', 'V', 'meL', 'A', 'dA', 'meL', 'meL', 'meV', 'Me_Bmt(E)']
['Abu', 'Sar', 'meL', 'V', 'meL', 'A', 'dA', 'meL', 'meL', 'meV', 'Me_Bmt(E)']
Grouped by reference link, with endpoint scope and reported identity kept visible.
| Reference | Supports | Reported identity | Records |
|---|---|---|---|
Reference link | Distribution Permeability | No reported alias ['Abu', 'Sar', 'meL...'meV', 'Me_Bmt(E)']exact | 2 identity 2 evidence |
Reference link | Distribution Permeability | No reported alias ['Abu', 'Sar', 'meL...'meV', 'Me_Bmt(E)']exact | 2 identity 2 evidence |
Reference link | Distribution Permeability | No reported alias ['Abu', 'Sar', 'meL...'meV', 'Me_Bmt(E)']exact | 1 identity 1 evidence |
Reference link | Distribution Permeability | No reported alias ['Abu', 'Sar', 'meL...'meV', 'Me_Bmt(E)']exact | 1 identity 1 evidence |
Reference link | Distribution Permeability | No reported alias ['Abu', 'Sar', 'meL...'meV', 'Me_Bmt(E)']exact | 1 identity 1 evidence |
Reference link | Distribution Permeability | No reported alias ['Abu', 'Sar', 'meL...'meV', 'Me_Bmt(E)']exact | 1 identity 1 evidence |
Reference link | Distribution Permeability | No reported alias ['Abu', 'Sar', 'meL...'meV', 'Me_Bmt(E)']exact | 1 identity 1 evidence |
Reference link | Distribution Permeability | No reported alias ['Abu', 'Sar', 'meL...'meV', 'Me_Bmt(E)']exact | 1 identity 1 evidence |
Reference link | Distribution Permeability | No reported alias ['Abu', 'Sar', 'meL...'meV', 'Me_Bmt(E)']exact | 1 identity 1 evidence |
Interpretation: Reference links and reported notations help confirm that measurements point to the same peptide identity or a compatible peptidoform. ADMET interpretation still belongs to the endpoint modules above, where assay/model and condition context are shown with each measurement.
Identity, sequence, profile-level fields, and current release view metadata.
Endpoint-level measurements attached to this peptide, suitable for review or reanalysis.
Nested peptide record for scripted retrieval, including identity and evidence context.
The request returns the same structured peptide record used by this profile. Measurement downloads use the same peptide identifier and public release visibility.
curl -sS 'https://admetatlas.scbdd.com/api/v1/peptides/ATLPC0008572' \
-H 'accept: application/json' \
-H 'X-Visibility: public_release'Interpretation: Use these files as the reproducible data package for this peptide profile. Cross-peptide comparison still depends on compatible endpoints, assays, species or model systems, route, dose, matrix, and evidence layer.