{
 "categories": [
  "ci-cd",
  "developer-tools"
 ],
 "deployment": "hybrid",
 "evidence": [
  {
   "date": "2026-10-07",
   "fact": "homepage",
   "note": "Bitrise presents a mobile DevOps platform for iOS and Android. The page lists public, dedicated, and private cloud, plus self-hosted solutions including Bitrise on AWS and Bitrise Runners.",
   "source": "https://bitrise.io/",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "deployment",
   "note": "The homepage offers fully managed public, dedicated, and private cloud together with self-hosted Bitrise on AWS and Bitrise Runners.",
   "source": "https://bitrise.io/",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "license",
   "note": "The homepage says Bitrise offers a free tier with managed cloud build infrastructure, and paid plans add build capacity and advanced features.",
   "source": "https://bitrise.io/",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.api.exists",
   "note": "Bitrise documents an API at https://api.bitrise.io/. Versioned calls use the v0.1 path, for example https://api.bitrise.io/v0.1/me.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.api.kinds[0]",
   "note": "The overview describes HTTP endpoints under /v0.1 for account, app, and build operations.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.api.auth[0]",
   "note": "One supported credential is a user-generated personal access token sent in the Authorization header.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/authenticating-with-the-bitrise-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.api.auth[1]",
   "note": "The other supported credential is a workspace API token, also sent in the Authorization header. Every endpoint except the root URL requires one of the two.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/authenticating-with-the-bitrise-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.api.coverage",
   "note": "Documented areas include apps, builds, artifacts, secrets, code signing, and webhooks. The page says v0.1 is work in progress and has no long-term compatibility promise.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.api.docs",
   "note": "This page is the public Bitrise API overview.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.mcp.first_party",
   "note": "Bitrise documents a remote MCP at mcp.bitrise.io and points to the Bitrise MCP GitHub repository. OAuth signs the user in. Clients without MCP OAuth send a personal access token as Authorization Bearer.",
   "source": "https://docs.bitrise.io/en/bitrise-platform/ai/bitrise-mcp",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.cli.exists",
   "note": "Bitrise documents an official open-source CLI that runs local workflows and calls the Bitrise account API.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/bitrise-cli/bitrise-cli-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.extensibility.webhooks",
   "note": "The API registers incoming git webhooks and creates outgoing webhooks that POST build and pipeline events. App owner or admin role is required.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/incoming-and-outgoing-webhooks",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.data_access.export[0]",
   "note": "The authentication example requests application/json from GET /v0.1/apps.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/authenticating-with-the-bitrise-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "modalities.data_access.import[0]",
   "note": "Creating an outgoing webhook is a JSON POST body with events, url, and optional headers.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/incoming-and-outgoing-webhooks",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "verdict.scores.api",
   "note": "Token auth, JSON, and build, app, and webhook endpoints are usable. The explicit v0.1 work-in-progress warning and missing compatibility promise keep the score at 6.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "verdict.scores.mcp",
   "note": "The vendor README documents app, build, and artifact access, with OAuth or a personal access token.",
   "source": "https://raw.githubusercontent.com/bitrise-io/bitrise-mcp/HEAD/README.md",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "verdict.scores.mcp",
   "note": "The vendor tool list includes invite_member_to_workspace, register_webhook, and tools that publish install pages. Those write actions keep the score at 7.",
   "source": "https://raw.githubusercontent.com/bitrise-io/bitrise-mcp/HEAD/docs/tools.md",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "verdict.scores.mcp",
   "note": "Repository metadata on 2026-10-07 showed pushed_at 2026-10-07T00:23:55Z, SPDX MIT, archived false, and fork false.",
   "source": "https://api.github.com/repos/bitrise-io/bitrise-mcp",
   "tier": "scraped"
  },
  {
   "date": "2026-10-07",
   "fact": "verdict.scores.cli",
   "note": "The official CLI supports bitrise auth, BITRISE_TOKEN, --format json, non-interactive failure when a workspace is ambiguous, and bitrise api for arbitrary v0.1 calls. Account commands still sit on the unfinished API, so the score is 8 rather than 9.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/bitrise-cli/bitrise-cli-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "freshness.watch[0].url",
   "note": "Opened the current Bitrise MCP docs, including mcp.bitrise.io, OAuth, and Bearer personal access tokens.",
   "source": "https://docs.bitrise.io/en/bitrise-platform/ai/bitrise-mcp",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "freshness.watch[1].url",
   "note": "Opened the current CLI overview, including JSON output, token auth, and bitrise api.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/bitrise-cli/bitrise-cli-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "freshness.watch[2].url",
   "note": "Opened the current API overview, including the v0.1 host and the work-in-progress notice.",
   "source": "https://docs.bitrise.io/en/bitrise-ci/api/api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-07",
   "fact": "freshness.watch[3].url",
   "note": "Opened the vendor repository page. The README in that repository documents app, build, and artifact access.",
   "source": "https://github.com/bitrise-io/bitrise-mcp",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-07",
  "volatility": "high",
  "watch": [
   {
    "type": "mcp",
    "url": "https://docs.bitrise.io/en/bitrise-platform/ai/bitrise-mcp"
   },
   {
    "type": "docs",
    "url": "https://docs.bitrise.io/en/bitrise-ci/bitrise-cli/bitrise-cli-overview"
   },
   {
    "type": "docs",
    "url": "https://docs.bitrise.io/en/bitrise-ci/api/api-overview"
   },
   {
    "type": "docs",
    "url": "https://github.com/bitrise-io/bitrise-mcp"
   }
  ]
 },
 "homepage": "https://bitrise.io/",
 "id": "bitrise",
 "license": "freemium",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [
    "personal-access-token",
    "workspace-api-token"
   ],
   "coverage": "partial",
   "docs": "https://docs.bitrise.io/en/bitrise-ci/api/api-overview",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": true
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "json"
   ],
   "import": [
    "json"
   ]
  },
  "extensibility": {
   "scripting": [],
   "webhooks": true
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": true,
   "third_party": [],
   "verdict": "official"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. The official CLI, REST API, webhooks, and hosted MCP cover build and app automation without browser control.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Bitrise",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "circleci"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Bitrise",
 "verdict": {
  "best_path": "cli",
  "scores": {
   "api": 6,
   "cli": 8,
   "computer_use": null,
   "integrations": null,
   "mcp": 7,
   "overall": 8,
   "rpa": null
  },
  "summary": "Bitrise is automatable today through the official CLI. This record is the Bitrise mobile CI/CD platform. The homepage lists public, dedicated, and private cloud plus self-hosted solutions, including Bitrise on AWS and Bitrise Runners. It is not CircleCI, GitHub Actions, or Jenkins. The CLI runs local workflows and account commands. bitrise auth login or BITRISE_TOKEN authenticates. Commands such as bitrise build and bitrise app accept --format json, and bitrise api calls https://api.bitrise.io/v0.1. The REST API accepts a personal access token or a workspace API token in the Authorization header. The vendor marks API v0.1 as work in progress and does not promise long-term compatibility. Incoming and outgoing webhooks are managed through that API. A first-party repository, bitrise-io/bitrise-mcp, is MIT licensed and was pushed on 2026-10-07. The remote server is mcp.bitrise.io. Clients that support OAuth sign in to Bitrise. Other clients send a personal access token as Authorization Bearer. Documented tool groups include apps, builds, artifacts, pipelines, and outgoing webhooks. Some tools invite members, register git webhooks, or publish install pages. No official language SDK was established on the opened API pages. iPaaS catalogs were not opened. Computer-use viability is unassessed. CLI scores 8 and is the best path because it is documented for non-interactive JSON use. MCP scores 7. API scores 6 because v0.1 is explicitly unfinished.\n"
 }
}