Skip to content
Gauge

ax-check.com

by Gauge

Strapi

strapi.io

ax-check.com

Checked 2 October 2026

B

65/100

Agents haven’t verified setup

Strapi's quickstart and docs work, but agents guess at pricing

Docs deliver a 12-step quickstart with working install commands and open pricing, but no documentation index exists, so agents recall pricing from memory instead of the live page.

3 fixes to start with

Concrete changes, backed by what we found.

Onboarding

Resolve the blocker that stopped agent setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Docs

Return Markdown when clients request text/markdown.

Homepage returned text/html for a text/markdown request; no Markdown representation offered.

Docs

Add links to your product documentation and quickstart in /llms.txt.

https://strapi.io/llms.txt returns HTTP 404, so no documentation index exists.

Recorded coding sessions

Same task, 3 models, no strapi.io account. Recorded 2 October 2026 on Pi.

3 recorded · 39s

39s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
Help me build a simple example using Strapi. 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.
Thinking…

The user wants help building a simple example using Strapi. Strapi is an open-source headless CMS. The user wants to know about the pricing model and also wants to know whether this product is easy to manage. They also say "use the hosted product via SDK or API" and "don't start a local service stack."

Key question: does Strapi have a hosted product with an API that can be used without a local stack? Strapi has Strapi Cloud. However, using Strapi Cloud requires an account/API token. There's probably no credential in the sandbox environment. The typical Strapi quickstart is to run npx create-strapi-app locally—that's exactly a local service stack, which the user has prohibited.

Let me first check the sandbox environment. Let me look at the current directory and check whether there are any credentials/environment variables.

The honest answer is probably as follows: Strapi's standard quickstart requires running a local Node server (create-strapi-app), which falls under what the user has prohibited. Strapi Cloud is a hosted option, but it requires signing up, and I can't do that without credentials. Let me check the environment for API keys.

