# AX Check: draftbit.com
Checked 2026-09-18.

Docs are agent-friendly, but pricing trips up some agents
Pricing is stated clearly on the page itself, yet 1 of 3 coding sessions couldn't pull exact figures and one guessed from memory instead.

## End-to-end onboarding not demonstrated

## Coding sessions
All three sessions completed. One correctly sourced the full pricing table with plan assumptions. Another gave rough guessed price ranges instead of the real figures. The third couldn't retrieve exact prices at all, only describing the credit system.

### DeepSeek V4 Pro
[View public run](https://agents.withgauge.com/p/runs/dd2914b0-e7c8-436d-a5c6-39deedbb3a90) · [Read transcript](https://www.ax-check.com/draftbit.com/sessions/deepseek.json)
Final output gives a full pricing table (Free/Standard/Pro/Team/Enterprise) sourced from JSON-LD on draftbit.com/pricing (seq 41-52) with explicit assumptions: monthly vs yearly billing, seat add-ons, sandbox/AI-credit limits, USD/Stripe billing.
#### End-to-end onboarding
- **End-to-end onboarding not demonstrated**: The agent never attempted to obtain or use product credentials. It only ran anonymous public requests (npm registry lookups, curl against draftbit.com/pricing and docs.draftbit.com) to research pricing and the docs sitemap. It concluded the hosted builder is browser-only behind Clerk login with no API/SDK/CLI surface to act on, and stopped without signing up, authenticating, or performing any authenticated operation.
  Event 34:

  ```text
  $0
  $12
  $8
  $24
  $16
  $120
  $16
  $5
  $10,000
  $100 and up
  $500 and up
  $1,000 and up
  $10,000 and up
  ```
  Event 95:

  ```text
  The hosted product (draftbit.com) is a browser-only visual builder behind Clerk login. Its docs sitemap (~250 pages) contains only UI/builder docs — no API reference, no SDK, no CLI.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No programmatic API, SDK, or CLI for the hosted builder**: Product behavior, not agent error: Draftbit's hosted app is a browser-only visual builder. npm registry confirmed draftbit and draftbit-cli packages don't exist; the only @draftbit npm packages are React Native UI component libraries, not a hosted-service client. The docs sitemap (~250 pages) has only component/UI/builder docs, no API reference, SDK, or CLI, leaving no way to create or manage a project without local Expo tooling or a human clicking the browser UI, both out of scope per task constraints.
  Event 14:

  ```text
  npm error 404
  npm error 404  '@draftbit/cli@*' is not in this registry.
  npm error 404
  npm error code E404
  npm error 404 Not Found - GET https://registry.npmjs.org/draftbit-cli - Not found
  ```
  Event 95:

  ```text
  No CLI. `@draftbit/cli` and `draftbit-cli` don't exist on npm.
  ```
  Event 95:

  ```text
  The only programmatic artifacts are the `@draftbit/ui`, `@draftbit/core`, `@draftbit/native` npm packages — React Native component libraries, not a hosted service.
  ```
- **GitHub export is a manual UI click, not an API call**: Product design limitation: the docs describe GitHub export as something a user triggers by clicking in the browser builder, not something invocable via API, preventing the agent from driving even the one code-artifact-producing feature programmatically.
  Event 83:

  ```text
  The GitHub Export integration commits your app's generated source code (React Native, Astro, Vite, or a backend variant, depending on your app) to a repository and branch you choose, whenever you trigger an export.
  ```

#### Suggested Changes
- **Publish an API or CLI reference page in the docs sitemap**: The docs sitemap at docs.draftbit.com/sitemap-0.xml lists roughly 250 pages covering UI components, publishing, and billing but no api, sdk, cli, or developer entry. Adding a documented API/CLI surface would let programmatic workflows self-serve instead of requiring the browser builder for every action; verify by confirming a new /docs/api or /docs/cli page appears in the sitemap with real endpoint or command documentation.
  Event 77:

  ```text
  https://docs.draftbit.com/docs/rest-api-integrations/
  https://docs.draftbit.com/docs/rest-api-services/
  https://docs.draftbit.com/docs/rest-services-endpoints/
  ```
  Event 95:

  ```text
  Its docs sitemap (~250 pages) contains only UI/builder docs — no API reference, no SDK, no CLI.
  ```

### Kimi K3
[View public run](https://agents.withgauge.com/p/runs/796db9cd-cff5-4a3c-bf1e-f64dbff94559) · [Read transcript](https://www.ax-check.com/draftbit.com/sessions/kimi.json)
Final output lists Free/Basic (~$19/mo)/Pro (~$59-79/mo)/Team tiers while explicitly flagging the assumption that figures are from prior knowledge since the live pricing page is JS-rendered and couldn't be scraped (seq 19-20).
#### End-to-end onboarding
- **End-to-end onboarding not demonstrated**: Agent never attempted authentication or credential acquisition. It only fetched public docs/pricing pages and an npm registry search, then concluded Draftbit has no programmatic API/SDK/CLI and stopped without signing up, obtaining an API key, or performing any authenticated operation.
  Event 20:

  ```text
  No public API or SDK** exists for creating/modifying apps, screens, or data programmatically.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **Draftbit has no programmatic API, SDK, or CLI**: Product behavior, not agent error or missing credentials: the agent inspected docs.draftbit.com and npm and found only a visual drag-and-drop builder with an npm UI component library (not an API/SDK for managing apps). This is an inherent product limitation for a coding-agent-driven workflow, confirmed by the agent's own research rather than a login wall or environment issue.
  Event 20:

  ```text
  Draftbit has no developer workflow I can act on.** It's a browser-based, drag-and-drop visual builder for React Native apps.
  ```
  Event 12:

  ```text
  github.com/draftbit
  github/
  
  ```
- **Pricing page is JavaScript-rendered, blocking scraping**: Test-environment/tooling limitation: curl-based scraping of draftbit.com/pricing returned no output because the page requires JS rendering, which the shell-only tool cannot execute. This forced the agent to rely on prior knowledge instead of live data.
  Event 18:

  ```text
  (no output)
  ```
  Event 20:

  ```text
  The pricing page is JS-rendered so I couldn't scrape it — I'll note that below.
  ```

#### Suggested Changes
- **Publish a machine-readable pricing page or API endpoint**: The current draftbit.com/pricing page renders via JavaScript, so simple HTTP fetches (curl) return empty content, as seen in the tool_result at seq 18. Adding a static HTML fallback or a JSON pricing endpoint would let automated tools and agents retrieve accurate current pricing without guessing. Verify by running a plain curl against the page and confirming tier names and prices appear in the raw HTML.
  Event 18:

  ```text
  (no output)
  ```
- **Document any existing programmatic surface prominently in docs.draftbit.com**: The agent's scan of docs.draftbit.com found only visual-builder, publishing, and GitHub-integration content, with no mention of an API, SDK, or CLI for managing apps or screens. If any headless/programmatic capability exists, add a clearly labeled 'API' or 'Developer' section to the docs site so it surfaces in a keyword scan; verify by re-running a grep for 'api' or 'sdk' against the docs homepage and confirming relevant links appear.
  Event 12:

  ```text
  click-publishing/android-publishing/
  click-publishing/ios-publishing/
  click-publishing/web-publishing/
  ```

### Qwen 3.8 Max
[View public run](https://agents.withgauge.com/p/runs/d585073d-eb2a-4dbc-bfb7-a295a8ac861d) · [Read transcript](https://www.ax-check.com/draftbit.com/sessions/qwen.json)
Agent never states an actual cost figure — it explicitly says 'Exact dollar figures are on their JS-rendered pricing page, which I couldn't scrape' (seq 39), so no price is given, only the credit mechanism, failing the 'stated what the product would cost' requirement.
#### End-to-end onboarding
- **End-to-end onboarding not demonstrated**: The agent never attempted to obtain Draftbit credentials or sign up for an account. It only crawled public docs/marketing pages via curl and checked npm registry listings. No login, API key, or authenticated request against draftbit.com was made, and no product resource was created.
  Event 39:

  ```text
  So I can't build the "simple example" for you. To do it yourself: sign up at draftbit.com ("Try Draftbit Free"), create a new app, and describe it via their AI prompt builder.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No public SDK/API/CLI to drive Draftbit programmatically**: Draftbit's core app-building workflow is only accessible through its browser-based visual editor. The agent checked npm for a CLI package and searched docs for API/SDK references, finding only React Native UI component libraries (for use inside exported code) and a 'REST API' doc that covers calling third-party APIs from within a Draftbit app, not controlling Draftbit itself. This is a product characteristic, not an agent error or missing credential — there is no lightweight SDK/API path for this session type to use.
  Event 15:

  ```text
  npm error code E404
  npm error 404 Not Found - GET https://registry.npmjs.org/draftbit-cli - Not found
  ```
  Event 39:

  ```text
  There is:
  
  - **No public SDK, REST API, or CLI** for creating or manipulating apps programmatically.
  ```
  Event 39:

  ```text
  The entire workflow — creating an app, writing AI prompts/tasks, editing, publishing — happens inside their hosted web editor, which requires an interactive browser session and login. I can't drive that from here.
  ```

#### Suggested Changes
- **Clarify scope of the REST API docs pages**: On docs.draftbit.com's rest-api-integrations and rest-api-services pages (found via the sitemap), add a lead sentence clarifying these describe integrating third-party APIs into a Draftbit app, not a way to programmatically create or manage Draftbit apps themselves. The agent had to fetch and parse full page content to determine this scope was not about controlling the platform headlessly. Verify by confirming the first visible line on those pages states the intended use case.
  Event 32:

  ```text
  https://docs.draftbit.com/docs/rest-api-integrations/
  https://docs.draftbit.com/docs/rest-api-services/
  ```
  Event 39:

  ```text
  the docs' "REST API" pages are about calling *third-party* APIs from inside your app — not an API for controlling Draftbit itself.
  ```

### Task given to each agent
Help me build a simple example using Draftbit. 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: A · 100/100 (provisional)
Grades come from completed site checks. Coding sessions and skipped checks do not affect the score.

### Clarity
- **Pass** — Homepage answers Markdown requests

  ```text
  Homepage returned text/markdown with content negotiation, confirming Markdown support.
  ```

- **Pass** — llms.txt provides an actionable documentation index

  ```text
  llms.txt links docs, product, templates, blog, changelog, and full content sections.
  ```

- **Pass** — llms.txt provides navigation guidance

  ```text
  llms.txt organizes links into labeled sections with descriptions for navigation.
  ```

- **Pass** — llms.txt mentions offered API, MCP, and skills

  ```text
  llms.txt references docs and MCP pages; MCP servers documented on site.
  ```

- **Pass** — A compact guide representation exists

  ```text
  llms.txt index and llms-product.txt provide compact Markdown representations of Draftbit content.
  ```

- **Pass** — A focused guide is directly retrievable

  ```text
  llms-product.txt and docs Getting Started are directly retrievable focused guides.
  ```

- **Pass** — Equivalent instructions fit a token budget

  ```text
  llms-product.txt is 17,488 tokens but llms.txt is 266; compact guide fits budget.
  ```

- **Pass** — Product-docs links survive format changes

  ```text
  Homepage Markdown supported; docs link to docs.draftbit.com survives in both representations.
  ```

- **Pass** — The compact guide is independently actionable

  ```text
  Getting Started guide gives concrete prep steps and next steps for building a first app.
  ```

- **Pass** — Install and next-step links resolve

  ```text
  Fetched install/next-step links (signup, docs, creating-a-new-app) returned 200.
  ```


### Onboarding
- **Pass** — Docs lead to a relevant quickstart

  ```text
  Docs Getting Started links to creating-a-new-app and next.draftbit.com to start building.
  ```

- **Skipped** — Installation commands are extractable

  ```text
  Draftbit is a browser-based builder; no install commands for a local package are offered.
  ```

- **Pass** — Code examples are available without interaction

  ```text
  Getting Started shows inline code and Nativewind class examples without interaction.
  ```

- **Pass** — Prerequisites and auth boundaries are explicit

  ```text
  Docs state Apple $99/yr and Google Play $25 accounts needed; auth via connected backend.
  ```


### Pricing
- **Failed** — Agents identify pricing and its assumptions

  ```text
  3 of 3 sessions were judged on pricing; 1 fell short. DeepSeek V4 Pro: Final output gives a full pricing table (Free/Standard/Pro/Team/Enterprise) sourced from JSON-LD on draftbit.com/pricing (seq 41-52) with explicit assumptions: monthly vs yearly billing, seat add-ons, sandbox/AI-credit limits, USD/Stripe billing. Kimi K3: Final output lists Free/Basic (~$19/mo)/Pro (~$59-79/mo)/Team tiers while explicitly flagging the assumption that figures are from prior knowledge since the live pricing page is JS-rendered and couldn't be scraped (seq 19-20). Qwen 3.8 Max: Agent never states an actual cost figure — it explicitly says 'Exact dollar figures are on their JS-rendered pricing page, which I couldn't scrape' (seq 39), so no price is given, only the credit mechanism, failing the 'stated what the product would cost' requirement. This behavioural item does not affect the fast grade.
  ```

- **Pass** — Pricing is readable without interaction

  ```text
  Pricing page renders plan cards and comparison table as static text, no interaction needed.
  ```

- **Pass** — Prices are stated, not gated

  ```text
  Prices stated: Free $0, Standard $12, Pro $24, Team $120 per month.
  ```

- **Pass** — Pricing units and limits are explicit

  ```text
  Units explicit: per month, seats, sandboxes, agents, credits, and volume bonuses listed.
  ```


### Activation
- **Skipped** — An API reference or OpenAPI spec is reachable

  ```text
  No Draftbit API reference or OpenAPI spec was fetched; docs describe importing third-party specs, not a Draftbit API.
  ```

- **Pass** — An MCP server is documented and well-formed

  ```text
  Draftbit documents MCP servers with config, auth, plan gating, and a 15-server catalog.
  ```

- **Skipped** — A CLI install path is documented

  ```text
  No Draftbit CLI install path was fetched; docs describe a cloud builder, not a packaged CLI.
  ```

- **Skipped** — SDK packages resolve on their registries

  ```text
  No Draftbit SDK or package registry lookup was supplied; only a GitHub org link appears.
  ```

- **Skipped** — Agent skills are published

  ```text
  No Draftbit agent skills were fetched or documented in the supplied evidence.
  ```



[Full report data](https://www.ax-check.com/draftbit.com/report.json)
