Skip to content
Gauge

ax-check.com

SupplementDEX

supplementdex.com

ax-check.com

Checked 19 September 2026

B

80/100

Agents haven’t verified setup

Pricing is posted clearly, but agents still can't find it.

Prices are stated in plain text on the site ($15/mo, $69/yr, $169 lifetime), yet 2 of 3 coding sessions refused to report any figure at all.

2 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 even when Markdown was requested via Accept header.

Recorded coding sessions

Same task, 3 models, no supplementdex.com account. Recorded 19 September 2026 on Pi.

3 recorded · 1m 4s

1m 4s · 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 SupplementDEX. 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…

Let me look at the repository to find SupplementDEX.

$ ls /sandbox/repo{"content":[{"text":"(no output)","type":"text"}]}
Thinking…

Empty repo. Let me check hidden files.

$ ls -la /sandbox/repo; find / -iname "*supplement*" -maxdepth 6 2>/dev/null | head -50{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 04:19 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00…ctrl+o
{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 04:19 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00 .git\n-rw-r--r-- 1 root root  408 Sep 18 08:00 .gitignore\n","type":"text"}]}
Thinking…

Empty repo with git history. Let me check git log/branches.

$ cd /sandbox/repo && git log --oneline -5 && git branch -a && cat .gitignore{"content":[{"text":"9ebf5fb Initial workspace\n* main\n# Keep generated and vendored files out of source diffs.\n\n# Logs / OS cruft\n*.log\n.DS_Store\n\n# Jav…ctrl+o
{"content":[{"text":"9ebf5fb Initial workspace\n* main\n# Keep generated and vendored files out of source diffs.\n\n# Logs / OS cruft\n*.log\n.DS_Store\n\n# JavaScript / TypeScript\nnode_modules/\n.next/\ndist/\nbuild/\ncoverage/\n\n# Python\n.venv/\nvenv/\n__pycache__/\n*.py[cod]\n.pytest_cache/\n*.egg-info/\n\n# Rust\ntarget/\n\n# Go / PHP / Ruby vendored deps\nvendor/\n.bundle/\n\n# Java / Kotlin / Scala\n.gradle/\n\n# .NET\nbin/\nobj/\n\n# Elixir\n_build/\ndeps/\n\n# Dart / Flutter\n.dart_tool/\n","type":"text"}]}
Thinking…

The workspace is empty — no SupplementDEX code, docs, or SDK. Let me check if there's any network access / npm registry to find "SupplementDEX". But the instruction says stay light, use hosted product through SDK/API. But we have no knowledge of SupplementDEX. Let me quickly check if it exists as a package.

$ cd /tmp && (npm view supplementdex 2>&1 | head -5); pip download supplementdex -d /tmp/x --no-deps 2>&1 | tail -2; curl -s -m 8 -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/supplementde…{"content":[{"text":"npm error code E404\nnpm error 404 Not Found - GET https://registry.npmjs.org/supplementdex - Not found\nnpm error 404\nnpm error 404 'sup…ctrl+o
{"content":[{"text":"npm error code E404\nnpm error 404 Not Found - GET https://registry.npmjs.org/supplementdex - Not found\nnpm error 404\nnpm error 404  'supplementdex@*' is not in this registry.\nnpm error 404\nERROR: Could not find a version that satisfies the requirement supplementdex (from versions: none)\nERROR: No matching distribution found for supplementdex\n404\n","type":"text"}]}
Thinking…

Nothing exists. Also check variations quickly and any docs online? Probably no network to arbitrary docs. Let me do a quick check of a couple of name variants, then report.

I should say plainly: no developer workflow I can act on. But first give a bit of verification.

$ for n in supplement-dex supplement_dex supplementdex-sdk @supplementdex/sdk sdex; do printf "%s: " "$n"; curl -s -m 6 -o /dev/null -w "%{http_code}\n" "https://registry.npmjs.org/$n"; done; curl -s -m…{"content":[{"text":"supplement-dex: 404\nsupplement_dex: 404\nsupplementdex-sdk: 404\n@supplementdex/sdk: 404\nsdex: 404\npypi:404\n","type":"text"}]}ctrl+o
for n in supplement-dex supplement_dex supplementdex-sdk @supplementdex/sdk sdex; do printf "%s: " "$n"; curl -s -m 6 -o /dev/null -w "%{http_code}\n" "https://registry.npmjs.org/$n"; done; curl -s -m 8 -o /dev/null -w "pypi:%{http_code}\n" https://pypi.org/pypi/supplement-dex/json

Thinking…

No such product available. Report plainly and stop.

Also address the three questions: pricing — I can't verify, I won't invent. Ease of management — can't assess without a workflow.

Keep it concise.

Stopping: SupplementDEX has no developer workflow I can act on here.

What I checked:

  • /sandbox/repo is empty apart from .git and .gitignore (single commit 9ebf5fb Initial workspace). No SupplementDEX source, SDK, docs, config, or credentials anywhere on the filesystem (find / -iname "*supplement*" → nothing).
  • No public package to install under any obvious name — npm and PyPI all return 404 for supplementdex, supplement-dex, supplement_dex, supplementdex-sdk, @supplementdex/sdk, sdex.
  • So there's no hosted endpoint, no API key/env var convention, and no quickstart to follow. I didn't start any local stack or long-running command.

Answers to your questions:

  • How pricing works: I can't tell you. There's no pricing page, plan config, or billing metadata in the workspace, and the product isn't reachable from a registry. Anything I said would be invented, so I'm not going to guess.
  • Will it be easy for me to manage: Can't assess it. Manageability depends on whether there's a real API surface, idempotent operations, and credentials I can read — none of which exist yet. With zero artifacts, the honest answer is "unknown," not "easy."
  • Blocked: Yes. Specifically blocked on the product itself existing in a form I can reach.

To unblock, give me any one of: the repo/docs for SupplementDEX, an SDK package name or API base URL, or credentials/env vars plus a quickstart. Then I'll build the example through the hosted SDK/API only — no local services.

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