iQualify Management API

{
  "service_type": "platform",
  "base_url": "https://iqualify.com",
  "auth_method": "api_key",
  "auth_config": {
    "token_request_method": "manual",
    "notes": "API access token must be requested after registering with iQualify; details on navigation to token request are truncated in source data."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Registration required; pricing tiers not specified in provided data."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "learning experience management",
    "instance data access",
    "API access token provisioning",
    "LMS / learning platform integration",
    "content and course management operations"
  ],
  "raw_analysis": "iQualify is a learning management / online learning platform (LMS) that provides a Management API for building and managing learning experiences using instance data. It is aimed at organizations, educators, and developers building or integrating online learning content. The API is described as offering 'management responses' for building learning experiences, implying CRUD-style operations over courses, learners, and content, though no explicit endpoint list is provided. Authentication is token-based: after registering with iQualify, users can request an API access token. The exact navigation path for obtaining the token is truncated in the source, so the precise flow cannot be confirmed. Maturity appears moderate-to-established given a commercial product with documentation, but no versioning, rate limit, or pricing details are available in the provided content. Integrations likely include LMS/CMS platforms and data workflows, but specifics are not stated. Because the documentation excerpt is incomplete and no endpoints are enumerated, endpoint discovery would require accessing the full developer docs (likely at a subdomain such as docs.iqualify.com or an API portal). The platform is fundamentally a SaaS product with a developer-facing management API rather than a pure API product, so its pricing model is likely subscription-based but is unverified here."
}

0/3 tests passed

{
  "overall": 18,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 2.0,
    "response_parseability": 3.0,
    "error_clarity": 2.0,
    "doc_quality": 2.0,
    "auth_simplicity": 3.0,
    "latency": 0.5,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "notes": "Pricing tiers not specified in provided data; registration required before any pricing or capability details are exposed."
  },
  "issues": [
    "All three checks (website uptime, robots.txt, llms.txt) failed with null status codes and ~30 second timeouts — the platform appears unreachable or severely degraded from the agent's perspective.",
    "No llms.txt means agents have no machine-readable guidance for LLM/agent usage.",
    "No robots.txt response resolves means crawler/agent access policy is unknown.",
    "Pricing model is unspecified, making cost-based recommendations impossible for agents.",
    "Capabilities are described only in high-level terms (learning experience management, instance data access, API access token provisioning) with no endpoint or schema detail.",
    "No status page or uptime signal observed; perceived reliability is very low.",
    "Auth is not marked as 'Sign in with Notlogin' or SSO/magic link — describes registration requirement only, suggesting a traditional complex onboarding."
  ],
  "recommendations": [
    "Publish an llms.txt and stable robots.txt so agents can discover and respect access policies.",
    "Fix upstream availability — 30s timeouts on all three probes indicate infrastructure or DNS problems that will block any agent integration.",
    "Document the API surface: endpoints, auth flow for token provisioning, and example requests/responses.",
    "Publish transparent pricing tiers and any usage limits for the API.",
    "Expose a public status page or uptime metrics so agents can factor reliability into recommendations.",
    "Adopt 'Sign in with Notlogin' or magic-link auth to let agents onboard without a human-in-the-loop registration dance.",
    "Provide structured exports (JSON schemas, OpenAPI spec) to improve parseability and first-try success."
  ]
}