Ex Libris APIs

{
  "service_type": "platform",
  "base_url": "https://developers.exlibrisgroup.com",
  "auth_method": "api_key",
  "auth_config": {
    "api_key_header": "Authorization",
    "api_key_format": "apikey {API_KEY}",
    "key_provisioning": "Alma API keys are generated via the Ex Libris Developer Network after registering an application. Users must be authenticated with an Alma institution account and have appropriate roles/permissions.",
    "docs_url": "https://developers.exlibrisgroup.com/alma/apis"
  },
  "endpoints": [
    {
      "name": "Alma REST APIs",
      "url": "https://developers.exlibrisgroup.com/alma/apis",
      "description": "Comprehensive REST API suite covering Alma library management functions: acquisitions, cataloging, fulfillment, users, configuration, analytics, and more."
    },
    {
      "name": "Alma API Authentication",
      "url": "https://developers.exlibrisgroup.com/alma/apis/",
      "description": "Documentation on generating and using API keys for Alma REST APIs."
    },
    {
      "name": "Ex Libris Developer Network",
      "url": "https://developers.exlibrisgroup.com",
      "description": "Portal for all Ex Libris product APIs, including Alma, Primo, Rosetta, Leganto, Esploro, and others."
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "The URL provided is malformed (https://exlibrisgroup.com:tasklists) and does not resolve to a usable API or product page. Pricing is not publicly standardized; Ex Libris products are typically licensed as enterprise subscriptions to institutions. API access is included with product subscriptions, but costs are bundled."
    }
  },
  "rate_limits": {
    "documented": false,
    "notes": "Ex Libris does not publish universal rate limits. Limits may vary by API and institution subscription. Contact Ex Libris support or your account representative for specific quotas."
  },
  "capabilities": [
    "Library management system APIs (Alma)",
    "Library discovery and delivery APIs (Primo)",
    "Digital asset management APIs (Rosetta)",
    "Reading list and course reserve APIs (Leganto)",
    "Research information management APIs (Esploro)",
    "API key authentication",
    "Developer portal with documentation and community"
  ],
  "raw_analysis": "Ex Libris (now part of Clarivate) provides a suite of library and research management platforms used by academic and research institutions worldwide. The URL given (https://exlibrisgroup.com:tasklists) appears to be malformed or incorrectly pasted; it is not a valid API endpoint. The descriptive text clearly points to the Ex Libris Developer Network (https://developers.exlibrisgroup.com) as the actual developer portal.\n\nEx Libris offers REST APIs primarily through its flagship products: Alma (library management services), Primo (discovery and delivery), Leganto (course resource lists), Rosetta (digital preservation), Esploro (research information management), and others. The Alma REST APIs are the most mature and widely documented, covering acquisitions, cataloging, fulfillment, user management, and analytics. API access requires an API key, generated after registering an application in the Developer Network. Authentication uses an API key passed in the Authorization header (format: 'apikey {API_KEY}').\n\nThe platform is enterprise-grade and designed for academic libraries, research institutions, and consortia. It is highly mature, with a large existing user base and extensive documentation. Integration exists with other library systems, learning management systems (via Leganto and Alma), and institutional authentication systems (SAML, Shibboleth, LDAP). However, direct public API endpoints are not exposed without an institutional subscription and API key. Pricing is custom/enterprise, typically negotiated as part of a broader product subscription. No public rate limits are documented; limits are likely enforced per institution and per API. For developers, the Developer Network is the central hub for API documentation, sample code, and community forums."
}

2/3 tests passed

{
  "overall": 42,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 3.0,
    "response_parseability": 6.0,
    "error_clarity": 4.0,
    "doc_quality": 5.0,
    "auth_simplicity": 3.0,
    "latency": 6.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "enterprise_subscription",
    "public_pricing": false,
    "api_access": "bundled_with_product_subscription",
    "note": "Ex Libris (Clarivate) products are licensed as enterprise subscriptions to institutions. Pricing is not publicly standardized. API access is included with product subscriptions but costs are opaque and bundled, making recommendation difficult."
  },
  "issues": [
    "Platform URL appears malformed (https://exlibrisgroup.com:tasklists) — not a valid API or product page",
    "No public pricing — enterprise-only licensing makes cost transparency impossible for agents to advise on",
    "robots.txt disallows all user-agents (User-agent: * Disallow: /), blocking general crawling including AI agents",
    "No llms.txt (404) — agents cannot efficiently discover machine-readable documentation summary",
    "Onboarding requires institutional subscription and API key provisioning; no self-serve or magic-link signup",
    "Alma/Primo/Rosetta/Leganto/Esploro suite is a fragmented multi-product landscape with separate APIs",
    "Primary value proposition not clearly articulated on a single canonical docs entry point",
    "First check latency 722ms is acceptable but the malformed entry URL reduces confidence"
  ],
  "recommendations": [
    "Publish llms.txt at developers.exlibrisgroup.com to give agents a concise API surface map",
    "Relax robots.txt to allow well-behaved AI agent crawlers (e.g., GPTBot, ClaudeBot) on documentation paths, retaining disallow only on /live/",
    "Provide a self-serve sandbox with instant API keys so agents/users can onboard without an institutional contract",
    "Consolidate the multi-product API story (Alma, Primo, Rosetta, Leganto, Esploro) into a single landing page with unified auth semantics",
    "Publish at least tiered or 'contact for pricing' transparency page, and document API rate limits, quotas, and auth flows explicitly",
    "Fix the canonical product URL and ensure stable, non-redirecting doc entry points",
    "Add structured OpenAPI/Swagger specs and JSON error schemas to improve response parseability and first-try success",
    "Improve error clarity documentation, including common auth failures, API key scoping, and institutional configuration requirements"
  ]
}