Can AI agents automate KulturIT Primus?

KulturIT Primus is automatable today only after a museum publishes collection data into eKultur's public surfaces. KulturIT states that eKultur APIs retrieve published data about named persons from DigitaltMuseum and from KulturNav datasets. DigitaltMuseum's public API searches a Solr index and returns JSON or XML, using an api.key query parameter; a documented demo key is published. KulturNav's API is HTTP GET JSON for published content and is not authenticated. Those interfaces are not a Primus collection-management API: they do not catalogue objects, run Spectrum procedures, or write into a museum's Primus database. Primus remains the staff collections system. Inside eKultur, Primus is connected to DigitaltMuseum so objects can be published from Primus, and to KulturNav so shared terminology can be pulled into cataloguing. Primus 10 is a cloud collections solution that replaces Primus 7.5 win and web, with login through eKulturportalen; KulturIT is still rolling it out in 2026, so some museums remain on 7.5. KulturIT states that more than 200 museums and heritage institutions in Norway and Sweden use Primus; that figure is vendor-declared. Vendor documentation does not settle first-party MCP ownership. Zapier, Make, Power Automate and n8n catalogs were not opened. Computer-use viability is unassessed. DigitaltMuseum as a standalone public portal, Axiell Collections and TMS stay outside this record.

Best path today: api · Overall automatability: 4/10