Skip to content
Gauge

ax-check.com

by Gauge

Mintlify

mintlify.com

ax-check.com

Checked 5 October 2026

A

100/100

Agents haven’t verified setup

Mintlify's docs, CLI, and pricing are all immediately usable by agents.

All 23 checked items passed: quickstart, CLI install, API/MCP docs, and pricing (Starter $0, Pro $450-540/mo, Enterprise contact sales) are stated plainly, no login walls.

1 fix 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.

Recorded coding sessions

Same task, 3 models, no mintlify.com account. Recorded 5 October 2026 on Pi.

3 recorded · 35s

35s · 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 Mintlify. 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…

I need to look into this further. Let me check the details.

The user wants to create a simple Mintlify documentation example. Mintlify is a documentation platform, and creating a docs project is just Markdown/MDX files, typically using their CLI or GitHub sync. There's no API for creating content from the CLI locally... Actually, Mintlify has a CLI (mintlify dev), which spins up a long-running local server—the user told me not to start a local service stack or wait for long-running commands.

So the question is: does Mintlify have a hosted API for managing content? Mintlify is content-managed via Git (GitHub repository sync). There's no public REST API for creating documentation pages. In other words, Mintlify doesn't have a developer workflow of "using the hosted product via SDK or API" for content—content is managed through a Git repo that the user syncs, and publishing requires connecting to GitHub, authentication, etc.

Wait—can't I just scaffold a project locally (writing MDX files, mint.json)? That's just file creation, which isn't the same as using the hosted product via SDK/API. The instructions say: "Stay lightweight: use the hosted product via SDK or API. Do not start a local service stack or wait for long-running commands. If either is needed for the quickstart, say so plainly and stop." And "if this product doesn't have a developer workflow you can act on, say so plainly and stop."

Mintlify's workflow: mintlify dev (long-running local server—prohibited), and publishing via Git sync to their hosted platform (requires the user's GitHub connection/authentication, no public API/SDK). So following the instructions, I should say so plainly and stop.

But should I double-check? Maybe I can check whether the mintlify CLI is installed. Let me do a quick check to give an accurate answer. I can also mention pricing (public info): Mintlify has a free tier (hobby), pro around $150/month (previously $120?), growth, enterprise. Pricing: Free (hobby), Pro $150/month, Growth $550/month (approximate, subject to change). I should mention that pricing changes.

Let me do a quick check in the sandbox for the mintlify CLI or network availability, then give my answer and stop.

which mintlify; npm ls -g --depth=0 2>/dev/null | head -20; ls /sandbox/repo
/usr/local/lib
/usr/local/lib
├── @anthropic-ai/claude-code@2.1.280
├── @earendil-works/pi-coding-agent@0.84.2
├── @openai/codex@0.142.5
├── corepack@0.34.6
└── npm@10.9.8


curl -s -m 8 -o /dev/null -w "%{http_code}" https://api.mintlify.com 2>&1; echo; curl -s -m 8 -o /dev/null -w "%{http_code}" https://mintlify.com 2>&1
401
401
307
Thinking…

I need to look into this further. Let me confirm the details.

Mintlify CLI is not installed. api.mintlify.com returns 401 (auth required, no public self-service API for creating docs). Mintlify's developer workflow: you create MDX files locally, preview with mintlify dev (a long-running local server — prohibited), and publish via Git sync to GitHub (requires user account/GitHub connection). There is no SDK/API for programmatically creating and publishing docs pages.

Following the instructions, I should state that frankly and stop. But should I also answer questions about pricing? The user asked: "Tell me how pricing works, and briefly tell me whether this product is easy for you to operate. Let me know if you get blocked. If this product has no developer workflow you can operate on, state that frankly and stop."

Therefore: state frankly that there is no workflow operable via API/SDK, answer pricing concisely from public knowledge, comment on ease of operation, and stop. No need to scaffold files. Because the workflow isn't executable (scaffolding MDX locally would be meaningless unless we run the prohibited dev server or the user connects GitHub).

Just to be safe, should I check Mintlify's docs to confirm the publishing workflow? I'm fairly confident: Mintlify = docs-as-code, Git-based, mintlify dev for local preview, deployment via GitHub integration. No public content API. That's enough. Stop.

Stopping here, plainly: Mintlify has no developer workflow I can act on under your constraints.

Here's why:

  • Mintlify is docs-as-code. Content is MDX files + a docs.json config in a Git repo. There is no public SDK or REST API for creating/publishing documentation pages programmatically — api.mintlify.com exists but requires an authenticated account connection, and its purpose is account/dashboard operations, not self-serve content publishing.
  • The quickstart requires both things you ruled out:
    1. Local preview via mintlify dev — a long-running local server (prohibited, and the CLI isn't even installed here).
    2. Publishing via Git sync — connecting a GitHub repo to your Mintlify account through their dashboard, which requires your credentials/OAuth, not something an API token from me can do headlessly.

Scaffolding MDX files locally would be inert: nothing I could run to validate or publish it without either the dev server or your GitHub connection. So per your instruction, I'm saying so plainly and stopping rather than producing dead files.

How pricing works (public info, subject to change — verify at mintlify.com/pricing):

  • Free/Hobby tier — one project, hosted subdomain, basic features; fine for a simple example.
  • Pro (~$150/mo) — custom domain, more editors, analytics, API playground, etc.
  • Growth/Enterprise (custom, several hundred $/mo and up) — SSO, advanced permissions, translation, support SLAs.
  • Billing is per-organization/month, seat-oriented on higher tiers; no usage-based metering.

Would it be easy for me to manage? Partially. Writing and editing the MDX/config files themselves is trivial for me — it's just Markdown and JSON. But the full lifecycle (preview, deploy, domain, settings) is gated behind a local dev server and a dashboard/Git integration I can't operate headlessly. So: easy to author, not manageable end-to-end by me alone.

Unblocked path, if you want one: you create the free Mintlify account and connect a GitHub repo; I can then write and commit the docs content to that repo, and Mintlify auto-deploys on push — that workflow I can act on. Say the word and I'll scaffold the repo content.

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