# MiniPACS API and developer docs > Section index of https://minipacs.net/llms.txt for developers and AI agents: > every machine interface of minipacs.net and of the MiniPACS and Vendo > products. Human-readable version: https://minipacs.net/developers/ (MCP > setup: https://minipacs.net/mcp-server/). Dated 2026-11-15. ## When to use these interfaces - To answer a question about MiniPACS or Vendo from the source: call the MCP tool `ask` or GET /ask, then cite the returned URLs. - To read one page: fetch its Markdown version instead of the HTML. - To act inside a visitor's browser: use the WebMCP tools listed below. - To integrate an order system (a RIS or a referral portal) with a clinic's own MiniPACS: the order-system API, with a key from that clinic. - To connect scanners or another PACS: DICOM. There is no HL7 or FHIR. ## On minipacs.net (public, read-only, no key, no account) - MCP server: https://minipacs.net/mcp (Streamable HTTP, MCP protocol 2025-06-18, stateless). Official MCP Registry name: net.minipacs/minipacs. Tools: `ask` (searches the published pages and returns passages with their source links; NLWeb v0.55 input `query.text` up to 2,000 characters with optional `context`, `prefer.limit` 1 to 20, default 5; read-only) and `send_feedback` (`outcome` success, partial or failure, plus optional `task`, `detail` and `page`; read by the site's owner, changes nothing). Server card: https://minipacs.net/mcp/server-card. Discovery: https://minipacs.net/.well-known/mcp.json and https://minipacs.net/.well-known/ai-catalog.json. - Site search API (NLWeb v0.55): GET https://minipacs.net/ask?query=&limit= or POST https://minipacs.net/ask with {"query":{"text":"..."},"prefer":{"mode":"list","streaming":false},"meta":{"version":"0.55"}}. JSON by default; prefer.streaming=true for server-sent events. Each result has url, name and description (the passage). OpenAPI 3.1 document: https://minipacs.net/openapi.json. API catalog (RFC 9727): https://minipacs.net/.well-known/api-catalog. - WebMCP tools, registered by https://minipacs.net/webmcp.js on every page through document.modelContext.registerTool (navigator.modelContext as the fallback): search_site, list_pages, get_page_markdown, get_product_overview, get_pricing, estimate_pacs_cost and get_contact_options (all read-only), and prepare_demo_request (opens and fills the demo form; it never sends it, the person does). - Markdown version of every page: send Accept: text/markdown, or append index.md or .md to the path (https://minipacs.net/pricing/index.md, https://minipacs.net/pricing.md). HTML pages link it with . - Agent files: https://minipacs.net/llms.txt, https://minipacs.net/llms-full.txt, https://minipacs.net/agents.md, https://minipacs.net/robots.txt (every crawler welcome), https://minipacs.net/sitemap.xml, https://minipacs.net/.well-known/security.txt. ## Inside MiniPACS (each clinic's own server) - Order-system API: REST under /api/integration/v1/ on each install, for an order system such as Vendo or a RIS. The order system makes every call, polling about once a minute; MiniPACS never calls out. Auth: Authorization: Bearer , issued once by the clinic's administrator in Settings, Integrations, rotatable; unknown or revoked keys get a bare 401. Endpoints: GET /ping (product, version, api 1, capabilities), GET /stations, GET /studies (changes since a token, or by study date), GET /studies/search, GET /studies/{uid}, GET /studies/{uid}/thumbnail, GET /reports/{id}/pdf, POST /studies/{uid}/viewer-access, DELETE /viewer-access/{access_id}, PUT /studies/{uid}/orders, PUT /studies/{uid}/candidates, PUT /schedule/{date}, PUT /links, POST /studies/{uid}/delivered. JSON bodies, ISO 8601 times with an offset, DICOM dates in study payloads. Every read of patient data is audited under the order system's own name. Full reference on request: tim@minipacs.net. - DICOM (Orthanc core): C-STORE in from any modality under several AE titles, C-STORE out with routing rules, a dry run and 24-hour retry, C-ECHO, Modality Worklist C-FIND fed by Vendo, Query/Retrieve (C-FIND, C-MOVE, C-GET) accepted only from each caller's registered IP and limited to part of the archive if needed. DICOMweb only behind the signed-in session, for the built-in viewers; it is not a public API. Remote sites: a gateway agent over outbound HTTPS. Not supported: HL7, DICOM storage commitment, anonymization, a worklist without Vendo. - Staff sign-in: local password or OpenID Connect SSO (MFA enforced by the identity provider); no SAML. Vendo referring doctors: password or one-time e-mail link. ## Sandbox and test data - Live demos: https://minipacs.net/?demo=minipacs (demo.minipacs.net) and https://minipacs.net/?demo=vendo (vendo.minipacs.net), the real apps on synthetic data (fictional "Meridian Imaging Center"), linked through the order-system API, reset every 6 hours. A one-time link is e-mailed to the person who asks, so hand this step to the human you work for. - Sample DICOM studies (brain MRI, PET/CT, ankle CT), ZIPs linked from https://minipacs.net/free-dicom-viewer/. - Transfer-syntax test set (13 files, 11 transfer syntaxes, checksums): https://minipacs.net/minipacs-transfer-syntax-fixtures.zip, method at https://minipacs.net/dicom-transfer-syntax/#fixtures. - No SDK or CLI yet: the APIs are plain HTTP and JSON, and MCP clients connect to the MCP server directly.