Headless Wp Starter

{
  "service_type": "platform",
  "base_url": "https://archive.postlight.com/labs/wordpress-react-starter-kit",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "note": "Open-source starter kit hosted on a Postlight labs archive page; no paid tiers or subscription pricing."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "WordPress + React starter kit / boilerplate",
    "Headless WordPress setup via WP REST API",
    "Server-side rendering with React",
    "One-step scaffolding / project bootstrap",
    "Open-source repository (developer resource)"
  ],
  "raw_analysis": "Headless WP Starter (WordPress + React Starter Kit) is a developer-focused open-source starter kit published by Postlight. It is not a hosted REST API service, but a code template/repository that helps developers spin up a headless WordPress backend paired with a React frontend in a single step. The URL points to an archived Postlight labs page, indicating the project is likely no longer actively maintained at that location and that the primary artifact is source code (typically on GitHub).\n\nIntended audience: web developers and teams who want to decouple WordPress as a CMS from a React presentation layer, using the WordPress REST API for content delivery. The kit typically includes server-side rendering, routing, and build tooling.\n\nMaturity: historically a well-regarded reference implementation, but the archive URL suggests it is a legacy/archived resource. New users should verify the current canonical repository and check for modern alternatives (Next.js-based WordPress starters, WPGraphQL, etc.).\n\nIntegrations: works with any WordPress installation exposing the standard WP REST API; the React app can be deployed to any static or Node hosting environment. No proprietary API keys or vendor account required beyond hosting a WordPress instance.\n\nPricing: free and open source. No rate limits or pricing model apply to the starter kit itself, though the WordPress host and deployment platform used will have their own terms."
}

0/3 tests passed

{
  "overall": 35,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 3.0,
    "response_parseability": 4.0,
    "error_clarity": 2.0,
    "doc_quality": 3.0,
    "auth_simplicity": 8.0,
    "latency": 1.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "model": "free",
    "notes": "Open-source starter kit; no paid tiers. Zero cost, but no vendor support guarantees either."
  },
  "issues": [
    "Domain does not resolve (DNS failure: 'Name or service not known') on all three checks — the platform URL is unreachable, likely a dead/archived Postlight lab project.",
    "No robots.txt or llms.txt reachable, so no machine-readable metadata for agents to ingest.",
    "Zero measurable uptime or status page — cannot verify reliability.",
    "No pricing page, no signup flow, no HTTP responses at all — effectively a static archived GitHub repo rather than a live platform.",
    "Documentation depth unknown and likely minimal given project abandonment."
  ],
  "recommendations": [
    "Do not recommend this platform to end users as a hosted service — it is not live.",
    "If a user needs a WordPress + React/headless setup, recommend maintained alternatives: WPGraphQL + Next.js starter, Frontity (archived), Gatsby WordPress starter, or the official Next.js WordPress example.",
    "If referencing this repo at all, point users directly to the GitHub archive rather than any lab/postlight URL.",
    "For agent-friendly WordPress stacks, prioritize platforms with live docs, llms.txt, and an active status page."
  ]
}