API for the COVID-19 Tracking QR Code Signin Server.

{
  "service_type": "platform",
  "base_url": "https://c19qrserver.local",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "QR code check-in for contact tracing",
    "COVID-19 venue sign-in tracking",
    "contact tracing data collection",
    "exposure notification support",
    "local/self-hosted deployment"
  ],
  "raw_analysis": "The provided service is described as the API for the COVID-19 Contact Tracing QR Code Signin Server, hosted at https://c19qrserver.local. The .local top-level domain is reserved for multicast DNS (mDNS) on local networks and is not globally routable on the public internet. This indicates the server is intended for private, on-premises, or local-network deployment rather than a publicly accessible SaaS platform. As such, conventional analysis of public API maturity, third-party integrations, and broadly documented endpoints does not apply in the usual sense.\n\nPurpose and audience: The platform exists to support COVID-19 contact tracing workflows. Users (venues, businesses, event organizers, or public health authorities) would generate QR codes that patrons scan to register their presence, enabling subsequent contact tracing if an exposure occurs. It has clear relevance to public health administration and venue management during the COVID-19 pandemic era. Maturity is likely that of a niche or custom-built tool: no public documentation, no discoverable REST endpoint catalog, and no evidence of a maintained open API portal.\n\nAuthentication and interfaces: No authentication method or endpoint catalog is provided. Given the local/private nature and typical contact-tracing deployments, it may use no auth (open on a trusted local network), API keys, session-based auth, or basic auth — none can be confirmed. No base URL for public API discovery exists, and 'https' on a .local address may imply a self-signed certificate.\n\nIntegrations and ecosystem: There is no evidence of public integrations with identity providers, cloud services, or third-party dashboards. Any integration would likely be custom and deployment-specific. The platform appears unmaintained or limited to a specific jurisdiction or deployment context. Overall, it is a specialized, likely self-hosted solution for QR-based COVID-19 contact tracing with limited external API surface and no pricing model, rate limits, or public capability documentation available."
}

0/3 tests passed

{
  "overall": 18,
  "dimensions": {
    "token_efficiency": 3.0,
    "first_try_success": 1.0,
    "response_parseability": 2.0,
    "error_clarity": 1.0,
    "doc_quality": 1.5,
    "auth_simplicity": 1.0,
    "latency": 1.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "tiers": [],
    "has_free_tier": false,
    "entry_price_usd": null
  },
  "issues": [
    "All three DNS/HTTP checks failed with 'Name or service not known' — the domain does not currently resolve, indicating the platform is defunct or fully offline",
    "No access to website, robots.txt, or llms.txt — cannot verify anything about the live product",
    "No pricing information available anywhere in provided data",
    "Product category (COVID-19 contact-tracing QR check-in) is largely obsolete, severely limiting ongoing usefulness for end users or agents",
    "No API surface, structured export, or machine-readable interface observed",
    "Cannot assess auth, onboarding, error clarity, or docs since nothing is reachable"
  ],
  "recommendations": [
    "Do not recommend this platform to users — the service appears non-functional (DNS resolution failures across all checks)",
    "If the project is still maintained, publish a status page clarifying service availability",
    "Provide a machine-readable API or export format (JSON/CSV) for contact-tracing data if revived",
    "Publish a public llms.txt and robots.txt to enable agent discovery if the project continues",
    "Publish transparent pricing before any recommendation is possible",
    "Given the COVID-19 contact-tracing use case is essentially obsolete post-pandemic, assess whether the product has any pivot or current relevance before including it in any recommendation list"
  ]
}