ax-check.com
by Gauge
A
AppealsDesk
appealsdesk.co.uk
ax-check.com
Checked 21 September 2026
A
100/100
Agents need your login
Docs are agent-ready, but actual pricing stays a mystery.
Homepage, llms.txt, API and MCP tools all check out clean, but only a single £20 fee is mentioned anywhere — no full pricing page exists for agents to cite.
1 fix to start with
Concrete changes, backed by what we found.
Recorded coding sessions
Same task, 3 models, no appealsdesk.co.uk account. Recorded 21 September 2026 on Pi.
3 recorded · 1m 6s
1m 6s · recorded
Session findings
Select a finding to see it in context.
›Thinking…
I'm checking the current directory and getting oriented with the repository structure.
✓$ pwd; ls -la; echo "---"; cat README* 2>/dev/null | head -100✓└{"content":[{"text":"/sandbox/repo\ntotal 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 21 21:22 ..\ndrwxr-xr-x 8 root root 40…ctrl+o
{"content":[{"text":"/sandbox/repo\ntotal 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 21 21:22 ..\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---\n","type":"text"}]}✓$ ls -R /sandbox 2>/dev/null | head -100; echo "ENV:"; env | grep -i -E "appeal|pi_" | head -40✓└{"content":[{"text":"/sandbox:\nrepo\n\n/sandbox/repo:\nENV:\nPI_CODING_AGENT=true\nPI_REASONING_LEVEL=medium\nPI_SESSION_FILE=/sandbox/.gauge/pi/sessions/2026-…ctrl+o
{"content":[{"text":"/sandbox:\nrepo\n\n/sandbox/repo:\nENV:\nPI_CODING_AGENT=true\nPI_REASONING_LEVEL=medium\nPI_SESSION_FILE=/sandbox/.gauge/pi/sessions/2026-09-21T21-22-55-909Z_01a0c5d9-bb25-747d-a45a-642d74900996.jsonl\nPI_PROVIDER=gauge-fireworks\nPI_MODEL=accounts/fireworks/models/qwen3p8-max\nPI_SESSION_ID=01a0c5d9-bb25-747d-a45a-642d74900996\nPI_GATEWAY_API_KEY=unused\n","type":"text"}]}›Thinking…
The repository is empty except for .git and .gitignore. "AppealsDesk" — I don't recognize this product. Check the git history and .gitignore.
✓$ cat .gitignore; echo "---"; git log --oneline | head; git show --stat HEAD 2>/dev/null | head -30✓└{"content":[{"text":"# 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/…ctrl+o
{"content":[{"text":"# 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---\n9ebf5fb Initial workspace\ncommit 9ebf5fbd2cef623cbb4d140d0c660320192c4977\nAuthor: Workspace Bootstrap <workspace@localhost>\nDate: Sat Jan 1 00:00:00 2000 +0000\n\n Initial workspace\n\n .gitignore | 41 +++++++++++++++++++++++++++++++++++++++++\n 1 file changed, 41 insertions(+)\n","type":"text"}]}✓$ pip index versions appealsdesk 2>&1 | head -3; npm view appealsdesk 2>&1 | head -3; pip download appealsdesk --no-deps -d /tmp/x 2>&1 | tail -2✓└{"content":[{"text":"ERROR: No matching distribution found for appealsdesk\nnpm error code E404\nnpm error 404 Not Found - GET https://registry.npmjs.org/appeal…ctrl+o
{"content":[{"text":"ERROR: No matching distribution found for appealsdesk\nnpm error code E404\nnpm error 404 Not Found - GET https://registry.npmjs.org/appealsdesk - Not found\nnpm error 404\nERROR: Could not find a version that satisfies the requirement appealsdesk (from versions: none)\nERROR: No matching distribution found for appealsdesk\n","type":"text"}]}›Thinking…
AppealsDesk doesn't exist on PyPI or npm. The repo is empty. There's no documentation and no SDK. Maybe there's a local package somewhere else? I'll check whether there are any credentials or docs in the sandbox. /sandbox only has the repo. No network documentation. There's no accessible developer workflow—meaning it's impossible to build a sample using this product. I should report this frankly and stop. Also, regarding pricing: unknown—don't fabricate. Regarding maintainability: the question is about product maintainability but... briefly, since the product isn't discoverable, it can't be managed.
I'm blocked, so here's the plain answer:
No developer workflow I can act on. I checked what's available:
- The workspace
/sandbox/repois empty — just a.gitignoreand one bootstrap commit. No docs, code, or config referencing AppealsDesk. - No credentials, API endpoints, or product materials exist anywhere in the sandbox (
envhas nothing AppealsDesk-related). - There's no published SDK:
appealsdeskreturns 404 on both npm and PyPI, and there's no discoverable public API documentation I can reach.
So I can't build an example against it — I'd have to invent an API, which would just be fiction.
Pricing: I have no information on how AppealsDesk pricing works. I won't guess at a pricing model for a product I can't verify exists. If you can share a pricing page, docs link, or API key + endpoint, I can act on that.
Will it be easy for me to manage? Not currently — with zero docs, no SDK, no API surface, and no credentials in this environment, there's nothing to manage. If AppealsDesk is a real product you have access to, give me: (1) a docs/quickstart URL or file, and (2) an API key or SDK package name. If the quickstart turns out to require running local service stacks (e.g., docker-compose, local servers), I'll flag that and stop per your instructions.
To unblock me, the simplest options are:
- Drop the API docs or SDK package name into the repo or tell me where to find them.
- Provide an endpoint + API key so I can write a minimal SDK/API example.
Until then, I'm stopping here as requested rather than fabricating an integration.
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