# AX Check: cura.inc Checked 2026-10-23. Agents confuse Cura the startup with Cura the free 3D-print slicer All three sessions misidentified pricing, citing the unrelated open-source UltiMaker Cura slicer or fee-based crypto docs instead of the stated $200/month plan. ## End-to-end onboarding not demonstrated ## Coding sessions All three independent sessions completed but misread pricing: one attributed free pricing to the UltiMaker Cura slicer, another cited swap-fee pricing from unrelated docs with no SaaS tier found, and the third assumed the product was the open-source slicer and couldn't verify cloud pricing. None surfaced the homepage's stated $200/month Emerging Manager plan or the custom tier. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/1c453626-709a-4beb-84c2-d8b98aeb7b65) · [Read transcript](https://www.ax-check.com/cura.inc/sessions/deepseek.json) Says the free price applies to UltiMaker Cura, the open-source desktop slicer, backed by search results. It names the separate paid cloud subscription and says the other Cura products use service pricing. (seq 41, seq 59) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No credentials were obtained and no authenticated product operation occurred. The agent only ran local shell discovery and web/DNS lookups (curl against public sites, npm/PyPI registry searches) to identify what 'Cura' even refers to, then concluded no hosted developer API exists and stopped before attempting any sign-up or API call. Event 16: ```text curl -sS -m 15 -A 'Mozilla/5.0' "https://html.duckduckgo.com/html/?q=$(python3 -c "import urllib.parse,sys;print(urllib.parse.quote(sys.argv[1]))" "$q")" ``` Event 59: ```text This product has no developer workflow I can act on, so I'm stopping rather than inventing one. ``` #### Hallucinated URLs - **Guessed docs/dev subdomain that doesn't resolve**: The agent guessed a documentation subdomain (docs.cura.com) and a dev TLD variant (cura.dev) without any prior evidence they existed, and both failed to resolve at the DNS level (not merely a 404), indicating pure guesswork rather than a broken documented link. Event 42: ```text https://cura.dev curl: (6) Could not resolve host: cura.dev 000 https://cura.co 200 https://cura.health 200 https://docs.cura.com curl: (6) Could not resolve host: docs.cura.com ``` #### Blockers - **No hosted 'Cura' developer API or SDK exists**: Product behavior/ambiguity, not agent error or missing credentials: extensive web, npm, and PyPI searches across multiple candidate 'Cura' products (UltiMaker Cura slicer, Cura TeleHealth, Cura career platform, Apex Cura healthcare AI, Cura Solana SDK) turned up only a free open-source desktop slicer with a local CLI, or unrelated services with no published developer API, keys, or usage-based pricing. The agent correctly stopped per the seed prompt's instruction not to start local service stacks. Event 59: ```text There is **no hosted SDK or API** I can act on ``` Event 59: ```text UltiMaker Cura is a GUI desktop app plus a local `CuraEngine` CLI. Using it means downloading/installing/building a local toolchain, not a hosted API. ``` Event 59: ```text Building an example would require downloading/running the local slicer stack, which you explicitly told me not to do, and there's no hosted SDK/API to call instead. ``` #### Suggested Changes None identified in this transcript. ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/e7fd64a1-0da4-43f2-9643-b7d4a73c1acd) · [Read transcript](https://www.ax-check.com/cura.inc/sessions/kimi.json) Gave fee-based pricing from the docs: Cura takes 5% of swap fees on 1%-tier Uniswap pools and 2% of token distributions. It noted there is no SaaS tier and that basic use appears free. (seq 65, seq 67) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent never attempted authentication or any API call requiring credentials. It concluded no developer-facing API/SDK exists (only a stub CLI package and end-user web dashboard requiring Farcaster login), and stopped per the seed prompt's instruction to halt if there's no developer workflow to act on. No credential acquisition or authenticated operation was attempted or demonstrated. Event 67: ```text There is no public API, SDK, API key, or developer quickstart ``` Event 67: ```text Every workflow requires being a **Farcaster channel moderator** who signs into the web app with a Farcaster account and adds `@curabot` as a channel mod via Warpcast. That's an interactive, human-account-based flow — nothing I can drive programmatically, and I don't hold a Farcaster account. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No programmatic API/SDK exists for Cura**: Product behavior/limitation, not agent error: the agent inspected the only published package (PyPI 'cura' 0.0.2), finding it contains a single no-op CLI command, and found the linked GitHub source repo returns 404. All real functionality is gated behind a web dashboard requiring a human Farcaster account login, so there was no hosted API or SDK surface for the agent to build an example against. Event 61: ```text async def version(): """Print the version.""" from .. import __version__ print(f'cura {__version__}') ``` Event 27: ```text 404: Not Found ``` Event 67: ```text its CLI contains literally one command (`version`). No functionality. ``` - **Core workflows require human Farcaster identity and Warpcast wallet actions**: Product design constraint: setting up Cura and all its channel-management, reward, and token features require signing into the web dashboard with a human Farcaster account and connecting a Warpcast-verified wallet — steps that cannot be completed by an unattended agent in this session. Event 53: ```text Step 2: Sign in using your Farcaster account ``` Event 54: ```text Step 3: Connect your Warpcast verified wallet to the frame. ``` #### Suggested Changes - **Publish a developer API/SDK reference or state there isn't one**: The docs site (cura-docs.openrank.com) currently has only end-user guides (Overview, Features, Setting up Cura, channel/reward/token pages) and a placeholder PyPI package with a single 'version' CLI command. If a developer-facing API is planned, add a dedicated API/SDK section to the docs; if none exists, state that plainly in the docs or package README so developers don't need to reverse-engineer this via the PyPI package and GitHub repo as this session did. Event 44: ```text - [Overview](https://cura-docs.openrank.com/overview.md) - [Features](https://cura-docs.openrank.com/features.md) - [Setting up Cura](https://cura-docs.openrank.com/setting-up-cura.md) ``` Event 61: ```text async def version(): """Print the version.""" from .. import __version__ print(f'cura {__version__}') ``` - **Fix or remove the dead GitHub source link**: The PyPI package metadata lists 'source': 'https://github.com/Karma3Labs/cura.git' and the repo's README was fetched via raw.githubusercontent.com, both returning 404. Either make the repository public or update the PyPI project_urls metadata to remove the broken reference, and verify by re-fetching the URL after the fix. Event 27: ```text 404: Not Found ``` Event 17: ```text {'documentation': 'https://cura-docs.openrank.com', 'homepage': 'https://cura.openrank.com', 'issues': 'https://github.com/Karma3Labs/issues', 'source': 'https://github.com/Karma3Labs/cura.git'} ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/747c5970-7bf8-4114-9608-c9c778d96576) · [Read transcript](https://www.ax-check.com/cura.inc/sessions/qwen.json) Stated Cura is free/open source (AGPL), explicitly assuming the product is Ultimaker Cura and noting cloud-service pricing could not be verified. (seq 20) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent never located a product called Cura with a hosted SDK or API. It searched the local repo (empty) and public package registries (npm, PyPI), found only unrelated placeholder packages, and concluded the only known 'Cura' is the Ultimaker 3D printing slicer, a desktop app with no public API. No credentials were obtained or used, and no authenticated operation was attempted. Event 20: ```text Cura is a desktop application. There is no hosted SDK or public API I can call from here. ``` Event 20: ```text This product has no developer workflow I can act on under your constraints — no hosted SDK, no public API, and no way to build a meaningful example without running local software. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No identifiable hosted Cura product with an API/SDK**: The agent could not find any product named Cura with a developer-facing hosted API or SDK. The local workspace was empty, and registry searches (npm, PyPI) only turned up unrelated stub packages. The only known match, Ultimaker Cura, is a desktop slicer app with no public API, which conflicts with the session's hosted-only constraint. This is an agent/environment ambiguity issue (ambiguous or missing product identity) rather than a demonstrated defect in a real product, since no actual 'Cura' product with a developer workflow was ever located. Event 10: ```text total 16 drwxr-xr-x 3 root root 4096 Sep 18 08:00 . drwxr-xr-x 8 root root 4096 Sep 24 20:05 .git -rw-r--r-- 1 root root 408 Sep 18 08:00 .gitignore ``` Event 18: ```text {"name":"cura","keywords":[],"version":"0.0.3","description":"cura" ``` Event 20: ```text The workspace (`/sandbox/repo`) is empty — just an initial commit with a `.gitignore`. No Cura docs, SDK, config, or credentials anywhere. ``` #### Suggested Changes None identified in this transcript. ### Task given to each agent Help me build a simple example using Cura. 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 · 80/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 text/markdown request; no Markdown representation offered. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt links About, Developers, API docs, sitemap, and MCP manifest with clear starting guidance. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt organizes Docs, MCP, and Contact sections with descriptive link labels and a when-to-use guide. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt mentions the REST API docs and the MCP manifest with server URL, transport, and OAuth auth. ``` - **Pass** — A compact guide representation exists ```text docs.cura.inc/introduction.md returns text/markdown, a standalone Markdown guide representation. ``` - **Pass** — A focused guide is directly retrievable ```text Introduction.md is directly retrievable at docs.cura.inc/introduction.md with base URL and auth. ``` - **Pass** — Equivalent instructions fit a token budget ```text Introduction.md is 504 tokens, well under the 8000-token budget. ``` - **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 gives a compact, actionable guide: when to use Cura, docs, MCP manifest, and contact. ``` - **Pass** — Install and next-step links resolve ```text Homepage links to docs.cura.inc, /developers, and /llms.txt, all of which fetched successfully. ``` ### Onboarding - **Skipped** — Docs lead to a relevant quickstart ```text llms.txt links a Developers overview and API docs, but no quickstart page was fetched. ``` - **Skipped** — Installation commands are extractable ```text No installation or CLI guide was fetched; llms.txt only lists docs and MCP manifest. ``` - **Skipped** — Code examples are available without interaction ```text No API reference or code example page was fetched; only llms.txt index available. ``` - **Skipped** — Prerequisites and auth boundaries are explicit ```text llms.txt notes workspace-scoped auth and OAuth MCP, but no auth setup page fetched. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing section renders on homepage with plan names, prices and limits visible without interaction. ``` - **Pass** — Prices are stated, not gated ```text Emerging Manager $200/month stated; Custom notes 90% pay $5,000–$15,000/year. ``` - **Pass** — Pricing units and limits are explicit ```text Units explicit: $200/month, 3 seats max, 20 portfolio companies; Custom unlimited seats/companies. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Says the free price applies to UltiMaker Cura, the open-source desktop slicer, backed by search results. It names the separate paid cloud subscription and says the other Cura products use service pricing. (seq 41, seq 59) Kimi K3: Gave fee-based pricing from the docs: Cura takes 5% of swap fees on 1%-tier Uniswap pools and 2% of token distributions. It noted there is no SaaS tier and that basic use appears free. (seq 65, seq 67) Qwen 3.8 Max: Stated Cura is free/open source (AGPL), explicitly assuming the product is Ultimaker Cura and noting cloud-service pricing could not be verified. (seq 20) This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text API reference page embeds a full OpenAPI 3.1 spec for the Cura API. ``` - **Pass** — An MCP server is documented and well-formed ```text MCP manifest gives server URL, streamable-http transport, and OAuth endpoints. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented in the fetched Cura developer pages. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK or package registry lookup supplied for Cura developer packages. ``` - **Skipped** — Agent skills are published ```text No agent skills published or referenced in the fetched Cura pages. ``` [Full report data](https://www.ax-check.com/cura.inc/report.json)