# AX Check: gameye.com Checked 2026-10-16. Gameye's docs, pricing, and setup all work cleanly for agents. All 23 checklist items passed: quickstart, API/MCP docs, and SDKs are reachable, and pricing is stated upfront with units and limits. ## Onboarding needs a login ## Coding sessions Three independent coding sessions (DeepSeek V4.1 Flash, Kimi K3, Qwen 3.8 Max) each reviewed pricing and completed the task, correctly quoting on-demand and reserved per-vCPU-hour rates, RAM ratios, the 8-core reserved minimum, and per-second billing details straight from the pricing page. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/6989f59f-664d-4f10-b924-38c7f2ae3b39) · [Read transcript](https://www.ax-check.com/gameye.com/sessions/deepseek.json) Quoted per-vCPU-hour rates by plan (on-demand vs reserved) and RAM ratio (2 GB vs 4 GB), plus the reserved minimum of one 8-core machine per region and per-second billing. Gave a worked cost example: 2 vCPU / 4 GB, on-demand, 90 seconds. (seq 46, seq 110, gameye-example/README.md) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent never obtained a real Gameye API token. It explored docs, downloaded the OpenAPI spec, and confirmed the hosted sandbox/production endpoints return structured 401s for unauthenticated/malformed requests, but it stopped short of creating credentials or performing any authenticated operation. The 'live' test used a deliberately invalid dummy token and received a 401, which is explicitly insufficient per the verification bar. The rest of the example run was a local --dry-run mock with no network calls. Event 108: ```text GAMEYE_TOKEN=dummy.invalid.token GAMEYE_IMAGE=my-game node example.mjs ``` Event 108: ```text Gameye 401 on /available-location/my-game: Please verify that you are using a valid auth token. ``` Event 110: ```text I can't verify a real session start. That needs an API token *and* an application with a tag loaded on nodes — neither of which exists in this environment (no `GAMEYE_TOKEN`, no Gameye account). ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to get an API token without human/account setup**: Gameye's Admin Panel is where API tokens, applications, and image tags get created, and the OpenAPI docs page tells users to ask support for a bearer token. The sandbox has no self-serve token-issuance path reachable from this environment, so the agent could not acquire real credentials on its own. This is a product/account-provisioning limitation, not an agent error — the agent correctly identified it and stopped rather than fabricating success. Event 45: ```text You’ll need to ask our support team for your Bearer Token. Then, make sure you add it in the header of each request. ``` Event 110: ```text I can't verify a real session start. That needs an API token *and* an application with a tag loaded on nodes — neither of which exists in this environment (no `GAMEYE_TOKEN`, no Gameye account). ``` - **Direct connection to api.gameye.com timed out**: An early connectivity probe to a guessed bare host (api.gameye.com) timed out rather than resolving; the agent treated this as inconclusive and moved on to the documented hosts (api.sandbox-gameye.gameye.net / api.production-gameye.gameye.net) found via the docs, which did respond. This is a minor test-environment/network hiccup, not a product defect, since the agent did not rely on the broken host for any conclusion. Event 10: ```text curl: (28) Operation timed out after 15002 milliseconds with 0 bytes received api.gameye.com: 000 ``` #### Suggested Changes - **Reconcile the two different token-acquisition stories in the docs**: The API v2 Authentication page describes a full self-service flow (sign in to Admin Panel, Users, Edit, +Add Token), while the OpenAPI spec reference page tells readers to ask support for a bearer token. A first-time developer following the OpenAPI spec page would believe self-service isn't possible. Update the OpenAPI spec page (gameye.com/docs/api-v2/open-api-spec/) to point to the Admin Panel self-service steps instead of 'ask our support team', and confirm by re-reading that page for a reference to the Admin Panel token flow. Event 45: ```text You’ll need to ask our support team for your Bearer Token. Then, make sure you add it in the header of each request. ``` Event 31: ```text Create or retrieve an API token in the Gameye Admin Panel: Sign in to the Admin Panel. ``` - **Remove or clearly flag the stale npm SDK package**: The npm registry lists @gameye/sdk at version 0.0.3-0 published in 2019 with no indication it's deprecated, which could mislead a developer searching npm into using an abandoned package instead of the current REST API v2. Add a deprecation notice to the @gameye/sdk npm package (via npm deprecate) or update its README to redirect to the REST API docs, and verify by checking that npm view @gameye/sdk shows a deprecation warning. Event 17: ```text {"name":"@gameye/sdk","keywords":[],"version":"0.0.3-0","description":"Node.js SDK for Gameye" ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/4762f6f7-5e85-4ecf-9675-de6c32e95c7c) · [Read transcript](https://www.ax-check.com/gameye.com/sessions/kimi.json) Quoted per-vCPU/hr rates sourced from pricing page, tied to plan (on-demand vs reserved), RAM ratio, 8-core per-region minimum, and BYO tier (seq 25, seq 85, README.md) #### End-to-end onboarding - **Onboarding needs a login**: The agent researched Gameye's docs and pricing thoroughly and built a working REST API example, but never obtained real API credentials. It attempted a dummy-token call which correctly produced a 401 from the live API (proving the endpoint is real and reachable), but no authenticated operation was ever performed. The agent explicitly stopped at the trial sign-up step, stating it lacks an email inbox to complete the self-serve trial sign-up. Event 65: ```text 200 Gameye Admin Panel ``` Event 54: ```text {"code":"UNAUTHORIZED","details":"The provided token is malformed, please ensure you provide a token of the form 'Bearer \u003ctoken\u003e'","identifier":"453a3205-495b-41c9-a267-0ba7378174cb","message":"Unable to authorize request.","path":"/session","statusCode":401,"timestamp":"2026-10-16T14:55:32Z","violations":[]} ``` Event 85: ```text I can't complete the last step myself: the free trial at `trial.gameye.com` requires signing up with an email address I can verify, and I don't have an inbox. ``` #### Hallucinated URLs - **Guessed getting-started API doc path returned 404**: The agent guessed a docs URL path for the API quickstart before discovering the real site navigation structure. This was a one-off guess (not a documented link later proven broken), and the agent immediately recovered by scraping the real sitemap from the docs homepage, so it is a borderline case included for transparency rather than a confirmed defect. Event 24: ```text https://docs.gameye.com/getting-started/start-with-the-api ``` Event 26: ```text 404 | Gameye Docs Skip to content Gameye Docs Search Ctrl K Cancel Discord Select theme Dark Light Auto 404 Page not found. Check the URL or try using the search bar. ``` - **Guessed FAQ URL slug returned 404**: The agent guessed a docs FAQ URL path ('/docs/faqs/free/') without having seen it linked anywhere in the scraped navigation, and the request returned a 404. This looks like an invented slug rather than a broken documented link, since the actual FAQ navigation items seen earlier (e.g. 'Is Gameye free to use?') did not match this slug pattern. Event 53: ```text https://docs.gameye.com/docs/faqs/free/ ``` Event 55: ```text 404 | Gameye Docs Skip to content Gameye Docs Search Ctrl K Cancel Discord Select theme Dark Light Auto 404 Page not found. Check the URL or try using the search bar. ``` #### Blockers - **Self-serve trial sign-up requires a verifiable email inbox**: The hosted trial sign-up at trial.gameye.com is a client-side app that the agent could reach (HTTP 200, loads the Admin Panel shell) but could not complete, since finishing sign-up needs a real, verifiable email address the agent doesn't have. This is a normal session/environment limitation (no human in the loop to receive a verification email), not a product defect — the product does offer self-service sign-up per its own marketing copy. Event 65: ```text 200 Gameye Admin Panel ``` Event 85: ```text I can't complete the last step myself: the free trial at `trial.gameye.com` requires signing up with an email address I can verify, and I don't have an inbox. ``` - **Published npm SDK targets a legacy/deprecated API version**: The only published Node SDK (@gameye/sdk on npm) is low-version (0.0.3-0, published over a year ago) and, per the agent's own README note, targets Gameye's legacy v1 API rather than the current documented v2 REST API. This is a product/packaging issue: a developer searching npm for an official SDK would get a stale package misaligned with current docs, forcing a fallback to plain REST calls. Event 9: ```text @gameye/sdk@0.0.3-0 | ISC | deps: 8 | versions: 13 Node.js SDK for Gameye https://github.com/Gameye/gameye-sdk-node#readme ``` Event 9: ```text published over a year ago by elmerbulthuis ``` #### Suggested Changes - **Fix or redirect the broken getting-started API quickstart URL pattern**: Requests to plausible quickstart-style paths such as '/getting-started/start-with-the-api' and '/docs/faqs/free/' return plain 404s instead of redirecting to the real pages ('/docs/getting-started/4-api-call/' and the actual free-trial FAQ entry). Add redirects from likely guessed slugs to the canonical docs pages, or ensure the 404 page itself surfaces a search/sitemap link prominently (verify by curling the old paths and confirming a 301 or helpful fallback instead of a bare 404). Event 26: ```text 404 | Gameye Docs Skip to content Gameye Docs Search Ctrl K Cancel Discord Select theme Dark Light Auto 404 Page not found. Check the URL or try using the search bar. ``` Event 55: ```text 404 | Gameye Docs Skip to content Gameye Docs Search Ctrl K Cancel Discord Select theme Dark Light Auto 404 Page not found. Check the URL or try using the search bar. ``` - **Update or deprecate the @gameye/sdk npm package**: The only published Node SDK on npm (@gameye/sdk, v0.0.3-0) is over a year old and targets the legacy v1 API, not the current v2 REST API documented at docs.gameye.com. Either publish an updated SDK aligned with v2, or add a deprecation notice on the npm package page pointing developers to the plain REST API docs. Verify by running 'npm view @gameye/sdk' and confirming the README or deprecation flag references the v2 API. Event 9: ```text @gameye/sdk@0.0.3-0 | ISC | deps: 8 | versions: 13 Node.js SDK for Gameye https://github.com/Gameye/gameye-sdk-node#readme ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/32bda056-c18a-4de7-aa49-9b893d9d3f7d) · [Read transcript](https://www.ax-check.com/gameye.com/sessions/qwen.json) Quoted per-vCPU-hour rates for on-demand and reserved, by RAM ratio. Named the assumptions: reserved needs an 8-core machine per region; per-second billing with TTL; no egress fees; free trial. (seq 27, seq 116, seq 195, gameye-example/README.md) #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained a real Gameye API token during the session. It searched the sandbox environment for credentials, found none, tried app.gameye.com (returned curl code 000, unreachable), and ultimately ran its built example against the live sandbox API using a self-typed bogus token, which correctly returned a 401 Unauthorized. No authenticated operation against the real product was ever demonstrated. Event 4: ```text env | grep -i -E "gameye|token|api|key" | sed 's/=.*/=/ ``` Event 115: ```text app.gameye.com:000 ``` Event 168: ```text API ERROR 401 UNAUTHORIZED GET /region -> 401 UNAUTHORIZED: Please verify that you are using a valid auth token. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No API token available, so live calls cannot authenticate**: The sandbox had no Gameye credentials and the Admin Panel (app.gameye.com) was unreachable from the environment, so the agent could not self-serve a token. This is a credentials/test-environment limitation, not a product defect — Gameye's own docs require token creation through a human login to the Admin Panel. Event 4: ```text env | grep -i -E "gameye|token|api|key" | sed 's/=.*/=/ ``` Event 115: ```text app.gameye.com:000 ``` Event 168: ```text GET /region -> 401 UNAUTHORIZED: Please verify that you are using a valid auth token. ``` - **Official npm SDK and API-spec package are broken/outdated**: The official @gameye/sdk package is legacy (2018-era, version 0.0.3-0) and its README says to email support for an API key rather than self-serve; the @gameye/match-api-spec package fails to install due to a missing transitive dependency. This is a product/package-maintenance issue rather than agent error, and it pushed the agent to use the raw REST API and the hosted OpenAPI YAML instead. Event 35: ```text npm error 404 '@oas3/oas3ts-lib@^4.0.0' is not in this registry. ``` Event 28: ```text You need an API key to use this SDK, to obtain a free Gameye API key, please send us [an email](mailto:support@gameye.com) ``` #### Suggested Changes - **Reconcile the LeaveSession OpenAPI schema with the reference docs**: The published OpenAPI spec at https://api.production-gameye.gameye.net/openapi.yaml declares LeaveSession with only a `players` field (additionalProperties: false), but the reference doc page for DELETE /session/player/leave requires both `session` and `players`. Fix by adding `session` as a required property to the LeaveSession schema in the spec, then confirm by re-running a schema diff against the reference docs for that endpoint. Event 85: ```text LeaveSession: type: object additionalProperties: false required: - players ``` Event 108: ```text session string Yes The ID of the session to remove players from. ``` - **Update or deprecate the legacy @gameye/sdk npm package**: The npm package @gameye/sdk (Node.js SDK, latest version 0.0.3-0) still instructs new developers to email support@gameye.com for an API key and references a 2017-2018 example app, which conflicts with the current self-serve token flow described in the Admin Panel docs. Update the README on https://github.com/Gameye/gameye-sdk-node (or deprecate the npm listing) to point to the current Session API and Admin Panel token creation flow. Event 28: ```text You need an API key to use this SDK, to obtain a free Gameye API key, please send us [an email](mailto:support@gameye.com) ``` - **Fix the broken @gameye/match-api-spec npm install**: Installing @gameye/match-api-spec fails immediately because its dependency @oas3/oas3ts-lib@^4.0.0 is not published to the npm registry. Pin or remove that dependency in the package's package.json and verify by running npm install @gameye/match-api-spec in a clean directory to confirm it succeeds. Event 35: ```text npm error 404 '@oas3/oas3ts-lib@^4.0.0' is not in this registry. ``` ### Task given to each agent Help me build a simple example using Gameye. 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 with 200 when requested with Accept: text/markdown. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt links docs, API reference, getting started, MCP, skills and pricing JSON. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt organizes links under Platform, API documentation, AI agents and Migration sections. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt AI agents section names MCP server, agent skills and API docs. ``` - **Pass** — A compact guide representation exists ```text Homepage served text/markdown via content negotiation; llms.txt also offers .md copies of each page. ``` - **Pass** — A focused guide is directly retrievable ```text llms.txt and docs/getting-started give a directly retrievable, actionable 4-step quickstart. ``` - **Pass** — Equivalent instructions fit a token budget ```text llms.txt is 4979 tokens, well under the 8000-token budget, and remains a usable guide. ``` - **Pass** — Product-docs links survive format changes ```text Homepage Markdown retains docs, pricing, and getting-started links; docs routes survive the format change. ``` - **Pass** — The compact guide is independently actionable ```text GHCR guide gives concrete steps: publish image, grant access, create app, load tag, start session. ``` - **Pass** — Install and next-step links resolve ```text Getting-started and GHCR pages fetched 200; install and next-step links resolve. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Getting Started lists four concrete setup steps from Docker Hub to first API session. ``` - **Pass** — Installation commands are extractable ```text GHCR guide gives extractable curl commands and a full GitHub Actions workflow. ``` - **Pass** — Code examples are available without interaction ```text Docs show curl examples for tokens, tags and POST /session without interaction. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text Prerequisites list Linux server, Docker, registry and account; auth uses Bearer token. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders on-demand $0.07/vCPU/hr and reserved $0.035/vCPU/hr without interaction. ``` - **Pass** — Prices are stated, not gated ```text On-demand, reserved and BYOI prices are stated publicly, not gated behind a sales call. ``` - **Pass** — Pricing units and limits are explicit ```text Units explicit: per vCPU/hr, per-second billing, 1 vCPU:2GB or 4GB RAM, no minimum session. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Quoted per-vCPU-hour rates by plan (on-demand vs reserved) and RAM ratio (2 GB vs 4 GB), plus the reserved minimum of one 8-core machine per region and per-second billing. Gave a worked cost example: 2 vCPU / 4 GB, on-demand, 90 seconds. (seq 46, seq 110, gameye-example/README.md) Kimi K3: Quoted per-vCPU/hr rates sourced from pricing page, tied to plan (on-demand vs reserved), RAM ratio, 8-core per-region minimum, and BYO tier (seq 25, seq 85, README.md) Qwen 3.8 Max: Quoted per-vCPU-hour rates for on-demand and reserved, by RAM ratio. Named the assumptions: reserved needs an 8-core machine per region; per-second billing with TTL; no egress fees; free trial. (seq 27, seq 116, seq 195, gameye-example/README.md) This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text Docs sidebar lists an Open API Spec page and a full API V2 reference with per-endpoint pages. ``` - **Pass** — An MCP server is documented and well-formed ```text gameye-mcp documented: npx -y gameye-mcp, GAMEYE_API_TOKEN, tool list, guardrails, npm/GHCR/registry. ``` - **Pass** — A CLI install path is documented ```text CLI install path documented: npx -y gameye-mcp and npx skills add gameye/gameye-skills. ``` - **Pass** — SDK packages resolve on their registries ```text gameye-mcp published on npm and ghcr.io/gameye/gameye-mcp; npm fetch was 403-blocked, not a missing package. ``` - **Pass** — Agent skills are published ```text gameye-skills repo publishes twelve SKILL.md agent skills with install and update instructions. ``` [Full report data](https://www.ax-check.com/gameye.com/report.json)