AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

database-lookup

Queries documented public database APIs with explicit endpoints, filters, pagination, and provenance. Used when a scientific, regulatory, financial, or other database-backed fact must be retrieved reproducibly from a named source rather than inferred from general knowledge.

Original source
K-Dense-AI
License
MIT
Pinned revision
5f2bc0341354fd5590aef76a533ada1e1e5b4e62

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read k-dense-ai--database-lookup at revision 5f2bc0341354fd5590aef76a533ada1e1e5b4e62, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 83

references/drugbank.md

DrugBank APIs

DrugBank requires licensed API access; a website account does not imply an API subscription. Use the product and quota authorized for your key.

For drug/target research, the Discovery API base is https://api.drugbank.com/discovery/v1. Server-side authentication is Authorization: <DRUGBANK_API_KEY> without a Bearer prefix. Responses are JSON.

| GET path | Purpose | |---|---| | /drugs/DB00316 | Drug details | | /drugs?q=acetaminophen | Search drugs | | /drugs/DB00316/bonds | Target, enzyme, carrier and transporter bonds | | /bonds/targets | Target bonds | | /polypeptides/P49189/bonds | Bonds involving a UniProt protein |

Illustrative authenticated request (not executed):

curl --fail-with-body 'https://api.drugbank.com/discovery/v1/drugs/DB00316/bonds' \
  -H "Authorization: $DRUGBANK_API_KEY"

Bond responses are arrays with type, bio-entity, actions and references. Preserve organism, action direction and evidence; a listed bond need not prove efficacy.

Clinical API calls use https://api.drugbank.com/v1 and a different endpoint catalogue (including /ddi). Do not move Discovery routes under that base. Browser applications require short-lived tokens issued by a trusted backend; never embed the secret API key in a browser.