Wave

{
  "service_type": "platform",
  "base_url": "https://devdojo.com/wave",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Wave is a downloadable software starter kit (Laravel-based SaaS boilerplate). Pricing not specified on the provided page content; likely a one-time purchase or subscription for source code access via DevDojo."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "SaaS starter kit / boilerplate for building subscription-based web applications",
    "Built on Laravel and PHP",
    "User authentication and registration scaffolding",
    "Subscription billing integration (Stripe, Paddle, etc.)",
    "User dashboard and admin panel templates",
    "Blog and content management scaffolding",
    "Theme/template system for frontend customization",
    "API scaffolding for building out endpoints",
    "Documentation and community support",
    "Deployable full-stack codebase"
  ],
  "raw_analysis": "Wave is a developer tool, not an operating platform with a hosted API. It is a software starter kit (boilerplate) from DevDojo designed to accelerate building SaaS applications. It ships as source code (Laravel/PHP stack) that developers download, customize, and self-host. As such, it has no public REST API of its own, no hosted service endpoints, and no authentication surface for third-party integrations. Its 'capabilities' are the features baked into the kit: auth, billing, admin dashboard, blog, theming, and user management scaffolds. Integrations would come from the Laravel ecosystem (Stripe, Paddle, Mail providers, etc.) rather than from Wave as a service. Maturity: DevDojo is an established developer education brand; Wave has an active community but as a boilerplate its maturity should be judged by code updates and community support rather than uptime/SLA. Pricing is not exposed in the provided content; it typically involves a purchase/subscription to access the repo. No rate limits apply since there is no hosted API. Recommend treating Wave as a code asset rather than an API provider: Prowl should not expect to call it, but could note it as a template for teams building SaaS products."
}

2/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.0,
    "response_parseability": 6.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 8.0,
    "latency": 6.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "type": "one_time_or_subscription",
    "notes": "Pricing not explicitly surfaced in provided content; likely a one-time purchase or subscription via DevDojo for source code access. Unknown exact figure."
  },
  "issues": [
    "No /llms.txt endpoint (404) — agents cannot easily discover machine-readable platform metadata.",
    "Pricing model not clearly specified on the landing page content, forcing users/agents to dig deeper.",
    "Homepage latency ~851ms is acceptable but not fast for a lightweight marketing site.",
    "No public API surface advertised — it's a downloadable boilerplate, not a hosted agent-friendly service."
  ],
  "recommendations": [
    "Publish an /llms.txt with a concise description, pricing, docs links, and capability summary for AI agents.",
    "Surface pricing clearly in page content and structured data (JSON-LD) for easy parsing.",
    "Improve homepage response time (target <500ms) via caching/CDN.",
    "Provide a machine-readable feature/pricing JSON endpoint so agents can recommend the product without scraping.",
    "Clarify authentication flow for purchasing/downloading (magic link or SSO would boost auth_simplicity to 10)."
  ]
}