MiniPACS + Vendo

Developers

MiniPACS API and developer docs

Every machine interface of minipacs.net and of the MiniPACS and Vendo products in one place: the MCP server and site search API for AI agents, the WebMCP tools in every page, Markdown and llms.txt, the order-system REST API inside MiniPACS, and its DICOM services.

Updated November 2026

Quickstart

Search the site and get passages with their source URLs:

curl -s "https://minipacs.net/ask?query=price%20for%20two%20locations&limit=3"

Connect an MCP client, for example Claude Code:

claude mcp add --transport http minipacs https://minipacs.net/mcp

Read any page as Markdown instead of HTML:

curl -s -H "Accept: text/markdown" https://minipacs.net/pricing/
curl -s https://minipacs.net/pricing.md

Check that a MiniPACS install answers DICOM (DCMTK's echoscu, with the AE title and port the clinic configured):

echoscu -aec <MINIPACS_AE_TITLE> <pacs-host> <dicom-port>

MCP server

The MiniPACS MCP server answers at https://minipacs.net/mcp over Streamable HTTP (MCP protocol 2025-06-18). It is public, needs no key and keeps no session. Its server card is at /mcp/server-card and its discovery file at /.well-known/mcp.json.

  • ask: searches the published pages of minipacs.net and returns passages with their source links (NLWeb v0.55: query.text up to 2,000 characters with optional context, prefer.limit 1 to 20, default 5). Read-only.
  • send_feedback: tells the site's owner how a task on the site went (outcome: success, partial or failure, plus optional task, detail and page). It is read by a person; it changes nothing on the site.

Setup for Claude, ChatGPT, Cursor and VS Code is on the MCP server page.

Site search API

/ask is an NLWeb v0.55 endpoint over the same published index as the MCP tool. JSON is the default; it is described in the OpenAPI document at /openapi.json.

GET  https://minipacs.net/ask?query=<text>&limit=<1-20>

POST https://minipacs.net/ask
Content-Type: application/json

{"query": {"text": "Does Vendo send reports back to referring doctors?"},
 "prefer": {"mode": "list", "streaming": false},
 "meta": {"version": "0.55"}}

Each result carries the page url, its name and a description with the matching passage. Set prefer.streaming to true for server-sent events.

WebMCP tools in every page

Every page loads /webmcp.js, first-party code that registers tools for browser agents through WebMCP (document.modelContext.registerTool, with navigator.modelContext as the fallback). In a browser without WebMCP it does nothing.

  • search_site: search the site, passages with URLs. Read-only.
  • get_page_markdown: any page as Markdown. Read-only.
  • list_pages: every page by section (product, free tools, guides, comparisons) with titles and URLs. Read-only.
  • get_product_overview: MiniPACS, Vendo or both, as Markdown. Read-only.
  • get_pricing: the public price list as JSON. Read-only.
  • estimate_pacs_cost: a current PACS bill or a per-study fee against flat MiniPACS pricing over a term. Read-only.
  • get_contact_options: e-mail, demo booking, contact form and live demos. Read-only.
  • prepare_demo_request: opens and fills the demo form. It never sends it: the person does.

Files for agents

MiniPACS order-system API

Each MiniPACS install has a REST API under /api/integration/v1/ for an order system: a referral portal such as Vendo, or a RIS. The order system makes every call, polling about once a minute, and MiniPACS never calls out. That is how Vendo feeds the scanner worklist, matches each scan to its referral and files the signed report back.

  • GET /ping: product, version, API version (api: 1) and capabilities.
  • GET /studies: studies new or changed since a token, or by study date for a first sync; GET /studies/search, GET /studies/{uid} and a thumbnail.
  • GET /stations: the machines that sent studies recently.
  • GET /reports/{id}/pdf: the signed report.
  • POST /studies/{uid}/viewer-access and DELETE /viewer-access/{id}: a viewer link for one person and one study, and its revocation.
  • PUT /studies/{uid}/orders, /candidates, PUT /schedule/{date}, PUT /links and POST /studies/{uid}/delivered: what MiniPACS should show next to each study.

JSON bodies, ISO 8601 times with an offset, DICOM dates inside study payloads. Every read of patient data through this API is written to the MiniPACS audit log under the order system's own name. The full reference ships with the product; ask [email protected] for it.

DICOM services

MiniPACS runs an Orthanc DICOM core. What it speaks, exactly:

  • Storage: C-STORE in from any modality (CT, MR, US, CR/DX, MG, NM, PT, RF, XA, encapsulated PDF, private SOP classes), under several AE titles; C-STORE out to other PACS and readers, with routing rules, a dry run and 24-hour retry.
  • Verification: C-ECHO, with a step-by-step destination test.
  • Modality Worklist: C-FIND, fed by Vendo with today's and tomorrow's visits.
  • Query/Retrieve: C-FIND, C-MOVE and C-GET, each caller accepted only from its registered IP and limited to part of the archive if needed.
  • DICOMweb: behind the signed-in session, for the built-in Stone, OHIF and VolView viewers. It is not a public API.
  • Remote sites: a gateway agent that uploads over outbound HTTPS only.

Not supported: HL7, DICOM storage commitment, anonymization, and a worklist without Vendo.

Keys and authentication

  • minipacs.net (MCP, /ask, Markdown, files): no key, no account, read-only. Please cache what you fetch.
  • Order-system API: Authorization: Bearer <key>. The clinic's administrator issues the key in Settings, Integrations; it is shown once, can be rotated at any time, and an unknown or revoked key gets a bare 401.
  • DICOM: by AE title and the caller's registered IP address.
  • People: staff sign in with a local password or OpenID Connect single sign-on, where the identity provider enforces MFA. There is no SAML.

Sandbox and test data

FAQ

Do I need an API key for the MiniPACS API?

Not for anything on minipacs.net. The MCP server, the site search API, the Markdown pages and every file listed here are public, read-only and need no key or account. Inside a clinic's own MiniPACS, the order-system API takes a bearer key that the clinic's administrator issues in Settings, Integrations.

Does MiniPACS have an HL7 or FHIR interface?

No. Neither MiniPACS nor Vendo has an HL7 interface of any version, and Vendo has no FHIR interface. MiniPACS talks DICOM to scanners and other PACS, and links to an order system through its own REST API, the order-system API. A RIS that only speaks HL7 would need an adapter.

Is there a sandbox to try the API?

Yes, two ways. The live demos at demo.minipacs.net and vendo.minipacs.net are the real apps on synthetic data, connected to each other through the order-system API, and they reset every 6 hours. For DICOM work there are free de-identified sample studies and a transfer-syntax test set on this site, and the free in-browser viewer needs no account.

Can an AI agent book a demo for someone?

It can prepare it. The WebMCP tool prepare_demo_request opens the demo form on any page and fills in the person's name, work e-mail and phone. The person then completes the bot check and presses the button, and the one-time demo link is e-mailed to them. Nothing is sent without the person.

Is there an SDK or a CLI?

Not yet. Everything here is plain HTTP and JSON, MCP clients connect to the MCP server directly, and the order-system API is small enough to call without a library.

Own your archive: the MiniPACS + Vendo brand card for independent imaging centers

See it run, then get pricing.

Built for US imaging clinics and proven in production: millions of images already live on this exact stack. Flat $300 a month per location, no per-study fees, and you can export everything to standard DICOM whenever you want. Both demos are the real apps on synthetic data; enter a work email and we send a one-time link that opens them.

Get pricing