カラーミーショップアプリストア API

{
  "service_type": "platform",
  "base_url": "https://app.shop-pro.jp",
  "auth_method": "oauth2",
  "auth_config": {
    "note": "Colorme Shop App Store uses OAuth 2.0 for app authorization against the Colorme Shop API; exact endpoints and scopes documented at developer.shop-pro.jp",
    "docs_url": "https://developer.shop-pro.jp/docs/colorme-api"
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "Colorme Shop itself is a paid e-commerce SaaS; the App Store API is provided to developers publishing apps on the store. Pricing for app developers not specified on the referenced page."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "e-commerce platform (Japanese shopping cart / storefront SaaS)",
    "public developer API (Colorme Shop API)",
    "App Store for third-party apps",
    "App Store API extending the base Colorme Shop API for published apps",
    "OAuth-based app authorization",
    "Store management (products, orders, customers) via API"
  ],
  "raw_analysis": "カラーミーショップアプリストア API (Colorme Shop App Store API) is an extension of the publicly available Colorme Shop API, provided by GMO Pepabo's Colorme Shop — a long-established Japanese e-commerce / shopping cart SaaS aimed at small and medium merchants. The API is intended for developers who publish apps on the Colorme Shop App Store (https://app.shop-pro.jp/).\n\nThe referenced URL (https://shop-pro.jp/?mode=inq) is a general inquiry/contact form on the main Colorme Shop site, not an API endpoint. The authoritative documentation lives at https://developer.shop-pro.jp/docs/colorme-api, which describes the base REST API (store info, products, orders, customers, etc.) and typically uses OAuth 2.0 for app authorization. The App Store API adds capabilities specific to apps distributed through the App Store (e.g., app lifecycle, installation/authorization events), though the exact endpoint list is not exposed in the provided snippet.\n\nMaturity: Colorme Shop is a mature, widely used platform in Japan (operated by GMO Pepabo). It has an established developer portal and documentation in Japanese. Integration ecosystem centers on the App Store and the public API.\n\nWho it's for: Japanese e-commerce merchants and third-party developers building integrations/apps for Colorme Shop stores.\n\nLimitations for this analysis: No public OpenAPI spec, endpoint list, or rate limit details are provided in the source snippet, so endpoints and rate_limits are left empty. Auth is assumed OAuth 2.0 based on typical Colorme Shop API documentation. Pricing for the API/App Store developer program is not stated."
}

2/3 tests passed

{
  "overall": 55,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 5.0,
    "response_parseability": 7.0,
    "error_clarity": 5.0,
    "doc_quality": 6.0,
    "auth_simplicity": 5.0,
    "latency": 6.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "note": "Colorme Shop is a paid Japanese e-commerce SaaS; App Store API pricing for developers is not clearly specified on the referenced page. No transparent pricing tiers available for agent recommendation."
  },
  "issues": [
    "No llms.txt (404) — agents have no machine-readable platform summary to parse",
    "Primary value prop is only discoverable in Japanese context; unclear English positioning for global AI agent recommendation",
    "Pricing model opaque — cannot state cost to users, which blocks confident recommendation",
    "OAuth-based app authorization requires developer registration flow, not agent-friendly onboarding",
    "Website latency ~1.4s on primary page (not ideal for high-frequency agent checks)",
    "Documentation is domain-specific (Japanese e-commerce) and may be hard for agents to summarize succinctly"
  ],
  "recommendations": [
    "Add /llms.txt with concise English + Japanese platform summary, capabilities, and pricing",
    "Publish a clear pricing page for App Store API developers (free tier? revenue share?)",
    "Provide English-language API docs and getting-started guide for global agent discoverability",
    "Expose structured OpenAPI/Swagger spec for Colorme Shop API to improve response_parseability",
    "Reduce homepage TTFB below 500ms to improve latency score",
    "Document OAuth scopes and rate limits clearly so agents can set user expectations on first try"
  ]
}