DLx

{
  "service_type": "platform",
  "base_url": "http://danielhieber.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {"type": "unknown", "details": {}},
  "rate_limits": {},
  "capabilities": [
    "Language documentation",
    "Linguistic data modeling",
    "Lexicon management",
    "Morphological analysis",
    "Text corpus annotation",
    "Cross-linguistic data interoperability"
  ],
  "raw_analysis": "DLx (Digital Linguistics) is a suite of open-source software tools and specifications for language documentation and linguistic data management, created by Daniel Hieber. The URL http://danielhieber.com appears to be a personal website, not the primary DLx project site. The actual project is hosted on GitHub under 'digitallinguistics' and provides a REST API? Although the API is not publicly documented with endpoints on that domain. Based on available public information, DLx includes a schema for linguistic data (DLx JSON), a JavaScript library (dlx), and potentially a web API. The API included in DLx may require authentication for write operations, but the landing page likely offers no public API. The stack is targeted at linguists, language documentation researchers, and developers building language tools. The project appears mature with multiple components (published on npm, GitHub org), open-source, and free to use. No pricing, rate limits, or public endpoints can be confirmed. Integrations are likely with linguistic databases, annotation tools, and other language technology. Because the provided URL points to a personal site rather than the API itself, the analysis is based on broader knowledge of DLx."
}

0/3 tests passed

{
  "overall": 31,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 2.0,
    "response_parseability": 5.0,
    "error_clarity": 2.0,
    "doc_quality": 2.0,
    "auth_simplicity": 5.0,
    "latency": 0.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "transparent": false,
    "notes": "No pricing data returned; cannot normalize to tiers or usage units."
  },
  "issues": [
    "All probe requests failed with ~30s timeouts (30.5s, 30.5s, 33.3s) and null status codes — platform appears unreachable or entirely unresponsive from agent infrastructure.",
    "Latency is far beyond any acceptable threshold; every check exceeded 30 seconds without a response.",
    "No security headers observed on any response.",
    "No llms.txt present, so agents have no machine-readable entry point describing the platform.",
    "Pricing model is unknown — no public, machine-readable pricing to recommend to users.",
    "No API/export surface evidenced; response_parseability capped despite the domain being data-centric (linguistics)."
  ],
  "recommendations": [
    "Restore service availability and publish a status page — repeated 30s+ timeouts make the platform a non-recommendation for any agent workflow.",
    "Add an llms.txt and a machine-readable pricing/endpoint manifest so agents can onboard without human discovery.",
    "Publish OpenAPI/JSON schemas for lexicon, morphological, and corpus endpoints — the domain naturally supports structured output and would raise parseability to 9-10.",
    "Document auth (magic link, SSO, or API keys) in a public getting-started guide to lift auth_simplicity.",
    "Serve a fast static landing page (<500ms) even if the app backend is slow, to avoid total latency failure.",
    "Clarify limitations, quotas, and licensing (often complex for linguistic corpora) in public docs to raise error_clarity."
  ]
}