Access the archive's administrative REST endpoints directly under the /dcm4chee-arc/ context root; for example, GET /dcm4chee-arc/ctrl/status returns archive run state, GET /dcm4chee-arc/aets lists configured AE titles, and GET /dcm4chee-arc/storage lists storage descriptors.
Use GET /dcm4chee-arc/aes to retrieve full Application Entity objects including network connection details for all configured AEs.
To explore and test all available REST operations (including device config, queue management, and export scheduling), consult the Swagger UI pointing at the published openapi.json: http://petstore.swagger.io/index.html?url=https://dcm4che.github.io/dcm4chee-arc-light/swagger/openapi.json
DICOMweb clinical operations (QIDO-RS, WADO-RS, STOW-RS, UPS-RS, and archive-specific study/patient management) are served under /dcm4chee-arc/aets/{aet}/rs, where {aet} is the Application Entity Title.
The web UI is served at /dcm4chee-arc/ui2/ and is distinct from the REST API paths; do not mix UI path references with API calls.
Known gotchas
Administrative config endpoints (status, aets, storage, reject, etc.) sit directly under /dcm4chee-arc/, while DICOMweb service endpoints require an AET segment (/dcm4chee-arc/aets/{aet}/rs/); confusing the two produces 404 errors.
The /ui2/ path is the web interface, not an API base path; REST calls made to /ui2/rs/ will not resolve to archive REST services.
When Keycloak securing is enabled, Web Application configurations with dcmWebServiceClass and dcmWebServicePath must match the incoming request path, or the archive returns 404 regardless of credentials.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp