# AX Check: atlassian.com Checked 2026-10-05. Atlassian docs, pricing, and CLI setup are all agent-readable. 20 of 23 checklist items passed: docs index, install commands, MCP server, and pricing are all stated plainly without login walls. ## Onboarding needs a login ## Coding sessions All three independent agent sessions completed the task and reported Atlassian's tiered per-user pricing (Free/Standard/Premium/Enterprise), each noting assumptions like billing cadence and user minimums, with figures that varied slightly across sessions but consistently sourced from public pricing pages. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/2cc58f5f-dd39-43b6-a4e4-f10eac4f65df) · [Read transcript](https://www.ax-check.com/atlassian.com/sessions/deepseek.json) README.md and final summary state per-user/per-month pricing by tier (Free/Standard/Premium/Enterprise), annual vs monthly, Data Center seat minimums, Marketplace app fees, and Forge quota-based free tier, explicitly flagged as approximate assumptions. #### End-to-end onboarding - **Onboarding needs a login**: No Atlassian credentials were available in the sandbox and the agent never obtained real ones. It built a Jira REST API client and validated its request shape only by stubbing out fetch locally (synthetic 201 response), never hitting a real Atlassian-hosted endpoint with real auth. The agent explicitly flagged the missing-credentials blocker and stopped short of any authenticated operation against a real product instance. Event 7: ```text env | grep -iE 'atlassian|jira|confluence|bitbucket|forge' | sed 's/=.*/=/' || echo "none" ``` Event 35: ```text Created PROJ-7: https://example.atlassian.net/browse/PROJ-7 ``` Event 44: ```text this sandbox has no Atlassian account or API token, so I could not run an authenticated call against a real site. The code is ready; only credentials are missing. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Atlassian account or API token available**: The sandbox environment had zero Atlassian credentials set (confirmed via env grep), and there was no self-service path in-session to mint a real API token or account. This is a test-environment/credential limitation, not a product defect — Jira's REST API itself works as documented once a token exists. The agent correctly stopped short of claiming a real authenticated call succeeded. Event 7: ```text env (atlassian/jira/confluence) --- ``` Event 44: ```text this sandbox has no Atlassian account or API token, so I could not run an authenticated call against a real site. The code is ready; only credentials are missing. ``` - **Pricing pages are JS-rendered, no static price data scrapeable via curl**: Attempts to curl the live Jira and Confluence pricing pages for dollar figures returned no matches, since those pages render pricing client-side via JavaScript rather than serving it in the initial HTML. This forced the agent to rely on general knowledge/approximate pricing framing instead of live figures. This is a product/site-behavior limitation for simple HTTP fetching, not an agent error. Event 21: ```text == https://www.atlassian.com/software/jira/pricing == == https://www.atlassian.com/software/confluence/pricing == ``` #### Suggested Changes - **Provide a non-interactive / sandbox-friendly credential path for Forge**: The agent noted that Atlassian's first-party Forge SDK requires interactive, account-bound commands (forge login, forge deploy), which blocked any autonomous deployment test. Consider documenting a service-account or CI-token based auth flow for Forge CLI on the Forge quickstart page (developer.atlassian.com) so headless/agentic environments can authenticate without a human-driven browser login. Verify by running forge login with a token-based flag in a clean container and confirming deploy succeeds without interactive prompts. Event 44: ```text the first-party **Forge** app SDK is interactive/account-bound (`forge login`, `forge deploy`), so I can write and review Forge code but can't deploy it autonomously ``` - **Serve key pricing figures in static HTML on the pricing pages**: curl against the live Jira and Confluence pricing URLs returned no price text, implying figures are injected client-side via JavaScript. Add server-rendered pricing figures (or a lightweight JSON/pricing-API endpoint) at www.atlassian.com/software/jira/pricing and the Confluence equivalent so automated tools and simple HTTP clients can read current per-user pricing without executing JS. Verify by curling the page and confirming dollar amounts appear in the raw response body. Event 21: ```text == https://www.atlassian.com/software/jira/pricing == == https://www.atlassian.com/software/confluence/pricing == ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/3f273bfd-c272-4bb9-843d-7a3b8b487291) · [Read transcript](https://www.ax-check.com/atlassian.com/sessions/kimi.json) Final output gives per-user/month tiers (Free ≤10 users, Standard ~$8/mo, Premium ~$15/mo, Enterprise custom) and flags assumptions (annual billing, prices approximate, check atlassian.com for current numbers) at seq 13. #### End-to-end onboarding - **Onboarding needs a login**: The agent checked the environment for Atlassian credentials, found none, and explicitly stated it could not create an Atlassian account or API token itself since that requires human sign-up. It wrote an example script but never executed it against the hosted Jira API, so no authenticated operation was demonstrated. Event 3: ```text env | grep -iE 'atlassian|jira|confluence' ; ls /sandbox/repo ``` Event 13: ```text I can't run the example: this environment has no `ATLASSIAN_SITE`, `ATLASSIAN_EMAIL`, or `ATLASSIAN_API_TOKEN`, and I can't create an Atlassian account or API token myself (requires a human sign-up at id.atlassian.com → *Security → API tokens*). ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Atlassian credentials available in sandbox**: The environment had no ATLASSIAN_SITE, ATLASSIAN_EMAIL, or ATLASSIAN_API_TOKEN set, and the agent has no self-service path to create a Jira Cloud account or API token (that requires human sign-up at id.atlassian.com). This is a missing-credentials/test-environment limitation, not a product defect — Atlassian's API requires normal account authentication by design. Event 3: ```text env | grep -iE 'atlassian|jira|confluence' ; ls /sandbox/repo ``` Event 13: ```text I can't run the example: this environment has no `ATLASSIAN_SITE`, `ATLASSIAN_EMAIL`, or `ATLASSIAN_API_TOKEN`, and I can't create an Atlassian account or API token myself (requires a human sign-up at id.atlassian.com → *Security → API tokens*). ``` #### Suggested Changes None identified in this transcript. ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/07b44fb5-71f8-4dee-83d5-74f396c5ae2d) · [Read transcript](https://www.ax-check.com/atlassian.com/sessions/qwen.json) Final output gives tiered pricing (Free/Standard ~$8.15/user/mo/Premium ~$16/user/mo/Enterprise) with named assumptions — Jira Cloud product, per-user billing, free tier up to 10 users, API calls not separately billed. #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: Agent checked env vars for Atlassian credentials, found none, and never obtained or used real credentials. It wrote a local example script and only verified Python syntax and SDK import locally — no authenticated call to a hosted Atlassian product was ever made. Event 8: ```text I checked the environment: the repo is empty and there are **no Atlassian credentials** configured (no `ATLASSIAN_*` / `JIRA_*` env vars). ``` Event 16: ```text syntax OK SDK import OK ``` Event 18: ```text **Blocked on one thing:** there are no Atlassian credentials in this environment. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Atlassian credentials available in sandbox**: The sandbox environment had no ATLASSIAN_SITE, ATLASSIAN_EMAIL, or ATLASSIAN_API_TOKEN set, and the agent had no self-service way to obtain them. This is a test-environment/credential limitation, not a product defect — Atlassian API tokens require a human to create one via the Atlassian account portal. Event 3: ```text env | grep -iE "atlassian|jira|confluence|bitbucket" ; ls /sandbox/repo ``` Event 8: ```text the repo is empty and there are **no Atlassian credentials** configured (no `ATLASSIAN_*` / `JIRA_*` env vars) ``` Event 18: ```text To actually run it, set `ATLASSIAN_SITE` (e.g. `yourco.atlassian.net`), `ATLASSIAN_EMAIL`, `ATLASSIAN_API_TOKEN` (free to create at id.atlassian.com → Security → API tokens), and `JIRA_PROJECT_KEY`. ``` #### Suggested Changes None identified in this transcript. ### Task given to each agent Help me build a simple example using Atlassian. 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: B · 84/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html for a text/markdown request; no Markdown representation offered. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt returns 200 with organized sections linking to docs, APIs, MCP, CLI and pricing. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt groups links under clear headings like Products, Platform & Developer Resources, and Pricing. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt lists REST APIs, GraphQL, the Atlassian MCP Server, and TWG CLI agent skills. ``` - **Pass** — A compact guide representation exists ```text llms.txt is a compact Markdown index of Atlassian docs, products, APIs, MCP and pricing. ``` - **Pass** — A focused guide is directly retrievable ```text llms.txt fetched directly as text/plain Markdown with organized sections and starting guidance. ``` - **Pass** — Equivalent instructions fit a token budget ```text llms.txt measured 5709 tokens, well under the 8000-token budget. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats cannot be measured. ``` - **Pass** — The compact guide is independently actionable ```text llms.txt is a well-organized index with products, APIs, MCP, CLI, skills and pricing links. ``` - **Pass** — Install and next-step links resolve ```text Fetched signup, get-started, MCP and skills pages all returned 200 with usable content. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text TWG CLI docs give a Get started path: install, set up agent skills, browse examples. ``` - **Pass** — Installation commands are extractable ```text Install page lists concrete curl, PowerShell, MSI and pkg install commands. ``` - **Pass** — Code examples are available without interaction ```text Install and skills pages show inline code blocks for commands and prompts. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text Docs state OS/account prerequisites and OAuth 2.1 auth with separate Bitbucket token. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Service Collection pricing page shows Free, Standard $20, Premium $51.42 per agent/month without interaction. ``` - **Pass** — Prices are stated, not gated ```text Bitbucket pricing lists Free $0, Standard $3.65, Premium $7.25 per user/month publicly. ``` - **Pass** — Pricing units and limits are explicit ```text Pricing states per-agent/per-user units and limits like 3 agents free, 1,250 automation steps. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: README.md and final summary state per-user/per-month pricing by tier (Free/Standard/Premium/Enterprise), annual vs monthly, Data Center seat minimums, Marketplace app fees, and Forge quota-based free tier, explicitly flagged as approximate assumptions. Kimi K3: Final output gives per-user/month tiers (Free ≤10 users, Standard ~$8/mo, Premium ~$15/mo, Enterprise custom) and flags assumptions (annual billing, prices approximate, check atlassian.com for current numbers) at seq 13. Qwen 3.8 Max: Final output gives tiered pricing (Free/Standard ~$8.15/user/mo/Premium ~$16/user/mo/Enterprise) with named assumptions — Jira Cloud product, per-user billing, free tier up to 10 users, API calls not separately billed. This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text llms.txt links Jira, Confluence, Bitbucket REST API intros and a GraphQL gateway reference. ``` - **Pass** — An MCP server is documented and well-formed ```text Rovo MCP server documented with server URL, client setup, OAuth 2.1 auth and tool list. ``` - **Pass** — A CLI install path is documented ```text TWG CLI install page gives curl, pkg, MSI and PowerShell install commands plus twg doctor. ``` - **Skipped** — SDK packages resolve on their registries ```text No registry lookup result for an Atlassian SDK or packaged CLI package was supplied. ``` - **Pass** — Agent skills are published ```text TWG CLI agent skills page documents installable skills under .agents/skills with twg skills install. ``` [Full report data](https://www.ax-check.com/atlassian.com/report.json)