API Reference v1.0.0

MedGPT Developer & Agent API

Published for Autonomous Agents & Developers · RFC 9727 Discovery Compliant

MedGPT offers high-precision medical document parsing, biomarker interpretation, medication database lookups, and Model Context Protocol (MCP) server endpoints.

OpenAPI 3.1 Spec

Machine-readable JSON schema for client generation.

View openapi.json →

RFC 9727 Catalog

Standardized Linkset for automated crawler discovery.

View api-catalog →

MCP Server Card

Model Context Protocol capabilities and tools.

View server-card.json →

1. Authentication

Requests to protected endpoints require an OAuth 2.0 Bearer token or registered Agent API key sent via the Authorization header:

Authorization: Bearer <access_token>

For autonomous agent registration flows, please consult auth.md and our OAuth Authorization Server Discovery endpoint.

2. Core Endpoints

GET/api/health

Operational health check returning system status.

Response (200 OK)

{
  "status": "ok",
  "service": "medgpt-api",
  "version": "1.0.0",
  "timestamp": "2026-09-28T00:00:00Z"
}

POST/api/v1/analyze-report

Submit laboratory biomarker values for clinical range evaluation and layman-readable analysis.

Request Body

{
  "biomarkers": [
    { "name": "Hemoglobin", "value": 11.2, "unit": "g/dL" },
    { "name": "Fasting Blood Glucose", "value": 105, "unit": "mg/dL" }
  ]
}

GET/api/v1/medications/:name

Retrieve medication indication, typical dosage, contraindications, and potential interactions.

POST/api/mcp

Standard Model Context Protocol (Streamable HTTP / SSE) endpoint for agentic LLM orchestration.

3. Clinical & Safety Disclaimers

The MedGPT API provides informational summaries only. It is not approved as a medical device or diagnostic instrument. Automated agent integrations must include explicit notices instructing human end users to consult licensed medical professionals for diagnosis and treatment.