Can AI agents automate Axiell Mikromarc?

The best evidenced path into Axiell Mikromarc is a vendor-declared open API for connecting add-on systems, not a public endpoint catalog. Axiell Sweden states that the system has an open API so libraries can attach add-on systems. Axiell Finland repeats that claim. Opened vendor pages do not publish protocol kinds, authentication, resource lists or a self-serve developer portal, so coverage stays unknown. Axiell's Norwegian Mikromarc wiki names OAI-PMH as a Mikromarc 3 harvest interface used toward Bibsøk, and the Swedish wiki documents MARCXML batch import from Libris through the catalog client. Those are library-data paths, not a general application API. Mikromarc+ on the Norwegian product page is the same ILS bundled with BIB-Control reporting and Arena website publishing. Arena stays outside this record: the opened pages do not show a shared public API between Mikromarc and Arena. Axiell Sweden names Quria as the logical next step for Mikromarc customers seeking a modern web-based library system, and still sells Mikromarc as a living, centrally operated product, including to more than 200 Swedish special and research libraries as a vendor-declared figure. That is a successor relationship, not a merge, and it is not an end-of-support notice. This record is not Axiell Quria, Bibliofil, Koha or Ex Libris Alma. Vendor documentation does not settle first-party MCP ownership. Zapier, Make, Power Automate and n8n catalogs were not opened. No official SDK, CLI or computer-use probe was established.

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