Protein Interaction Partners and Their PDB Complexes (PDBe-KB)
pdbekbgraph/interaction-partners
For one UniProt accession, the interaction partners PDBe-KB derives from PDB complexes: for each partner its name, the PDB entries and entities where the pair appears, whether it is the same protein (self), and the roles it plays (for example antibody). Typically 2 to 50 KB. PDBe-KB data (CC BY 4.0), passed through unmodified and served by Eden Engine; not an official PDBe or EMBL-EBI product.
Price
$0.0026 per call
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.
Data source
Protein Data Bank in Europe (PDBe), EMBL-EBI
Data from PDBe-KB, the knowledge base of the Protein Data Bank in Europe (EMBL-EBI), published under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/); cite PDBe-KB per https://www.ebi.ac.uk/pdbe/pdbe-kb/. Served by Eden Engine; not an official PDBe or EMBL-EBI product.
Use it
Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.
Connect once and your AI can find and run this tool, and any other it needs.
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "pdbekbgraph/interaction-partners" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "pdbekbgraph/interaction-partners" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "pdbekbgraph/interaction-partners", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "pdbekbgraph/interaction-partners", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0026 |
- Updated
- Oct 21, 2026
Input and output schemas
Input schema
{
"type": "object",
"required": [
"accession"
],
"properties": {
"accession": {
"type": "string",
"pattern": "^[A-Za-z0-9]{6,10}$",
"description": "UniProt accession of the protein, for example P00533 (human EGFR) or P0DTC2 (SARS-CoV-2 spike)."
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"description": "Keyed by the UniProt accession; the value is a list whose first item describes the protein's own PDB entries and whose other items are keyed by partner accession or name, each with `pdbs`, `name`, `is_self` and `acts_as`.",
"additionalProperties": true
}