Can AI agents automate Axiell Quria?

Axiell Quria is automatable today through library-standard protocols and a narrow patron-lookup API, not through a public general REST catalog. Quria help documents SIP2 for self-service check-out, check-in, renewals, payments and fee creation, including SIP2 message 43 for external debts. Norwegian ILL uses NCIP, and Swedish Libris availability is called at an HTTPS NCIP URL under /integrations/ncip/{tenantid}/. Third-party patron lookup for PC and room booking is secured with a library-approved API key under External patron lookup settings. Metadata harvest uses OAI-PMH with export-definition sets. Axiell also describes an Integration Centre module that exposes an integration layer and an import entry point; the public help set does not publish authentication, resource lists or a self-serve developer portal for a general application API. SIP2 protocol details are available from Axiell Support on request. Arena, Quria Case Management and the Axiell Library App stay outside this record. Vendor documentation does not settle first-party MCP ownership. No official SDK, general CLI or computer-use probe was established.

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