# AX Check: getgalaxy.io Checked 2026-10-21. Docs and quickstart are solid, but pricing is never stated 17 of 23 checklist items pass, including quickstart, CLI install, and API docs. All pricing items are unassessed—no pricing page or stated prices found. ## Onboarding needs a login ## Coding sessions All three independent sessions completed. Two were asked to review pricing and both concluded Galaxy is free, citing hosted instances with shared compute/storage quotas and free self-hosting, though neither found an official pricing page confirming this. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/8b29d2ef-b8f2-4152-8f44-2424f97af2e2) · [Read transcript](https://www.ax-check.com/getgalaxy.io/sessions/deepseek.json) #### End-to-end onboarding - **Onboarding needs a login**: The agent used the hosted usegalaxy.org service and BioBlend SDK unauthenticated for read-only calls (version lookup, tool listing). It attempted a write operation (create history) without credentials and was rejected with a 403 requiring login. No account or API key was ever obtained during the session (registration requires email verification, which the agent cannot self-serve), so the authenticated write path was written but never executed or verified. Event 78: ```text {"err_msg":"You need to be logged in to create histories.","err_code":403001} HTTP 403 ``` Event 108: ```text **No API key** → I could not execute or verify the authenticated end-to-end path. I can't register an account for you (email verification), so this is a hard stop on the write path until you either paste a key or confirm you don't want that step run. ``` Event 106: ```text [2] Skipped: no GALAXY_API_KEY set. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **Write operations require a Galaxy account API key**: Product behavior: creating a history (and any authenticated write) on usegalaxy.org returns a 403 for anonymous/unauthenticated requests. The agent cannot self-register an account (needs email verification), so the full read-write example could only be written, not executed end-to-end. This is a normal auth requirement, not a product defect. Event 77: ```text POST anonymous history ``` Event 78: ```text {"err_msg":"You need to be logged in to create histories.","err_code":403001} HTTP 403 ``` - **Ambiguous product identity named 'Galaxy'**: Agent error/test-environment ambiguity: the prompt said 'Galaxy' without specifying which product, and web search surfaced at least four distinct products sharing the name (Ansible Galaxy, Galaxy digital-asset APIs at galaxy.com, Samsung Galaxy SDK, and the Galaxy Project bioinformatics platform at usegalaxy.org). The agent had to guess which one was intended, settling on the Galaxy Project/BioBlend platform, and flagged this guess to the user rather than being blocked outright. Event 28: ```text Galaxy APIs | Developer Portal Galaxy APIs Institutional-grade APIs for execution, balances, positions, staking, and onchain transaction submission ``` Event 108: ```text I assumed **Galaxy = the Galaxy Project** (the data-science/workflow platform, hosted at `usegalaxy.org`, with the official **BioBlend** Python SDK). That's the "Galaxy" whose quickstart involves a local server but which also exposes a hosted API. If you meant Ansible Galaxy or Galaxy Digital, say so and I'll redirect. ``` #### Suggested Changes - **Add a disambiguation landing page for 'Galaxy' search queries**: When a developer searches for Galaxy API/SDK docs, results return multiple unrelated 'Galaxy' products (Ansible Galaxy, galaxy.com digital assets, Samsung Galaxy, Galaxy Project/usegalaxy.org). Add a clear disambiguation note or distinct branding on the Galaxy Project developer docs homepage (galaxyproject.org/develop/api/) so agents and new developers land on the correct docs without burning multiple search/fetch cycles. Verify by searching 'Galaxy API SDK pricing' and confirming the intended docs site ranks clearly distinguishable from unrelated Galaxy products. Event 28: ```text Galaxy Pricing 2026 Learn more about the cost of Galaxy, different pricing plans, starting costs, free trials, and more pricing-related information provided by Galaxy. www.g2.com/products/galaxyap/pricing ``` - **Document the no-code-required path to an API key on the quickstart**: The develop/api page explains API keys exist but the agent had to separately discover the exact account menu path. Add the explicit self-service steps (account creation URL, then User -> Preferences -> Manage API Key) directly to https://galaxyproject.org/develop/api/ so developers do not need to infer the path from BioBlend's docstring or trial-and-error. Verify by following the documented steps on a fresh account and confirming an API key is produced without extra lookups. Event 62: ```text To use the API, you must first generate an API Key for the account you want to access Galaxy from. Please note that this key acts as an alternate means to access your account, and should be treated with the same care as your login password. You can do so in the UI under user preferences (while logged in). ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/fe730290-6a83-4619-a013-6738e70a2834) · [Read transcript](https://www.ax-check.com/getgalaxy.io/sessions/kimi.json) Said Galaxy is free and gave the basis: grant-funded public instances, a storage quota, queued shared compute, free self-hosting and no paid API tier. The ~250 GB quota figure wasn't verified from fetched data. (seq 30, seq 68) #### End-to-end onboarding - **Onboarding needs a login**: Agent never obtained credentials on its own. It probed usegalaxy.org anonymously and every write-capable endpoint (history creation, tool execution, user registration) returned 403s requiring login/admin rights. It wrote a BioBlend script that would perform an authenticated operation (create history, upload data, run tool, download result) but explicitly could not execute it, since registration requires email verification with no inbox available in the sandbox. No real credentials were ever acquired or used. Event 36: ```text {"err_msg":"You need to be logged in to create histories.","err_code":403001} ``` Event 43: ```text {"err_msg": "API authentication or Galaxy session required for this request", "err_code": 403001} ``` Event 68: ```text account creation is web-only with **email verification**, which I have no inbox to complete. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **Account registration requires email verification**: Creating a usegalaxy.org account (needed for an API key) is web-only and requires email verification, which the sandbox has no inbox to complete. This is a normal authentication requirement of the product, not a product defect, but it stopped the agent from running the authenticated write workflow end-to-end. Event 68: ```text account creation is web-only with **email verification**, which I have no inbox to complete. ``` - **Anonymous write operations rejected by the API**: Attempts to create a history and run a tool without authentication were rejected with 403 errors, confirming the public API is read-only for anonymous users. This is expected product behavior (auth required for write actions), not an agent mistake. Event 36: ```text {"err_msg":"You need to be logged in to create histories.","err_code":403001} ``` Event 43: ```text {"err_msg": "API authentication or Galaxy session required for this request", "err_code": 403001} ``` - **Self-service API registration is admin-gated**: Attempting to register a new user via the API (/api/users) returned an admin-only error, so there is no self-serve API path for account creation — confirming the web UI plus email verification is the only route. Event 43: ```text {"err_msg":"You must be logged in as an administrator to access this feature.","err_code":403006} ``` #### Suggested Changes - **Clarify that galaxy.ai is unrelated to the Galaxy project API**: The agent initially checked https://galaxy.ai expecting developer docs/pricing and found only a holding-company marketing page with no API, docs, or pricing endpoints (all 404). If 'Galaxy' branding confusion is a recurring issue, add a disambiguation note on relevant marketing or docs surfaces pointing developers to galaxyproject.org/usegalaxy.org. Event 16: ```text == https://galaxy.ai/api 404 https://galaxy.ai/api == https://galaxy.ai/pricing 404 https://galaxy.ai/pricing ``` - **Document that tool search returns bare ID strings, not objects**: Calling GET /api/tools?q=fastqc returns a flat list of ToolShed ID strings rather than objects with name/id fields, which broke the agent's first attempt to parse results (AttributeError on .get). Document the actual response shape in the API reference for the tools search endpoint so developers don't need to trial-and-error the schema. Event 52: ```text AttributeError: 'str' object has no attribute 'get' ``` Event 58: ```text ["toolshed.g2.bx.psu.edu/repos/devteam/fastqc/fastqc/0.74+galaxy1", "toolshed.g2.bx.psu.edu/repos/iuc/falco/falco/1.3.2+galaxy0" ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/ffc66517-439a-43ac-a791-c134bc2f695d) · [Read transcript](https://www.ax-check.com/getgalaxy.io/sessions/qwen.json) The agent said Galaxy is free and gave the basis. Hosted usegalaxy.org is free with a shared compute allowance and throttling instead of billing. Self-hosting costs only your own infrastructure. It cited no pricing docs. (seq 48) #### End-to-end onboarding - **Onboarding needs a login**: The agent reached the hosted Galaxy server (usegalaxy.org) and used it anonymously for read-only calls (listing tools), but every attempt to perform an authenticated write operation (creating a history) failed with a 403 requiring login. The agent could not obtain real API credentials on its own, since Galaxy requires creating an account via the web UI, which it explicitly said it could not do autonomously. No credentials were ever acquired, so no authenticated product operation was demonstrated. Event 33: ```text history creation failed: ConnectionError Unexpected HTTP status code: 403: {"err_msg":"You need to be logged in to create histories.","err_code":403001} ``` Event 48: ```text the **full workflow path requires an API key**, which requires creating an account via the web UI (email signup) — something I can't do autonomously ``` Event 46: ```text Connected to https://usegalaxy.org — 9055 public tools available. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **Authenticated Galaxy operations require web-signup account creation**: Creating a history (and by extension uploading data or running tools) on usegalaxy.org requires a logged-in account with an API key. The agent confirmed anonymous calls get a clear 403 and that obtaining an API key requires a web UI signup flow it cannot complete autonomously. This is a normal login/credential requirement of the hosted product, not a product defect, and it stopped the agent from demonstrating the full read-write workflow. Event 33: ```text history creation failed: ConnectionError Unexpected HTTP status code: 403: {"err_msg":"You need to be logged in to create histories.","err_code":403001} ``` Event 48: ```text the **full workflow path requires an API key**, which requires creating an account via the web UI (email signup) — something I can't do autonomously ``` #### Suggested Changes - **Add a self-service API key or token provisioning endpoint for usegalaxy.org**: Currently the only way to get a GALAXY_API_KEY is signing up through the web UI and visiting Preferences, which blocks any fully automated/developer-first onboarding flow. Consider exposing a scriptable account/token creation path (e.g., a documented API endpoint for registration or key issuance) so SDK users like bioblend can obtain credentials without a browser. Verify by scripting account creation and confirming a returned API key can call an authenticated endpoint like /api/histories successfully from a fresh script. Event 48: ```text the **full workflow path requires an API key**, which requires creating an account via the web UI (email signup) — something I can't do autonomously ``` ### Task given to each agent Help me build a simple example using Galaxy. 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. No product credentials were supplied and no purchases were authorized. ## Score: A · 100/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Pass** — Homepage answers Markdown requests ```text Homepage returned text/markdown (200) for the Markdown Accept header. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt (200) indexes Filament docs, quickstart, API reference, comparisons, and blog. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt groups links under Filament, Compare, Blog, Articles, and Optional headings. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt describes Filament's ConnectRPC API, CLI, web UI, and Go library. ``` - **Pass** — A compact guide representation exists ```text Quickstart served as text/markdown at /pages/guides/get-started/quickstart and .md variant. ``` - **Pass** — A focused guide is directly retrievable ```text Quickstart gives concrete steps: just infra, just dev, just test with prerequisites. ``` - **Pass** — Equivalent instructions fit a token budget ```text Markdown quickstart is 510 tokens, well under 8000 and under 40% of HTML. ``` - **Pass** — Product-docs links survive format changes ```text Markdown quickstart retains Architecture and Connectors next-step doc links. ``` - **Pass** — The compact guide is independently actionable ```text Quickstart gives concrete prerequisites and three commands (just infra, just dev, just test) with next steps. ``` - **Pass** — Install and next-step links resolve ```text Fetched quickstart, introduction, and API reference pages all returned HTTP 200. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Docs introduction links Quickstart and 'Your first pipeline' with concrete steps. ``` - **Pass** — Installation commands are extractable ```text CLI install commands extractable: curl install script, brew tap, GitHub Releases. ``` - **Pass** — Code examples are available without interaction ```text Quickstart and CLI pages show inline shell/YAML examples without interaction. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text Quickstart lists prerequisites; CLI documents auth login and service-account credentials. ``` ### Pricing - **Skipped** — Pricing is readable without interaction ```text No pricing page fetched; homepage shows no prices, only 'Talk to team' contact. ``` - **Skipped** — Prices are stated, not gated ```text No pricing page fetched; homepage shows no stated prices or plans. ``` - **Skipped** — Pricing units and limits are explicit ```text No pricing page fetched; no units or limits stated on homepage. ``` - **Pass** — Agents identify pricing and its assumptions ```text 2 of 3 sessions were judged on pricing; 0 fell short. Kimi K3: Said Galaxy is free and gave the basis: grant-funded public instances, a storage quota, queued shared compute, free self-hosting and no paid API tier. The ~250 GB quota figure wasn't verified from fetched data. (seq 30, seq 68) Qwen 3.8 Max: The agent said Galaxy is free and gave the basis. Hosted usegalaxy.org is free with a shared compute allowance and throttling instead of billing. Self-hosting costs only your own infrastructure. It cited no pricing docs. (seq 48) This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text ConnectRPC API reference with RPCs, auth, errors, pagination; OpenAPI 3.1 generated via buf. ``` - **Skipped** — An MCP server is documented and well-formed ```text No MCP server documentation found in fetched Filament docs or llms.txt. ``` - **Pass** — A CLI install path is documented ```text CLI install via curl script, Homebrew tap, and GitHub Releases; commands documented. ``` - **Skipped** — SDK packages resolve on their registries ```text Python and TypeScript SDKs referenced, but no registry lookup result supplied. ``` - **Skipped** — Agent skills are published ```text No agent skills published or documented in fetched evidence. ``` [Full report data](https://www.ax-check.com/getgalaxy.io/report.json)