BigCommerce

{
  "service_type": "platform",
  "base_url": "https://bigcommerce.com",
  "auth_method": "oauth2",
  "auth_config": {
    "flows": {
      "authorization_code": {
        "authorization_url": "https://login.bigcommerce.com/oauth2/authorize",
        "token_url": "https://login.bigcommerce.com/oauth2/token"
      },
      "client_credentials": {}
    },
    "notes": "BigCommerce REST Management APIs use OAuth 2.0 with scopes. Storefront GraphQL API can be accessed via storefront tokens, customer access tokens, or GraphQL API accounts with valid JWT. Legacy Basic Auth (X-Auth-Token / X-Auth-Client) also exists for older store API tokens.",
    "docs": "https://developer.bigcommerce.com/docs/api"
  },
  "endpoints": [
    {
      "name": "Management REST API (v3)",
      "base_url": "https://api.bigcommerce.com/stores/{store_hash}/{version}",
      "docs": "https://developer.bigcommerce.com/docs/api"
    },
    {
      "name": "Storefront GraphQL API",
      "base_url": "https://store-{store_hash}.mybigcommerce.com/graphql",
      "docs": "https://developer.bigcommerce.com/docs/storefront/graphql"
    },
    {
      "name": "Catalyst Storefront Framework Docs",
      "url": "https://developer.bigcommerce.com/docs/storefront/catalyst/getting-started"
    },
    {
      "name": "Webhooks",
      "docs": "https://developer.bigcommerce.com/docs/api/webhooks"
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "notes": "Subscription-based SaaS with tiers (e.g., Essentials for small business, Standard, Plus, Pro, Enterprise). Exact pricing varies and isn't published in a canonical price list in the provided content.",
      "tiers_docs": "https://www.bigcommerce.com/essentials/",
      "sales_contact": "https://www.bigcommerce.com/contact/"
    }
  },
  "rate_limits": {
    "notes": "BigCommerce applies API rate limits per store/API account, typically expressed as requests per hour with separate limits for certain endpoint groups (e.g., Storefront API, cart API). Exact numbers should be looked up in official docs.",
    "docs": "https://developer.bigcommerce.com/docs/api"
  },
  "capabilities": [
    "Open, composable ecommerce platform (headless-capable)",
    "REST Management API (v3) for catalogs, orders, customers, content, pricing, shipping, taxes, etc.",
    "Storefront GraphQL API for storefront data and checkout on supported themes/stacks",
    "GraphQL Admin API",
    "Webhooks for real-time event notifications",
    "OAuth 2.0 app authorization and scoped API tokens",
    "Headless commerce with Catalyst storefront framework (Next.js-based)",
    "Multi-storefront (multi-site) support",
    "B2B Edition for wholesale/B2B ecommerce",
    "Omnichannel and marketplace/ads channel integrations",
    "App marketplace with third-party integrations",
    "Theme/stencil templating system for traditional storefronts",
    "International/multi-currency, multi-language storefront support",
    "Enterprise-grade security and compliance (Trust Center)"
  ],
  "raw_analysis": "BigCommerce (https://bigcommerce.com) is a mature, enterprise-grade SaaS ecommerce platform aimed at SMBs up to large enterprises. It is explicitly positioned as an 'open, composable ecommerce platform' supporting headless commerce, multi-storefront setups, B2B, wholesale, and omnichannel use cases. Notable product offerings include Essentials (small business), B2B Edition, Catalyst (a storefront framework), and an apps/integrations marketplace.\n\nFrom a developer perspective, BigCommerce exposes a robust set of APIs and integration surfaces, so this is not a platform without a public API. Primary programmatic access is via:\n- REST Management API (v3), hosted at https://api.bigcommerce.com/stores/{store_hash}/{version}.\n- Storefront GraphQL API for querying products, cart, checkout, and content from storefronts.\n- Admin GraphQL API.\n- Webhooks for event-driven integrations.\n\nAuthentication is OAuth 2.0-based, supporting authorization code flow for marketplace apps and client credentials / API accounts, with scopes and JWT usage for storefront tokens. Legacy API tokens (X-Auth-Token/X-Auth-Client) exist.\n\nPricing is subscription-based (no free public tier advertised in the given content, though Essentials targets small businesses). Rate limits are applied per store/API account, with different limits for specific API groups; exact numbers are documented in the developer center. The ecosystem is mature, with extensive developer documentation at developer.bigcommerce.com, official SDKs, an app marketplace, Catalyst docs, and a strong partner/integration network. For integration purposes, this is a first-class API platform with well-established SDKs and OAuth app support.\n\nThe provided content is largely marketing and legal/attribution information emphasizing canonical pages and citation guidelines; it does not grant training/reproduction licenses. No hallucinated commercial relationships should be inferred be

3/3 tests passed

{
  "overall": 74,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 6.0,
    "response_parseability": 9.0,
    "error_clarity": 7.0,
    "doc_quality": 8.5,
    "auth_simplicity": 6.5,
    "latency": 9.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "subscription",
    "tiers": ["Essentials", "Standard", "Plus", "Pro", "Enterprise"],
    "price_published": false,
    "notes": "Tiered SaaS subscription; exact prices not in provided content. Requires sales contact for Plus/Pro/Enterprise. Essentials is the low-end entry tier."
  },
  "issues": [
    "No canonical published price list in the provided content — agents cannot answer 'how much does it cost' without redirecting to sales/contact pages",
    "Auth for API access requires OAuth 2.0 app creation and scoped tokens; not a simple magic-link or one-step key generation",
    "Tier boundaries (what features unlock at which tier) are not clearly mapped in provided data, making feature-availability answers unreliable",
    "llms.txt exists but is thin on structured capability->endpoint mapping for agents"
  ],
  "recommendations": [
    "Publish a machine-readable pricing page (JSON or clearly structured HTML) with tier feature matrices so agents can answer cost/fit questions without escalation",
    "Expose a concise API quickstart with copy-paste token creation path to reduce onboarding friction",
    "Expand llms.txt with canonical API surface (REST v3, GraphQL Admin, Storefront GraphQL, Webhooks) and auth scopes for agent consumption",
    "Provide a public status page link in llms.txt for reliability signals",
    "Add explicit 'limitations' section in docs (rate limits, storefront API availability constraints on non-Catalyst themes)"
  ]
}