Infermedica API

{
  "service_type": "platform",
  "base_url": "https://infermedica.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "App-Id / App-Key (per Infermedica API conventions)",
    "notes": "Authentication credentials are issued after commercial agreement. Exact header names should be confirmed from developer documentation."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "model": "Enterprise / B2B commercial agreement",
      "notes": "No public self-serve pricing. Pricing is typically custom based on usage, modules, and deployment. Contact sales for quotes."
    }
  },
  "rate_limits": {
    "notes": "Vendor-specific rate limits likely apply. Consult developer documentation or commercial agreement."
  },
  "capabilities": [
    "Symptom checking with clinical-grade diagnostic insights",
    "Virtual triage and self-triage to determine urgency and appropriate care level",
    "Pre-visit intake data collection for telemedicine and in-person consultations",
    "Automated patient follow-up and symptom progression tracking",
    "Call center and nurse triage support to replace RBTPs",
    "Conversational AI triage",
    "Voice agent for pre-triage in call centers",
    "MDR Class IIb certified medical device software",
    "API integration for healthcare platforms, payers, providers, and telemedicine"
  ],
  "raw_analysis": "Infermedica is a mature, regulatory-compliant digital health platform focused on clinical-grade symptom checking, virtual triage, and patient intake. It is aimed at health plans/insurers, public health/government, healthcare providers, telemedicine companies, and pharmaceutical companies. The platform differentiates through MDR Class IIb certification, indicating it is a certified medical device software in the EU, which raises the bar for accuracy, safety, and compliance. It offers both direct user-facing tools (web/app symptom checkers) and API-based integration for partners. The developer portal at developer.infermedica.com provides API reference and documentation, confirming that a public-facing REST API exists, though access is gated behind commercial agreements rather than open self-serve signup. The API likely supports endpoints for symptom assessment, triage recommendations, intake, and follow-up. Authentication appears to be API key/credential based (common in B2B health APIs), though exact details should be verified from the developer documentation. Pricing is enterprise/custom, with no public tiers. Overall, this is a high-maturity, clinically validated platform suitable for regulated healthcare use cases, not a lightweight or free developer tool."
}

3/3 tests passed

{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 4.0,
    "response_parseability": 7.5,
    "error_clarity": 7.0,
    "doc_quality": 8.0,
    "auth_simplicity": 3.5,
    "latency": 10.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "enterprise_b2b",
    "self_serve": false,
    "transparency": 2.0,
    "notes": "No public pricing; requires custom sales agreement. Not ideal for agent-led recommendations or trials."
  },
  "issues": [
    "No self-serve signup or trial — onboarding requires a sales conversation.",
    "Pricing is fully opaque (custom enterprise contract), making cost estimation impossible for agents.",
    "Auth model unclear from public docs; likely complex B2B/enterprise integration (API keys via contract).",
    "MDR Class IIb regulatory status implies lengthy compliance onboarding for developers.",
    "No public API sandbox or quick-start credential flow visible."
  ],
  "recommendations": [
    "Publish a public developer sandbox with instant API keys (or magic-link auth) to enable first-try success.",
    "Add transparent tiered pricing or usage-based calculator so agents can shortlist the product confidently.",
    "Expose an OpenAPI spec and Postman collection to boost response parseability and reduce integration friction.",
    "Provide a clear 'limitations & compliance' doc page (MDR scope, data residency, certification boundaries) to improve error clarity.",
    "Expand llms.txt with machine-readable capability, pricing, and onboarding metadata for agent consumption."
  ]
}