# AX Check: stacksync.com Checked 2026-10-20. Pricing is clear, but no runnable quickstart or code exists yet 12 of 23 checklist items pass, mostly pricing and docs navigation. 10 items are unassessed: no quickstart, install commands, code samples, or API/MCP docs were found. ## Onboarding needs a login ## Coding sessions All three independent sessions (DeepSeek V4.1 Flash, Kimi K3, Qwen 3.8 Max) completed and successfully found and quoted the pricing page, correctly noting plan tiers, billing assumptions, and usage limits. None attempted a technical setup or install step, as no such task was part of their review. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/cad05653-0ccf-44ec-b948-1e8d4e61ec29) · [Read transcript](https://www.ax-check.com/stacksync.com/sessions/deepseek.json) Quoted list prices from the pricing page and named the assumptions: annual billing, sync and record allowances per tier, per-1K overage tiers, and API Proxy calls per day. (seq 14, seq 68, seq 104) #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained real Stacksync credentials. It built a stdlib Python script that calls the hosted API Proxy, then validated the wiring only with no token (local error) and a dummy token (401 from the live endpoint). No signup, API key generation, or authenticated operation against Stacksync or a connected app (HubSpot, Salesforce, etc.) occurred. The agent explicitly flagged the missing credential as a blocker ending the session. Event 102: ```text HTTP 401: {"msg":"Incorrect token: token is absent, malformed, incorrect, expired, suspended or inexistent."} ``` Event 104: ```text I can't complete an authenticated run because I don't have a Stacksync workspace/service token, and minting one requires signing up (Starter is self-serve paid). ``` Event 104: ```text Give me a `STACKSYNC_API_PROXY_TOKEN` (after connecting HubSpot/Airtable/Salesforce in the UI) and I'll run the example end-to-end and show the real response. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-serve API token without paid signup**: The API Proxy requires a Stacksync workspace service token, obtained only after creating a workspace and connecting an app in the UI. The agent could not generate this itself and the Starter plan ($1,000/mo) is the self-serve entry point, with no free API Proxy trial. This is a product/credential limitation, not an agent error — the agent correctly identified it and stopped rather than fabricating a token. Event 104: ```text I can't complete an authenticated run because I don't have a Stacksync workspace/service token, and minting one requires signing up (Starter is self-serve paid). ``` Event 104: ```text ❌ No free tier for the API Proxy. The free trial is on AI Agents, which doesn't include the proxy. ``` - **CLI quickstart requires a long-running local process**: The only documented developer workflow beyond the API Proxy is the Stacksync CLI, whose quickstart requires `stacksync login` (browser or API-key auth) and `stacksync workflow-connector run`, a long-running local process. Per the session's explicit instruction to avoid long-running commands, the agent correctly declined to pursue this path rather than treating it as a dead end caused by error. Event 62: ````text Start the connector locally: ```bash stacksync workflow-connector run ``` ```` Event 104: ```text The **CLI quickstart requires a long-running local process** (`stacksync workflow-connector run`) plus `stacksync login`. Per your instruction, I did not go down that path. ``` #### Suggested Changes - **Publish an API Proxy sandbox or free-tier token for first-time evaluation**: On the pricing page and API Proxy quickstart (docs.stacksync.com/api-proxy), offer a free or trial service token so developers can make one authenticated call before paying for Starter. Verify by confirming a request with the trial token against the hosted proxy returns a 200 instead of the current 401 for unauthenticated users. Event 104: ```text ❌ No free tier for the API Proxy. The free trial is on AI Agents, which doesn't include the proxy. ``` Event 61: ```text HTTP 401 {"msg":"Incorrect token: token is absent, malformed, incorrect, expired, suspended or inexistent."} ``` - **Publish an official SDK or OpenAPI spec for the API Proxy**: Add a published Python/JS package (PyPI/npm) or an OpenAPI/Swagger reference for the API Proxy and Management API, linked from docs.stacksync.com/developers. Verify by searching PyPI/npm for an official 'stacksync' package and confirming it returns Stacksync's own library rather than unrelated third-party packages. Event 54: ```text stacksync | 1.0.2 | Sync to async utility library ``` Event 104: ```text ⚠️ **No public SDK.** The npm `stacksync` package is an unrelated sync utility; there's no official PyPI package. ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/15d8f9e9-f512-47ed-84cf-b1126465ff99) · [Read transcript](https://www.ax-check.com/stacksync.com/sessions/kimi.json) Quoted plan prices ($1K/$3K/$4.2K per month, billed annually) with assumptions: syncs, records in sync, annual vs monthly billing, per-1K usage tiers. Sourced from the scraped pricing page. (seq 51, seq 56, seq 58) #### End-to-end onboarding - **Onboarding needs a login**: Agent never obtained a Stacksync account or API/service token. It confirmed via docs that every credential (workspace API key, API proxy service token) is minted inside the authenticated dashboard at app.stacksync.com, which requires human signup and third-party OAuth connections (e.g. Salesforce, HubSpot). No authenticated call to any Stacksync endpoint was ever made; the session stopped at the research stage and explicitly reported the blocker instead of attempting a workaround. Event 58: ```text Every credential is minted inside an authenticated dashboard** — API keys and service tokens are generated in workspace settings at `app.stacksync.com`, which requires signing up (email + verification). ``` Event 58: ```text No sandbox, trial API key, or anonymous endpoint** exists to develop against. ``` Event 58: ```text If you can create a workspace, connect two apps, and hand me a service token (and tell me the region endpoint), I can immediately build and run a real example ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **Dashboard-only credential issuance blocks self-service API access**: Stacksync's REST API proxy and workspace Management API both require a Bearer token, but that token can only be generated from the authenticated web dashboard after signup and OAuth-connecting third-party apps (Salesforce, HubSpot, etc.). This is expected product behavior (auth gating), not an agent error or test-environment issue, but it fully prevented any authenticated API call in this session. Event 58: ```text API keys and service tokens are generated in workspace settings at `app.stacksync.com`, which requires signing up (email + verification). ``` Event 58: ```text I have no Salesforce/HubSpot credentials to authorize, and Stacksync's whole value is syncing *between two connected systems*, so there's nothing meaningful to call without them. ``` - **No official SDK package found on npm**: Agent searched the npm registry for a Stacksync SDK and found only unrelated packages with similar names, confirming there is no official client library to install and use directly. Event 23: ```text stacksync - Sync to async utility library @iron-stack/sync - Declarative real-time data sync engine ``` Event 58: ```text No public SDK** — npm has no official `stacksync` package (only unrelated name collisions). ``` #### Suggested Changes - **Offer a sandbox or trial API token that does not require full dashboard signup plus third-party OAuth**: The quickstart and API proxy docs (docs.stacksync.com/start-here/quick-start, llms-full.txt) require creating a workspace and connecting a real third-party app (Salesforce, HubSpot, Supabase) before any token exists. Adding a disposable sandbox token or demo connector that issues a usable Bearer token without a live third-party OAuth grant would let developers exercise the API proxy end to end. Verify by having a fresh, unauthenticated user obtain a working token and successfully call the proxy within minutes. Event 58: ```text No sandbox, trial API key, or anonymous endpoint** exists to develop against. ``` - **Publish an official SDK package on npm**: A registry search for "stacksync" returned no official package, only unrelated libraries (stacksync, @iron-stack/sync). Publishing a scoped package (e.g. @stacksync/sdk) and linking it from the Quick Start and API proxy docs would let developers npm install it directly. Verify by searching npm registry for the official package name and confirming it resolves to Stacksync's own repo. Event 23: ```text stacksync - Sync to async utility library @iron-stack/sync - Declarative real-time data sync engine ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/082840c7-c271-47b9-b700-e154f9862d8e) · [Read transcript](https://www.ax-check.com/stacksync.com/sessions/qwen.json) Quoted per-plan prices from the fetched pricing page and named the assumptions behind them: annual vs month-to-month billing, record limits, sync counts, and which features each plan includes. (seq 42, seq 52) #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained Stacksync credentials or performed any authenticated operation. It found no public SDK/API package, no public API reference, and determined the documented quickstart is entirely UI-driven, requiring sign-up at app.stacksync.com and browser OAuth into real third-party apps (Salesforce, HubSpot, etc.), which it had no way to do without a human-provided account. It explicitly asked the user to supply a Stacksync account with Pro access before it could proceed. Event 52: ```text The quickstart is entirely UI-driven and requires live third-party accounts. Per docs.stacksync.com/start-here/quick-start: sign up at app.stacksync.com → connect real apps (e.g., Salesforce, HubSpot) via browser OAuth → map tables and fields in the dashboard → toggle sync on. I can't do browser OAuth into your CRM/ERP, and I have no Stacksync credentials. ``` Event 52: ```text If you can provide a Stacksync account with Pro access (Management API key) or want me to write a speculative scaffold against the undocumented API, say so — otherwise this is where I stop. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No public SDK or package for Stacksync**: Product behavior/naming collision: the agent searched npm and PyPI for a 'stacksync' package. The npm result was an unrelated utility library (sync-to-async), and PyPI had no matching package at all. This means there is no lightweight SDK a developer can pip/npm install to start building against Stacksync. Event 6: ```text stacksync@1.0.2 | ISC | deps: 1 | versions: 3 Sync to async utility library ``` Event 6: ```text ERROR: No matching distribution found for stacksync ``` - **Developer API is undocumented and paywalled**: Product behavior: the agent found no public API reference, OpenAPI spec, or docs subdomain for programmatic access. The 'Management API' is only mentioned in marketing/docs prose and is gated behind the Pro plan ($3,000/mo), with 404s on every guessed documentation path, so there is no way for a first-time developer to self-serve into the API even if they wanted to pay. Event 50: ```text == https://docs.stacksync.com/api-reference == 404 == https://docs.stacksync.com/api == 404 == https://api.stacksync.com == 404 ``` Event 26: ```text == docs == 404 == pricing == 200 == developers == 404 == api == 404 ``` - **Quickstart requires UI sign-up and live third-party OAuth**: Test-environment limitation (not a product defect): the documented quick-start flow requires creating a sync through the web dashboard and connecting real CRM/ERP accounts via browser OAuth. This falls outside what a non-interactive coding agent can do without human-supplied credentials, so the agent correctly stopped rather than faking a result. Event 52: ```text sign up at app.stacksync.com → connect real apps (e.g., Salesforce, HubSpot) via browser OAuth → map tables and fields in the dashboard → toggle sync on. I can't do browser OAuth into your CRM/ERP, and I have no Stacksync credentials. ``` #### Suggested Changes - **Publish a public API reference for the Management API**: The docs site and llms.txt mention a 'Management API' and 'config as code' as Pro-plan features but provide no reference documentation, OpenAPI spec, or endpoint list at docs.stacksync.com or api.stacksync.com (all returned 404). Add a public API reference page (even if actions require a paid key) so prospective developers can evaluate the integration shape before buying. Verify by confirming docs.stacksync.com/api-reference returns a real page instead of 404. Event 50: ```text == https://docs.stacksync.com/api-reference == 404 == https://docs.stacksync.com/api == 404 == https://api.stacksync.com == 404 ``` Event 49: ```text Pro and higher plans include the Management API and config as code for maintaining the configuration afterwards. ``` - **Add a lightweight, no-signup way to try the sync flow**: The Quick Start guide at docs.stacksync.com/start-here/quick-start requires signing up, then connecting live third-party apps through browser OAuth before any sync can be tested. Consider a sandbox/demo mode (e.g., with mock connectors or a CLI-based sync definition) so developers evaluating the product can exercise the core workflow without first authorizing production CRM/ERP accounts. Verify by having a fresh account complete a sync end-to-end without needing a real Salesforce/HubSpot/NetSuite login. Event 52: ```text sign up at app.stacksync.com → connect real apps (e.g., Salesforce, HubSpot) via browser OAuth → map tables and fields in the dashboard → toggle sync on. ``` ### Task given to each agent Help me build a simple example using Stacksync. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: B · 76/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html for a Markdown Accept header; no Markdown representation served. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt links docs, connectors, use cases, pricing and EDI with organized sections and summaries. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt explains .md URL convention, index.md for home, and points to llms-full.txt. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt mentions AI agents (Genies), MCP-vs-synced-database article, and EDI surfaces. ``` - **Pass** — A compact guide representation exists ```text llms.txt links .md versions of key pages, e.g. two-way-sync.md and pricing.md. ``` - **Pass** — A focused guide is directly retrievable ```text llms.txt is directly retrievable and links markdown versions of each key page. ``` - **Pass** — Equivalent instructions fit a token budget ```text llms.txt is a compact index well under the token budget, with organized sections. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats cannot be measured. ``` - **Pass** — The compact guide is independently actionable ```text llms.txt provides a structured, actionable index of docs, connectors, Genies, EDI and pricing. ``` - **Pass** — Install and next-step links resolve ```text Homepage links to docs, pricing and app; app.stacksync.com and docs resolve with HTTP 200. ``` ### Onboarding - **Skipped** — Docs lead to a relevant quickstart ```text llms.txt links many guides but no fetched page is a concrete quickstart with first steps. ``` - **Skipped** — Installation commands are extractable ```text No fetched page shows installation commands; llms.txt lists only conceptual guides and use cases. ``` - **Skipped** — Code examples are available without interaction ```text No fetched page contains code examples; llms.txt entries are prose summaries only. ``` - **Skipped** — Prerequisites and auth boundaries are explicit ```text llms.txt notes connector prerequisites generally but no fetched page states auth boundaries or API keys. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders full plan tables, usage rates and FAQs as static text without interaction. ``` - **Pass** — Prices are stated, not gated ```text Starter $1,000/mo, Pro $3,000/mo, Managed Pro $4,200/mo, AI Agents $200/mo all stated publicly. ``` - **Pass** — Pricing units and limits are explicit ```text Records in sync, active syncs, workflow executions and per-1,000 usage tiers are explicit. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Quoted list prices from the pricing page and named the assumptions: annual billing, sync and record allowances per tier, per-1K overage tiers, and API Proxy calls per day. (seq 14, seq 68, seq 104) Kimi K3: Quoted plan prices ($1K/$3K/$4.2K per month, billed annually) with assumptions: syncs, records in sync, annual vs monthly billing, per-1K usage tiers. Sourced from the scraped pricing page. (seq 51, seq 56, seq 58) Qwen 3.8 Max: Quoted per-plan prices from the fetched pricing page and named the assumptions behind them: annual vs month-to-month billing, record limits, sync counts, and which features each plan includes. (seq 42, seq 52) This behavioural item does not affect the fast grade. ``` ### Activation - **Skipped** — An API reference or OpenAPI spec is reachable ```text No API reference or OpenAPI spec was fetched; llms.txt lists only product, connector and EDI pages. ``` - **Skipped** — An MCP server is documented and well-formed ```text llms.txt mentions MCP only in a blog comparison title; no MCP server documentation was fetched. ``` - **Skipped** — A CLI install path is documented ```text No CLI install guide was fetched; llms.txt references Enterprise OS one-command deploy but no install path. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK or package registry lookup was supplied for any Stacksync developer package. ``` - **Skipped** — Agent skills are published ```text No agent skills documentation was fetched; llms.txt describes Genies AI agents, not published skills. ``` [Full report data](https://www.ax-check.com/stacksync.com/report.json)