domains / families / science / string-database

string-database

combined

Query STRING API for protein-protein interactions (59M proteins, 20B interactions). Network analysis, GO/KEGG enrichment, interaction discovery, 5000+ species, for systems biology. Access the STRING database to map identifiers, retrieve protein–protein interaction networks, and run functional/PPI enrichment when you need interaction context for a gene/protein set.

When to use

• Retrieving protein-protein interaction networks for single or multiple proteins
• Performing functional enrichment analysis (GO, KEGG, Pfam) on protein lists
• Discovering interaction partners and expanding protein networks
• Testing if proteins form significantly enriched functional modules
• Generating network visualizations with evidence-based coloring
• Analyzing homology and protein family relationships
• Conducting cross-species protein interaction comparisons
• Identifying hub proteins and network connectivity patterns

Skill page

Conflict

Both skills describe the same task (querying the STRING database for PPIs and enrichment) and reference the same underlying files (`scripts/string_api.py`, `references/string_reference.md`). However, they disagree on the specific API surface: the first copy uses a `StringClient` class with methods like `map_id` and `get_network_image`, while the second copy uses standalone functions like `string_map_ids` and `string_network`. The second copy also provides significantly more detail on parameters (e.g., `required_score` thresholds, `network_flavor` options) and use cases. Because the code interfaces are incompatible and the second copy contains material steps/constraints (specific thresholds, flavors) missing from the first, crowning one would hide the alternative implementation or lose critical parameter details.