ax-check.com
by Gauge
P
Plank+Beam
plankandbeam.com
ax-check.com
Checked 22 October 2026
B
67/100
Agents haven’t verified setup
Agent gets shopping steps, but the MCP tool link is dead
The agent guide outlines clear shopping steps and auth rules, but its advertised MCP endpoint returns a 404, and no session could pull a live price.
4 fixes to start with
Concrete changes, backed by what we found.
Correct the MCP connection instructions.
llms.txt advertises MCP endpoint https://plankandbeam.com/api/ucp/mcp, but that URL returns 404.
llms.txt advertises MCP endpoint https://plankandbeam.com/api/ucp/mcp, but that fetch returned 404.
Linked from plankandbeam.com/llms.txt
Recorded coding sessions
Same task, 3 models, no plankandbeam.com account. Recorded 22 October 2026 on Pi.
3 recorded · 34s
34s · recorded
Session findings
Select a finding to see it in context.
›Thinking…
Let me look at the repo to understand the context. "Plank+Beam" — maybe it's a product in this repo? Let me explore.
I'll start by looking at the repository to understand what we're working with.
ls -la /sandbox/repo && echo "---README---" && ls *.md 2>/dev/null
Failedtotal 16
total 16 drwxr-xr-x 3 root root 4096 Sep 18 08:00 . drwxr-xr-x 7 root root 4096 Oct 22 17:41 .. drwxr-xr-x 8 root root 4096 Sep 24 20:05 .git -rw-r--r-- 1 root root 408 Sep 18 08:00 .gitignore ---README--- Command exited with code 2
Recorded tool call
{
"type": "tool_call",
"seq": 4,
"ts": "2026-10-22T17:41:39.150Z",
"name": "bash",
"turn": 1,
"input": {
"command": "ls -la /sandbox/repo && echo \"---README---\" && ls *.md 2>/dev/null"
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-a9ba57574a444899",
"tool_kind": "shell"
}Recorded tool result
{
"type": "tool_result",
"seq": 6,
"ts": "2026-10-22T17:41:39.150Z",
"turn": 1,
"output": {
"content": [
{
"text": "total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Oct 22 17:41 ..\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---README---\n\n\nCommand exited with code 2",
"type": "text"
}
],
"details": {}
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-a9ba57574a444899",
"is_error": true,
"tool_kind": "shell"
}cd /sandbox/repo && git log --oneline -20 2>/dev/null | head -30; echo "---"; find . -maxdepth 2 -type d -not -path '*/node_modules*' -not -path '*/.git*' | head -50
9ebf5fb Initial workspace
9ebf5fb Initial workspace --- .
Recorded tool call
{
"type": "tool_call",
"seq": 5,
"ts": "2026-10-22T17:41:39.150Z",
"name": "bash",
"turn": 1,
"input": {
"command": "cd /sandbox/repo && git log --oneline -20 2>/dev/null | head -30; echo \"---\"; find . -maxdepth 2 -type d -not -path '*/node_modules*' -not -path '*/.git*' | head -50"
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-be8b435b1502bcf6",
"tool_kind": "shell"
}Recorded tool result
{
"type": "tool_result",
"seq": 7,
"ts": "2026-10-22T17:41:39.150Z",
"turn": 1,
"output": {
"content": [
{
"text": "9ebf5fb Initial workspace\n---\n.\n",
"type": "text"
}
]
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-be8b435b1502bcf6",
"is_error": false,
"tool_kind": "shell"
}›Thinking…
The repo is essentially empty — just a .gitignore and one commit "Initial workspace". So there's no existing Plank+Beam codebase here. Let me check the .gitignore for hints, and check whether there's any known product "Plank+Beam". I should be honest: I don't know this product. Let me check for network access, npm registry, docs.
Let me check .gitignore content and search for any local references.
✓read /sandbox/repo/.gitignore✓└{"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","type":"text"}]}cd /sandbox/repo && grep -ri "plank" . --include=* -l 2>/dev/null | head; echo "--- env hints ---"; env | grep -i -E "plank|beam|api|key|token" | sed 's/=.*/=<redacted>/' | head -20
--- env hints ---
--- env hints --- PI_GATEWAY_API_KEY=<redacted> GIT_CONFIG_KEY_0=<redacted>
Recorded tool call
{
"type": "tool_call",
"seq": 11,
"ts": "2026-10-22T17:41:41.380Z",
"name": "bash",
"turn": 1,
"input": {
"command": "cd /sandbox/repo && grep -ri \"plank\" . --include=* -l 2>/dev/null | head; echo \"--- env hints ---\"; env | grep -i -E \"plank|beam|api|key|token\" | sed 's/=.*/=<redacted>/' | head -20"
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-b0da563b09c0859d",
"tool_kind": "shell"
}Recorded tool result
{
"type": "tool_result",
"seq": 13,
"ts": "2026-10-22T17:41:41.380Z",
"turn": 1,
"output": {
"content": [
{
"text": "--- env hints ---\nPI_GATEWAY_API_KEY=<redacted>\nGIT_CONFIG_KEY_0=<redacted>\n",
"type": "text"
}
]
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-b0da563b09c0859d",
"is_error": false,
"tool_kind": "shell"
}›Thinking…
The repo is empty — a blank workspace with just a .gitignore. There's no Plank+Beam product, SDK, API key, docs, or anything in the environment.
Let me check whether there's network access and whether "Plank+Beam" is a real thing I can look up. Let me try npm registry / pip / web search quickly. But I should be careful not to fabricate.
Let me check network connectivity quickly with short timeouts.
cd /tmp && timeout 15 curl -sS -o /dev/null -w "npm:%{http_code}\n" https://registry.npmjs.org/plank-beam 2>&1 | head -5; timeout 15 curl -sS -o /dev/null -w "pypi:%{http_code}\n" https://pypi.org/pypi/plank-beam/json 2>&1 | head -5npm:404
npm:404 pypi:404
Recorded tool call
{
"type": "tool_call",
"seq": 16,
"ts": "2026-10-22T17:41:43.684Z",
"name": "bash",
"turn": 1,
"input": {
"command": "cd /tmp && timeout 15 curl -sS -o /dev/null -w \"npm:%{http_code}\\n\" https://registry.npmjs.org/plank-beam 2>&1 | head -5; timeout 15 curl -sS -o /dev/null -w \"pypi:%{http_code}\\n\" https://pypi.org/pypi/plank-beam/json 2>&1 | head -5"
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-970f7f28a8c8ecbd",
"tool_kind": "shell"
}Recorded tool result
{
"type": "tool_result",
"seq": 18,
"ts": "2026-10-22T17:41:44.477Z",
"turn": 1,
"output": {
"content": [
{
"text": "npm:404\npypi:404\n",
"type": "text"
}
]
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-970f7f28a8c8ecbd",
"is_error": false,
"tool_kind": "shell"
}cd /tmp && for q in "plank-beam" "plank%2Bbeam" "plankbeam"; do timeout 12 curl -sS "https://registry.npmjs.org/-/v1/search?text=$q&size=3" 2>/dev/null | head -c 400; echo; done
{"objects":[{"downloads":{"monthly":97204361,"weekly":13414089},"dependents":"33","updated":"2026-10-19T12:46:11.001Z","searchScore":117.299545,"package":{"name
{"objects":[{"downloads":{"monthly":97204361,"weekly":13414089},"dependents":"33","updated":"2026-10-19T12:46:11.001Z","searchScore":117.299545,"package":{"name":"@types/triple-beam","keywords":[],"version":"1.3.5","description":"TypeScript definitions for triple-beam","sanitized_name":"@types/triple-beam","publisher":{"email":"ts-npm-types@microsoft.com","username":"types"},"maintainers":[{"email
{"objects":[{"downloads":{"monthly":97204361,"weekly":13414089},"dependents":"33","updated":"2026-10-19T12:46:11.001Z","searchScore":117.299545,"package":{"name":"@types/triple-beam","keywords":[],"version":"1.3.5","description":"TypeScript definitions for triple-beam","sanitized_name":"@types/triple-beam","publisher":{"email":"ts-npm-types@microsoft.com","username":"types"},"maintainers":[{"email
{"objects":[],"total":0,"time":"2026-10-22T17:41:45.257Z"}
Recorded tool call
{
"type": "tool_call",
"seq": 17,
"ts": "2026-10-22T17:41:43.684Z",
"name": "bash",
"turn": 1,
"input": {
"command": "cd /tmp && for q in \"plank-beam\" \"plank%2Bbeam\" \"plankbeam\"; do timeout 12 curl -sS \"https://registry.npmjs.org/-/v1/search?text=$q&size=3\" 2>/dev/null | head -c 400; echo; done"
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-b285ec7180a5a067",
"tool_kind": "shell"
}Recorded tool result
{
"type": "tool_result",
"seq": 19,
"ts": "2026-10-22T17:41:45.555Z",
"turn": 1,
"output": {
"content": [
{
"text": "{\"objects\":[{\"downloads\":{\"monthly\":97204361,\"weekly\":13414089},\"dependents\":\"33\",\"updated\":\"2026-10-19T12:46:11.001Z\",\"searchScore\":117.299545,\"package\":{\"name\":\"@types/triple-beam\",\"keywords\":[],\"version\":\"1.3.5\",\"description\":\"TypeScript definitions for triple-beam\",\"sanitized_name\":\"@types/triple-beam\",\"publisher\":{\"email\":\"ts-npm-types@microsoft.com\",\"username\":\"types\"},\"maintainers\":[{\"email\n{\"objects\":[{\"downloads\":{\"monthly\":97204361,\"weekly\":13414089},\"dependents\":\"33\",\"updated\":\"2026-10-19T12:46:11.001Z\",\"searchScore\":117.299545,\"package\":{\"name\":\"@types/triple-beam\",\"keywords\":[],\"version\":\"1.3.5\",\"description\":\"TypeScript definitions for triple-beam\",\"sanitized_name\":\"@types/triple-beam\",\"publisher\":{\"email\":\"ts-npm-types@microsoft.com\",\"username\":\"types\"},\"maintainers\":[{\"email\n{\"objects\":[],\"total\":0,\"time\":\"2026-10-22T17:41:45.257Z\"}\n",
"type": "text"
}
]
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-b285ec7180a5a067",
"is_error": false,
"tool_kind": "shell"
}›Thinking…
Confirmed: network works (npm registry reachable), but there is no "Plank+Beam" package on npm or PyPI. The repo is empty. There's no API key, no docs, no SDK.
Let me do one more quick check — maybe a docs site or GitHub. But honestly I should be careful about spending too much. Let me do a quick GitHub search and a general web check.
cd /tmp && timeout 15 curl -sS "https://api.github.com/search/repositories?q=plank-beam&per_page=3" 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); print('total:',d.get('total_count')); [print(r['full_name'], '|', (r.get('description') or '')[:80]) for r in d.get('items',[])]" 2>&1 | head -10total: 3
total: 3 dunabia/Plank-Beam | nick-van-h/cutlistcalculator | Calculates most optimal cutlist for beams/planks vicyap/theseus | Replace every plank while the ship keeps sailing: AI-authored hot code loading o
Recorded tool call
{
"type": "tool_call",
"seq": 22,
"ts": "2026-10-22T17:41:48.409Z",
"name": "bash",
"turn": 1,
"input": {
"command": "cd /tmp && timeout 15 curl -sS \"https://api.github.com/search/repositories?q=plank-beam&per_page=3\" 2>/dev/null | python3 -c \"import sys,json; d=json.load(sys.stdin); print('total:',d.get('total_count')); [print(r['full_name'], '|', (r.get('description') or '')[:80]) for r in d.get('items',[])]\" 2>&1 | head -10"
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-9581915d3dbddc61",
"tool_kind": "shell"
}Recorded tool result
{
"type": "tool_result",
"seq": 25,
"ts": "2026-10-22T17:41:49.234Z",
"turn": 1,
"output": {
"content": [
{
"text": "total: 3\ndunabia/Plank-Beam | \nnick-van-h/cutlistcalculator | Calculates most optimal cutlist for beams/planks\nvicyap/theseus | Replace every plank while the ship keeps sailing: AI-authored hot code loading o\n",
"type": "text"
}
]
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-9581915d3dbddc61",
"is_error": false,
"tool_kind": "shell"
}cd /tmp && timeout 15 curl -sS "https://api.github.com/search/repositories?q=plank+beam+sdk&per_page=5" 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); print('total:',d.get('total_count')); [print(r['full_name'],'|',(r.get('description') or '')[:80]) for r in d.get('items',[])]" 2>&1 | head -12total: 0
total: 0
Recorded tool call
{
"type": "tool_call",
"seq": 23,
"ts": "2026-10-22T17:41:48.409Z",
"name": "bash",
"turn": 1,
"input": {
"command": "cd /tmp && timeout 15 curl -sS \"https://api.github.com/search/repositories?q=plank+beam+sdk&per_page=5\" 2>/dev/null | python3 -c \"import sys,json; d=json.load(sys.stdin); print('total:',d.get('total_count')); [print(r['full_name'],'|',(r.get('description') or '')[:80]) for r in d.get('items',[])]\" 2>&1 | head -12"
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-950a0ed13e4663f2",
"tool_kind": "shell"
}Recorded tool result
{
"type": "tool_result",
"seq": 24,
"ts": "2026-10-22T17:41:49.234Z",
"turn": 1,
"output": {
"content": [
{
"text": "total: 0\n",
"type": "text"
}
]
},
"run_id": "cmvjtvbvi01az0jus8mzmotkj",
"tool_id": "chatcmpl-tool-950a0ed13e4663f2",
"is_error": false,
"tool_kind": "shell"
}›Thinking…
Confirmed. There's no "Plank+Beam" product with an SDK or API. The repo is empty. I should stop plainly and say so, per the user's instruction: "If this product has no developer workflow you can act on, say so plainly and stop."
I should not fabricate pricing or a build. I'll report:
- What I found (empty repo, no credentials, no package on npm/PyPI/GitHub).
- I cannot build an example or describe pricing without inventing it — and I won't invent it.
- What I need from them to proceed.
- The manageability question — I can answer briefly and honestly in the abstract: it depends on whether it's a hosted API/SDK product. I shouldn't pretend to have assessed a product I can't find. I'll give a conditional answer.
Keep it concise. No local stacks started, no long-running commands. Good.
Let me write the response.
I checked before writing any code, and I have to stop here: Plank+Beam has no developer workflow I can act on. I won't invent an example or a pricing model for a product I can't verify.
What I found
The workspace is empty. /sandbox/repo contains only a .gitignore (generic, multi-language) and a single commit, 9ebf5fb Initial workspace. No source, no docs, no SDK, no config:
/sandbox/repo
├── .git/
└── .gitignore # boilerplate ignore rules only
No credentials or endpoints are wired up. The only secrets in the environment are PI_GATEWAY_API_KEY (the agent harness itself) and a git config key. Nothing named for Plank or Beam — no API key, base URL, tenant, or org ID.
The product doesn't exist on any public registry. Network access works fine, so these are real negatives, not connectivity failures:
| Checked | Result |
|---|---|
registry.npmjs.org/plank-beam | 404 |
pypi.org/pypi/plank-beam/json | 404 |
npm search plankbeam | 0 results |
npm search plank-beam | only @types/triple-beam (unrelated logging lib) |
GitHub plank-beam | 3 repos, none a product/SDK — one is dunabia/Plank-Beam with no description |
GitHub plank beam sdk | 0 results |
So there's no SDK to install, no API to call, no quickstart to follow, and no published pricing page I could read.
Your three questions
Pricing — I can't tell you. Any numbers I gave would be fabricated. Pricing details live on the vendor's site or contract, neither of which is reachable from here.
Easy for me to manage? — I can't assess a product I can't see. Speaking generally: a hosted product with a real SDK, an API key, and versioned docs is easy for me to manage — I can install the client, write calls, read errors, and iterate. What blocks me is the absence of all three. That's a property of what's in this workspace, not a judgement on the product.
Am I blocked? — Yes, and per your instruction I've stopped rather than working around it. I did not start any local services or run anything long-lived; every command above was a short read-only lookup.
To unblock, send me any one of these
- A docs URL or API reference — enough for me to see the endpoints and auth scheme.
- The SDK package name as actually published (my guesses above may simply be wrong; the real name might be scoped, like
@plankbeam/sdk, or vendor-branded differently). - Credentials in the environment — an API key plus base URL, and I'll write the example against the live hosted API.
- Or the real source, if Plank+Beam is internal and this repo was supposed to be seeded with it. The
Initial workspacecommit suggests a setup step may not have completed.
Point me at any one of those and I'll build the example immediately.
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