Skip to content
Gauge

ax-check.com

Atlassian

atlassian.com

ax-check.com

Checked 5 October 2026

B

84/100

Agents need your login

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.

2 fixes to start with

Concrete changes, backed by what we found.

Onboarding

Give agents a clear login handoff and a way to resume setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Docs

Return Markdown when clients request text/markdown.

Homepage returned text/html for a text/markdown request; no Markdown representation offered.

Recorded coding sessions

Same task, 3 models, no atlassian.com account. Recorded 5 October 2026 on Pi.

3 recorded · 37s

37s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
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.
Thinking…

The user wants to build a simple example using Atlassian. I don't have access to credentials. Let me check the environment to see if there's anything available.

env | grep -iE "atlassian|jira|confluence|bitbucket" ; ls /sandbox/repo
(no output)
(no output)
ls /usr/local/lib/node_modules/@earendil-works/pi-coding-agent/docs 2>/dev/null | head -40
compaction.md
compaction.md
containerization.md
custom-provider.md
development.md
docs.json
environment-variables.md
extensions.md
images
index.md
json.md
keybindings.md
llama-cpp.md
models.md
packages.md
prompt-templates.md
providers.md
quickstart.md
rpc.md
sdk.md
security.md
session-format.md
sessions.md
settings.md
shell-aliases.md
skills.md
terminal-setup.md
termux.md
themes.md
tmux.md
tui.md
usage.md
windows.md
Thinking…

The environment has no Atlassian credentials, and the repository is empty. Atlassian is a hosted product (Jira, Confluence), and has a REST API and SDK. Without credentials (API token, site domain), we cannot actually make calls. The user has requested to build a simple example — we can write a sample script that calls the Atlassian Jira REST API, but we can't execute it without authentication credentials. Is that a blocker? The user said, "Let me know if you get blocked." We can build a sample script and explain what credentials are needed. That's reasonable — no local stack, no long-running commands needed.

Pricing: Atlassian's pricing structure — Jira: Free plan (up to 10 users), Premium/Enterprise. Cloud pricing depends on the tier. Should explain concisely: free plan up to 10 users, Standard/Premium are paid per-user per-month, and API access is included in all plans (rate limits apply).

Manageability: Yes, easy — simple REST API, JSON responses, official SDKs available (atlassian-python-api, jira package, node's jira.js). Managing via API is easy, but some admin tasks are restricted.

Let me write a simple example: a Python script using Atlassian's REST API (Jira Cloud) that creates a ticket/issue and fetches an issue. Additionally, a health check might be nice too. Keep it light.

I checked the environment: the repo is empty and there are no Atlassian credentials configured (no ATLASSIAN_* / JIRA_* env vars). Atlassian (Jira/Confluence Cloud) does have a real developer workflow — plain REST APIs with official SDKs — so I can proceed. I'll build the example now; it just can't be executed end-to-end until you supply an API token + site URL.

File edits

1 file

Completed
Writtenatlassian_example.pyView changes

/sandbox/repo/atlassian_example.py

Written content · previous contents were not recorded

"""Simple Atlassian Jira Cloud example.
Uses the official `atlassian-python-api` SDK against the hosted REST API.
No local services required — just credentials.
Setup:
pip install atlassian-python-api
export ATLASSIAN_SITE="your-domain.atlassian.net"
export ATLASSIAN_EMAIL="you@example.com"
export ATLASSIAN_API_TOKEN="..." # create at https://id.atlassian.com/manage-profile/security/api-tokens
export JIRA_PROJECT_KEY="DEMO" # an existing project key
Run:
python atlassian_example.py
"""
import os
import sys
from atlassian import Jira
def main() -> None:
site = os.environ.get("ATLASSIAN_SITE")
email = os.environ.get("ATLASSIAN_EMAIL")
token = os.environ.get("ATLASSIAN_API_TOKEN")
project = os.environ.get("JIRA_PROJECT_KEY", "DEMO")
missing = [k for k, v in {
"ATLASSIAN_SITE": site,
"ATLASSIAN_EMAIL": email,
"ATLASSIAN_API_TOKEN": token,
}.items() if not v]
if missing:
sys.exit(f"Missing required env vars: {', '.join(missing)}")
jira = Jira(url=f"https://{site}", username=email, password=token, cloud=True)
# 1. Read: search recent issues in the project (JQL)
print(f"-- Recent issues in {project} --")
result = jira.jql(
f"project = {project} ORDER BY created DESC",
limit=5,
fields=["summary", "status"],
)
for issue in result.get("issues", []):
print(f" {issue['key']}: {issue['fields']['summary']} "
f"[{issue['fields']['status']['name']}]")
# 2. Write: create a task
new_issue = jira.issue_create(
fields={
"project": {"key": project},
"summary": "Created via Atlassian REST API example",
"description": "Hello from atlassian-python-api 👋",
"issuetype": {"name": "Task"},
}
)
key = new_issue["key"]
print(f"\nCreated issue: https://{site}/browse/{key}")
# 3. Update: add a comment, then transition if a 'Done' transition exists
jira.issue_add_comment(key, "Automated comment from the example script.")
transitions = jira.get_issue_transitions(key)
done = next((t for t in transitions if t["name"].lower() == "done"), None)
if done:
jira.issue_transition(key, done["id"])
print(f"Transitioned {key} -> Done")
else:
print(f"No 'Done' transition available for {key} "
f"(available: {[t['name'] for t in transitions]})")
if __name__ == "__main__":
main()
Thinking…

Verify the syntax and install the SDK? Installing the SDK via pip is quick and fine (it's not a long-running service). Let's check whether Python is available, and do a syntax check + import check.

cd /sandbox/repo && python3 -m py_compile atlassian_example.py && echo "syntax OK" && pip install -q atlassian-python-api 2>&1 | tail -2; python3 -c "from atlassian import Jira; print('SDK import OK')"
syntax OK
syntax OK
SDK import OK
Thinking…

Everything's fine. The SDK is installed, and the script compiles. Can't run it without credentials. Okay, so let me answer about pricing and ease of administration, and note the blocker (no credentials).

Done. The example is at /sandbox/repo/atlassian_example.py — it uses the official atlassian-python-api SDK against Jira Cloud's hosted REST API (search via JQL → create an issue → comment → transition to Done). Syntax verified and the SDK installs/imports cleanly. No local services needed.

Blocked on one thing: there are no Atlassian credentials in this environment. 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. Then python3 atlassian_example.py.

How pricing works (Jira Cloud, the product used here):

  • Free tier: up to 10 users, includes full REST API access — enough for this example at $0.
  • Standard: ~$8.15/user/month (billed monthly), 35k users cap.
  • Premium: ~$16/user/month, adds advanced automation/insights, 99.9% uptime SLA.
  • Enterprise: custom pricing for 10+ sites/large scale.
  • API calls themselves aren't billed — they're rate-limited instead. (Confluence/Bitbucket follow the same per-user, free-tier-first model.)

Will it be easy for me to manage? Yes, largely:

  • Clean, well-documented REST APIs with JSON in/out, plus official SDKs for Python, Node, and Go — very scriptable.
  • Most day-to-day work (issues, projects, comments, transitions, Confluence pages) is fully API-driven.
  • Caveats: user/site administration is split across a separate Admin API and the web console (some things like billing and certain org settings are GUI-only), and OAuth 2.0 apps require a bit of one-time setup — though basic-auth API tokens (used here) sidestep that entirely.

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

AX Check by Gauge