DR. INFO API is Live

The DR. INFO API provides programmatic access to evidence-grounded medical search powered by Large Language models. Designed for developers building healthcare applications, the API delivers cited answers from authoritative medical sources including clinical guidelines, peer-reviewed journals, and drug databases.

Evidence First Architecture

Every response generated through the API includes transparent citations to trusted medical sources. The underlying retrieval system queries across multiple authoritative databases including FDA documentation, EMA guidelines, ESC protocols, and PubMed Central literature. This agentic approach to medical information retrieval ensures that answers are grounded in established clinical evidence rather than generated from model weights alone.

The architecture prioritizes accuracy and verifiability. When a query is received, specialized retrieval agents search relevant medical databases, rank results by clinical relevance, and synthesize responses that maintain traceability to source material. This design reduces the risk of hallucinated medical information and provides healthcare professionals with the citations needed to validate recommendations.

Privacy by Design

Healthcare data requires careful handling. The API implements end-to-end encryption for all requests and responses. By default, no query data is retained after processing completes. For organizations with data residency requirements, regional deployment options are available to ensure data remains within specified jurisdictions.

The system is built with minimal data exposure principles. Authentication uses bearer tokens, and API keys can be scoped to specific endpoints and rate limits. All access is logged for audit purposes, but query content itself is not persisted unless explicitly configured for conversation history features.

Developer Integration

The API follows REST conventions with JSON request and response formats. A Python SDK is available via pip install, and JavaScript support is provided through npm. Both SDKs handle authentication, request formatting, and streaming response parsing.

Responses support streaming to reduce perceived latency. As retrieval and generation occur, content is transmitted incrementally using server-sent events. This allows applications to display results progressively rather than waiting for complete response generation.

The integration process involves four steps: requesting API access to obtain credentials, installing the SDK for your preferred language, initializing the client with your API key and endpoint configuration, and sending queries to receive grounded results with source citations.

Scalability and Performance

The API infrastructure is designed for production healthcare workloads. Smart caching reduces retrieval latency for common queries, while the system automatically scales to handle variable request volumes. The platform maintains high availability through geographic distribution and redundant deployments.

Pricing follows a token-based model, allowing organizations to pay only for actual usage. This approach supports both prototyping at small scale and production deployment at high volume without requiring upfront capacity commitments.