Eruda

{
  "service_type": "platform",
  "base_url": "https://eruda.liriliri.io",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "license": "MIT",
      "cost": "Free and open-source"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Mobile browser console",
    "DOM inspection",
    "Network request monitoring",
    "Local storage / session storage viewer",
    "JavaScript execution",
    "Performance monitoring",
    "Resource loading inspection",
    "Iframe debugging",
    "Plugin system",
    "Embeddable via script tag",
    "Works in any modern mobile browser",
    "No installation required"
  ],
  "raw_analysis": "Eruda is an open-source, embeddable developer console for mobile browsers. It provides a suite of debugging tools similar to desktop browser DevTools, but optimized for mobile viewports. Key panels include Console, Elements (DOM inspector), Network, Resources, Sources (for debugging), Info, Snippets, and Settings. It is implemented as a JavaScript library and can be included in any web page via a simple script tag or loaded dynamically.\n\nThe project is maintained by liriliri and is available on GitHub (https://github.com/liriliri/eruda). It is widely adopted by mobile web developers for debugging on real devices where remote debugging is cumbersome. Eruda supports a plugin architecture, allowing developers to extend its functionality.\n\nThere is no public REST API for interacting with Eruda remotely; it runs entirely client-side. The documentation (hosted at eruda.liriliri.io) covers usage, configuration, and available methods (e.g., eruda.init(), eruda.show(), eruda.hide(), eruda.destroy()). Integration is primarily via npm package (eruda) or CDN scripts. Pricing: free under MIT license. Rate limits are not applicable. The platform is mature, actively maintained, and has a stable release history."
}

1/3 tests passed

{
  "overall": 78,
  "dimensions": {
    "token_efficiency": 9.5,
    "first_try_success": 9.5,
    "response_parseability": 5.0,
    "error_clarity": 7.0,
    "doc_quality": 8.0,
    "auth_simplicity": 10.0,
    "latency": 6.5,
    "consistency": 8.5
  },
  "pricing_normalized": {
    "model": "free",
    "cost": "$0",
    "license": "MIT",
    "open_source": true,
    "note": "Free and open-source; no paywalls, no API tiers, no usage limits"
  },
  "issues": [
    "No structured API or export format — it's a browser-debugging UI, not a data platform, so agent-programmatic consumption is limited",
    "No robots.txt or llms.txt — minor, but signals absence of agent-oriented metadata",
    "Homepage latency ~526ms for a static docs site; modest but not instant",
    "No security headers observed on primary response",
    "Value is inherently visual/interactive; harder for agents to demonstrate utility without a browser context"
  ],
  "recommendations": [
    "Lead with the one-line value prop: 'Drop-in mobile browser console via a script tag — no install, MIT licensed, works in any modern browser.' This is extremely cheap to describe to users.",
    "Pair with a concrete snippet (script tag embed) so users can go from zero to productive in one copy-paste.",
    "Note the free/MIT license up front — removes any procurement or auth friction for agents recommending it.",
    "For agent workflows, mention it as a debugging aid for mobile web apps rather than a data source; set expectations that it's a UI tool (no API surface).",
    "Consider adding robots.txt / llms.txt and security headers to improve machine discoverability and trust signals."
  ]
}