Spree

{
  "service_type": "platform",
  "base_url": "https://spreecommerce.org",
  "auth_method": "api_key",
  "auth_config": {
    "header_name": "X-Spree-Token",
    "format": "Bearer token or API key",
    "notes": "Spree uses API keys/tokens for REST API authentication. Admin API uses OAuth2. Platform itself is self-hosted, so auth is configured per deployment."
  },
  "endpoints": [
    {
      "name": "Storefront API",
      "url": "/api/v2/storefront",
      "method": "GET",
      "description": "Public-facing product, cart, and order endpoints"
    },
    {
      "name": "Platform API",
      "url": "/api/v2/platform",
      "method": "GET",
      "description": "Admin/management endpoints for products, orders, users"
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "model": "open_source",
      "license": "BSD-3-Clause",
      "notes": "Spree is free and open-source. Costs come from hosting, infrastructure, and optional Spree Commerce enterprise support/services."
    }
  },
  "rate_limits": {
    "notes": "No default rate limits enforced by the open-source platform; limits depend on self-hosted deployment infrastructure (e.g., reverse proxy, Rails Rack::Attack)."
  },
  "capabilities": [
    "Headless eCommerce",
    "Cross-border commerce",
    "B2B commerce",
    "Marketplace support",
    "REST API",
    "TypeScript SDK",
    "Next.js storefront",
    "Product catalog management",
    "Cart and checkout",
    "Order management",
    "Multi-currency",
    "Multi-store",
    "Plugin/extension ecosystem",
    "Open-source self-hosting"
  ],
  "raw_analysis": "Spree Commerce is a mature, open-source headless eCommerce platform built on Ruby on Rails. It provides REST APIs (v2 storefront and platform APIs) along with a TypeScript SDK and a reference Next.js storefront, enabling developers to build custom storefronts and integrations. It targets developers and businesses needing flexibility for cross-border, B2B, or marketplace commerce. The platform is self-hosted, so there is no single public SaaS API endpoint; instead, each deployment exposes its own API. Authentication is token/API-key based, with OAuth2 for admin operations. There are no global rate limits inherent to the software. The project has been around since 2007 and has a large community, with commercial support offered by Spree Commerce, Inc. It integrates with payment gateways, shipping providers, tax services, and other eCommerce tools via extensions. Overall, it is a highly customizable, developer-focused platform rather than a plug-and-play SaaS product."
}

2/3 tests passed

```json
{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 6.0,
    "response_parseability": 7.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 8.0,
    "latency": 9.5,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "open_source",
    "list_price": 0,
    "license": "BSD-3-Clause",
    "notes": "Free OSS; real cost is hosting/infra + optional enterprise support. No per-call API metering."
  },
  "issues": [
    "No /llms.txt (404) — agents cannot fetch a machine-readable platform summary.",
    "Robots.txt is stock WordPress plugin output and blocks /wp-admin and /track — signals the marketing site runs on WordPress, not directly informative about the actual API surface.",
    "No security headers on responses (no HSTS/CSP observed) — mild trust/consistency concern.",
    "No machine-readable pricing/feature manifest exposed; agents must scrape HTML or read docs manually.",
    "Self-hosting/complexity tax: production readiness requires infra decisions the agent must translate for a user.",
    "Auth is not a simple 'get a key and go' — it's install/deploy, so 'onboarding in minutes' only holds with container/cloud templates."
  ],
  "recommendations": [
    "Publish /llms.txt summarizing capabilities, install paths, and API entry points for agent consumption.",
    "Expose a structured JSON manifest (features, license, supported Rails/Ruby versions, extension list).",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) on the marketing site.",
    "Provide a 'quickstart in 60s' doc with docker-compose and a cloud one-click deploy link so agents can hand users a working instance fastest.",
    "If Spree Cloud/enterprise pricing exists, expose it as structured pricing data rather than prose.",
    "Document API auth (API keys/OAuth) explicitly on a single page with curl examples for orders/products."
  ]
}
```