$ ls -la /sandbox/repo 2>/dev/null; echo "---"; env | grep -i -E "strapi|api_key|token" | head -20{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Oct 2 15:23 ..\ndrwxr-xr-x 8 root root 4096 Sep 24 20:05…ctrl+o
{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Oct  2 15:23 ..\ndrwxr-xr-x 8 root root 4096 Sep 24 20:05 .git\n-rw-r--r-- 1 root root  408 Sep 18 08:00 .gitignore\n---\nPI_GATEWAY_API_KEY=unused\n","type":"text"}]}
$ curl -s -m 10 -o /dev/null -w "%{http_code}" https://cloud.strapi.io 2>&1; echo; node --version 2>/dev/null; npm --version 2>/dev/null{"content":[{"text":"200\nv22.23.2\n10.9.8\n","type":"text"}]}
Thinking…

Environment: empty repository, no Strapi credentials, no API tokens. Strapi Cloud is reachable, but a Strapi Cloud account is required to create a project — signup requires email authentication, and I can't do that.

Strapi's standard quickstart: npx create-strapi-app@latest quickstart — this spins up a local Node.js dev server (long-running) — explicitly forbidden by the user ("don't start a local service stack or wait on long-running commands; if the quickstart requires either, say so plainly and stop").

Strapi Cloud (hosted version) has a REST API, but provisioning a project requires a web signup flow with email verification, or the Cloud API which requires an account token that I don't have. There's no anonymous/sandbox tier accessible without credentials.

So per instructions: "If there is no actionable developer workflow for this product, say so plainly and stop." The honest answer is:

  • Pricing: Strapi is open source (free, MIT). Strapi Cloud is hosted, with a free 14-day trial, then paid plans (Developer ~$22/mo… let me think carefully). Pricing as of my knowledge: Strapi Cloud plans — free 14-day trial; Developer plan ~$22/mo; Pro ~$99/mo (older pricing was Starter $99?). Actually: Strapi Cloud pricing is: free 14-day trial; Developer $22/mo; Pro $99/mo; custom/enterprise. I should present this roughly and note that it should be confirmed on strapi.io/pricing. I could try to fetch the pricing page.

  • Manageability: Strapi itself is an ordinary Node project — easy for an agent to manage as code. But the hosted Cloud provisioning requires an authenticated web flow I can't complete.

  • Blocked: can't act. The quickstart requires a long-running local server (forbidden), and the hosted version requires account credentials I don't have. Per instructions, say so plainly and stop.

Let me quickly check pricing from the web so I can give accurate pricing info. That's a short curl and doesn't count as a long-running command.

$ curl -s -m 15 https://strapi.io/pricing | grep -o -i -E '(\$[0-9]+|free|trial|per month|/month|Developer|Pro|Enterprise|Basic|Business)' | sort | uniq -c | sort -rn | head -25{"content":[{"text":" 1 pro\n","type":"text"}]}
Thinking…

The pricing page is rendered with JS. Let me try their API or a cached source. There might be a sitemap or JSON. Not important — I'll state the pricing from known information, while clearly noting that it should be verified. Actually, should I quickly try one more approach? — the Strapi docs might have some mention of pricing, or use a different URL.

$ curl -s -m 15 "https://strapi.io/pricing" -H "User-Agent: Mozilla/5.0" | tr '>' '>\n' | grep -i -E '\$[0-9]|month|trial' | head -30{"content":[{"text":"(no output)","type":"text"}]}
Thinking…

Since the page is rendered with JS, I can't scrape it here. I'll convey pricing info from my own knowledge, and explicitly note that I couldn't verify it in real time.

Okay, decision time: Is there an executable developer workflow?

Strapi = a self-hosted open-source headless CMS. The official quickstart (npx create-strapi-app) starts a long-running local dev server → prohibited by the user's constraints.

Strapi Cloud = the hosted option, but:

  • Provisioning a project requires a web sign-up + email verification, or an authenticated Cloud API call using an account token. This sandbox has no credentials whatsoever (confirmed: only PI_GATEWAY_API_KEY=unused, an empty repo).
  • Without an account, there's no way to get an anonymous/demo Strapi endpoint that I could hit with the REST API.

Therefore, following the user's instructions, I should state it plainly and stop. What I should provide: pricing info, manageability assessment, the fact that I'm blocked. Keep it concise.

I checked the environment and Strapi's options before writing any code. Here's where things stand.

Blocked — stopping as instructed

Strapi has no developer workflow I can act on under your constraints:

  1. Self-hosted quickstart (the official path): npx create-strapi-app@latest boots a long-running local Node.js dev server. That's a local service stack + long-running command — both explicitly off-limits per your instructions.
  2. Strapi Cloud (the hosted product): It has a clean REST API (/api/:collection with bearer tokens) that would be ideal for a light SDK-style example — but there is no anonymous or credential-free way to provision a project. Sign-up requires an interactive web flow with email verification, and its management API requires an account token. I verified this sandbox has no Strapi credentials (env shows nothing, repo is empty), so I cannot create a hosted project or get an API token to demonstrate against.

There is no third option — Strapi has no public demo API endpoint, no free-tier-without-signup, and no CLI provisioning that works unauthenticated.

Pricing (from knowledge — the pricing page is JS-rendered, so I couldn't verify live)

  • Strapi itself: open source, MIT licensed, free (self-hosted; you pay only for your own infrastructure).
  • Strapi Cloud (hosted): ~14-day free trial, then roughly $22/mo (Developer), $99/mo (Pro), and custom Enterprise pricing. Verify at strapi.io/pricing before relying on these numbers.

Manageability (for me, as an agent)

  • As code: very manageable. It's a plain Node.js project — schema definitions, content types, and plugins are JSON/JS files I can read, edit, and version-control easily. Its REST/GraphQL APIs are simple and well-documented.
  • As a hosted service: manageable only if you hand me a Strapi Cloud project URL + API token. Then building a CRUD example (create content type → POST/GET entries via fetch) takes minutes with no local stack.

What would unblock this

If you create a free Strapi Cloud trial project yourself (or give me credentials/an existing project URL + API token), I can immediately build a working example against it via plain HTTP — no local server needed. Otherwise, per your instructions, I'm stopping here.

AX Fundamentals

23 checks. Open an area for details.

This check is a quick preview. Test more tasks and models with Gauge Agents.

Test your product with Gauge Agents

AX Check by Gauge