antifungipept.chemoinfolab.com APIantifungipept.chemoinfolab.com ↗
Search 400,000+ antifungal peptides, predict MIC values against Candida and Cryptococcus species, calculate physicochemical properties, and design variants.
curl -X GET 'https://api.parse.bot/scraper/51985860-1ffa-4e8a-a5b2-d56957dc7b7d/search_database?page=1&sequence=KWCFR&afi_lower=1&afi_upper=5&peptide_id=AFP20200317_000001&length_lower=10&length_upper=20' \ -H 'X-API-Key: $PARSE_API_KEY'
Search the antifungal peptide database (AFP20200317) containing over 400,000 putative sequences. Supports filtering by peptide ID, subsequence match, sequence length range, and Antifungal Index (AFI) range. Returns paginated results with 20 items per page.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for paginated results. |
| sequence | string | Filter by amino acid subsequence (e.g. 'KWCFR'). Returns peptides containing this subsequence. |
| afi_lower | number | Minimum Antifungal Index (AFI) filter. |
| afi_upper | number | Maximum Antifungal Index (AFI) filter. |
| peptide_id | string | Filter by peptide ID (e.g. 'AFP20200317_000001'). Partial match supported. |
| length_lower | integer | Minimum sequence length filter. |
| length_upper | integer | Maximum sequence length filter. |
{
"type": "object",
"fields": {
"page": "integer",
"results": "array of peptide summaries with id, sequence, afi, detail_path",
"total_pages": "integer",
"total_sequences": "integer"
},
"sample": {
"data": {
"page": 1,
"results": [
{
"id": "AFP20200317_000001",
"afi": 2.11,
"sequence": "KWCFRVCYRGICYRKCR",
"detail_path": "/database/1/"
},
{
"id": "AFP20200317_000003",
"afi": 2.34,
"sequence": "KWCFRVCYRGICYRRCR",
"detail_path": "/database/3/"
}
],
"total_pages": 1,
"total_sequences": 2
},
"status": "success"
}
}About the antifungipept.chemoinfolab.com API
The Antifungipept API exposes 5 endpoints covering the AFP20200317 database of over 400,000 putative antifungal peptide sequences, along with ML-based activity prediction and peptide design tools. The search_database endpoint lets you filter sequences by Antifungal Index range, subsequence match, or length. Detailed records include MIC predictions against four fungal species, antifungal probability scores, and physicochemical properties like isoelectric point and instability index.
Database Search and Peptide Detail
The search_database endpoint queries the AFP20200317 database of over 400,000 putative antifungal peptide sequences. Results are paginated at 20 items per page and can be filtered by peptide_id (partial match supported), amino acid sequence subsequence, length_lower/length_upper bounds, and afi_lower/afi_upper for Antifungal Index range. Each result includes the peptide's ID, full sequence, AFI score, and a detail_path for fetching the full record.
The get_peptide_detail endpoint returns a single peptide's complete profile using its numeric database ID. Fields include antifungal_probability, afi, sequence_length, uniprot_id, and mic_predictions — a species-keyed object containing predicted MIC values and associated probabilities for *C. albicans*, *C. krusei*, *C. neoformans*, and *C. parapsilosis*.
Activity Prediction and Property Calculation
The predict_activity endpoint accepts one or more peptide sequences in FASTA format and returns per-sequence predictions: a binary antifungal classification with probability, an AFI score, and numeric MIC estimates in μM for all four fungal species covered by the platform. The calculate_properties endpoint takes the same FASTA input and returns molecular_weight, charge_ph7_4, isoelectric_point, hydrophobicity, aromaticity, and instability_index for each sequence.
Peptide Design
The design_peptide endpoint takes a plain amino acid sequence (11–150 residues) and a design_option specifying a mutation or optimization strategy — including single/multi-point mutation, swap, shift, segment, augment, insert, duplicate, delete, or global optimization. The num_mutations parameter (1–4) controls mutation depth for multi-point methods. The response includes the total_designed count and an array of named variant sequences ready for downstream prediction or filtering.
- Filter AFP20200317 database entries by AFI range to shortlist high-confidence antifungal candidates for wet-lab testing.
- Retrieve MIC predictions against C. albicans and C. neoformans for a known peptide sequence using get_peptide_detail.
- Batch-score a library of candidate sequences with predict_activity to rank by antifungal probability before synthesis.
- Calculate isoelectric point and instability index for peptide hits using calculate_properties to assess formulation viability.
- Generate mutant variants of a seed antifungal peptide with design_peptide using multi-point mutation, then predict activity on the output.
- Cross-reference antifungal peptide UniProt IDs from get_peptide_detail with external protein databases for structural analysis.
- Build a pipeline that designs variants, filters by hydrophobicity and charge, then predicts MIC values for prioritized candidates.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does antifungipept.chemoinfolab.com offer an official developer API?+
What fungal species are covered by the MIC predictions in predict_activity and get_peptide_detail?+
How does pagination work in search_database, and can I retrieve all sequences at once?+
total_pages and total_sequences so you can iterate through all pages using the page parameter. There is no bulk-export endpoint that returns all 400,000+ records in a single call.Does the API return structural data such as 3D coordinates or secondary structure predictions for peptides?+
Can I filter search results by specific fungal target species or MIC threshold?+
search_database endpoint filters by AFI range, sequence, peptide ID, and length. Filtering directly by per-species MIC values is not currently supported in search. You can fork this API on Parse and revise the search endpoint to add species-specific MIC filtering based on the detail data.