{ "data": { "a": { "slug": "aura-autopilot", "name": "Aura Autopilot", "vendor": "Ramen", "vendorUrl": "https://www.tryaura.dev/autopilot/", "kind": "mcp", "category": "desktop-automation", "summary": "Aura Autopilot is Ramen's Apache-2.0 game playtester for Unreal Engine 5, Unity 6 and Godot 4. An editor plugin and local agent service play the game, and Claude Code or Codex drive it through a stdio MCP server.", "url": "https://www.anchorterminal.com/tools/aura-autopilot", "markdownUrl": "https://www.anchorterminal.com/tools/aura-autopilot.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/aura-autopilot.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/aura-autopilot.json", "dns": "aura-autopilot.grade.anchorterminal.com", "repo": "https://github.com/ramenvr/autopilot", "license": "Apache-2.0", "transports": [ "stdio" ], "packages": [], "auth": "api-key", "authNotes": "No Ramen account needed with one's own keys. A run needs a TypeSafe API key for the Jev decision model and a model provider key or Claude or ChatGPT plan, or an Aura sign-in in the browser instead. Keys are kept in autopilot.env in the user settings folder.", "pricing": "byo-plan", "pricingNotes": "Free under Apache-2.0. Runs pay for Jev through a TypeSafe key ($0.042 per million input tokens, per our typesafe-jev listing) or an Aura plan from $10 a month billed annually, plus the coding agent's model on the user's key or plan.", "priceSummary": "Your plan", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the repository, the docs or the download page, checked 1 November 2026.", "endpoints": [] }, "toolCount": 14, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://www.tryaura.dev/documentation/autopilot", "capabilities": [ "desktop.control", "desktop.scripting" ], "tags": [ "open-source", "apache-2.0", "local", "mcp", "stdio", "python", "game-testing", "unreal-engine", "unity", "godot", "claude-code-plugin", "pre-1.0" ], "graded": true, "anchor": { "graded": true, "score": 55.5, "grade": "C", "agentReady": false, "rank": 787, "ranked": true, "rankOf": 1251, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 43, "payments": 50, "reliability": 41, "schema": 74, "security": 53, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Apache-2.0, with typed MCP tools carrying read-only hints, a separate process for model-written code and headless exit codes for CI. It is days old with no changelog, needs a TypeSafe Jev key or an Aura account, and by default shares recordings, agent traces and the user's own agent conversation with Ramen unless turned off.", "bestFor": "Agent-driven playtests of Unreal, Unity or Godot games in the editor or in CI", "strengths": [ "Apache-2.0 source for the agent service, the Unreal, Unity and Godot plugins and the Claude Code plugin in one repository", "Fourteen MCP tools with JSON Schema inputs, readOnlyHint on the seven that only read, and a `wait` call for long episodes", "Model-written harness and probe code runs in a child process without API keys; on Linux bubblewrap also removes network and most disk access", "Headless runs from the engine's command line write result.json and exit 0, 1, 2 or 3 for CI", "Release downloads are signed, listed in SHA256SUMS.txt and published as immutable GitHub releases" ], "weaknesses": [ "Run sharing is on by default and sends recordings, screenshots, agent traces with code excerpts and, for MCP runs, the user's Claude Code or Codex conversation to app.tryaura.dev", "Shared run data already sent is never deleted, even by `autopilot uninstall`, and no retention period was found", "Python package 0.1.0 and an Unreal plugin flagged beta, with no changelog in the repository; docs/run-data.md and docs/architecture.md are referenced but not published", "Needs a TypeSafe key for the Jev decision model (early access, per our typesafe-jev listing) or an Aura account, plus a model provider key or plan", "On Windows and macOS, the supported platforms, the sandbox is a plain child process that keeps keys out but not network or disk access" ], "agentNotes": [ "Check the game's project is open in the editor with the Autopilot tab connected before calling start_run; otherwise it answers that the agent service isn't running.", "When a call answers \"still going\", call `wait` until it returns; don't start another tool call meanwhile.", "Pass the user's request in their own words with kind verify, goal or explore, and read the INSTRUCTIONS.md that start_run names in parts with Autopilot's read_file.", "Tell the user that run data is shared by default and how to turn it off (the Settings page, AUTOPILOT_SHARE=0 or -PlaytestShare=0) before the first run.", "Never ask the user to paste a TypeSafe or provider key into the conversation; keys belong in autopilot.env or the Autopilot tab." ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.5 } ], "editorialScores": { "ergonomics": 69, "maintenance": 43, "payments": 50, "reliability": 41, "schema": 74, "security": 53, "transparency": 58 }, "provenanceScore": 52, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "# Download the plugin for your engine and OS from https://www.tryaura.dev/autopilot/ and finish the first-run setup in the editor's Autopilot tab\nautopilot connect claude\nautopilot connect codex", "claudeCode": "claude plugin install autopilot --marketplace ramenvr/autopilot", "config": { "mcpServers": { "autopilot": { "args": [ "mcp" ], "command": "autopilot" } } } }, "letme": { "capability": "https://letme.dev/desktop.control", "tool": "https://letme.dev/aura-autopilot" }, "area": "developer", "unitPrices": [ { "item": "Aura Indie, billed monthly", "unit": "month", "usd": 20, "note": "Includes Autopilot; $10 a month billed annually ($120 a year). Two-week trial, no card" }, { "item": "Aura Pro", "unit": "month", "usd": 40, "note": "Includes Autopilot; $360 a year billed annually" }, { "item": "Aura Ultimate", "unit": "month", "usd": 200, "note": "Includes Autopilot; $1,800 a year billed annually" } ], "provenance": { "legalEntity": "TribeVR Inc. (named in Aura's terms of service and privacy policy), trading as Ramen", "domain": "tryaura.dev", "domainRegistered": "2025-04-29", "endpointOnVendorDomain": null, "terms": "https://www.tryaura.dev/terms-of-service", "privacy": "https://www.tryaura.dev/privacy-policy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "The repository's licence file is Apache 2.0; Aura's terms (25 June 2026) and privacy policy (27 August 2026) are TribeVR Inc.'s and don't mention Autopilot.", "RDAP gives tryaura.dev a registration date of 29 April 2025 and ramenvr.com of 16 February 2019.", "www.tryaura.dev/.well-known/security.txt answered 404. SECURITY.md in the repository asks for GitHub private vulnerability reporting.", "app.tryaura.dev, where shared run data goes and where sign-in happens, disallows ClaudeBot, anthropic-ai and Claude-Web in robots.txt and carries Content-Signal ai-train=no, so nothing on it was read.", "Local software, so there is no status page. Aura's release notes mention Autopilot; the repository has no changelog." ], "score": 52 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/aura-autopilot.json" }, "answer": "Aura Autopilot scores 55.5 (C) on agent readiness against Automation Anywhere's 51 (D), and leads in 4 of 7 scored categories. Automation Anywhere leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "automation-anywhere", "name": "Automation Anywhere", "vendor": "Automation Anywhere", "vendorUrl": "https://www.automationanywhere.com", "kind": "http-api", "category": "desktop-automation", "summary": "Automation Anywhere's Automation 360 is a cloud robotic process automation platform whose Control Room deploys bots that operate desktop and web applications. Outside agents run automations through the Control Room REST API or its MCP inbound endpoint.", "url": "https://www.anchorterminal.com/tools/automation-anywhere", "markdownUrl": "https://www.anchorterminal.com/tools/automation-anywhere.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/automation-anywhere.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/automation-anywhere.json", "dns": "automation-anywhere.grade.anchorterminal.com", "license": "Proprietary service under Automation Anywhere's customer agreement and product-specific terms", "transports": [ "http" ], "remoteUrl": "https://\u003ccontrol-room\u003e/mcp", "packages": [], "auth": "mixed", "authNotes": "Control Room API calls carry either `X-Authorization` with a JSON token from the Authentication API or `Authorization: Bearer` with an OAuth token (v.27 and later), not both. MCP inbound uses OAuth 2.0. An administrator registers OAuth services in Settings, creates an OAuth client (regular web or single-page application) under Manage \u003e OAuth client, and enters the client ID, secret and URLs in the MCP client by hand, adding the client's redirect URL afterwards. Users sign in through the Control Room's OIDC or SAML identity provider, and RBAC decides which automations they can discover and run.", "pricing": "freemium", "pricingNotes": "Community Edition is free with no credit card required, for students, developers and small businesses under the stated limits. Paid Automation 360 Cloud plans have no published prices on automationanywhere.com, and the A+ Tokens and Accelerators terms refer to order forms. Whether Community Edition includes Control Room API or MCP inbound access was not stated (checked 2026-10-14).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Control Room API pages, the MCP inbound pages or the product-specific terms (checked 2026-10-14).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.automationanywhere.com/r/control-room-apis", "llmsTxt": "https://www.automationanywhere.com/llms.txt", "capabilities": [ "desktop.rpa", "desktop.orchestration", "desktop.control" ], "tags": [ "hosted", "official", "oauth", "enterprise", "mcp", "closed-source", "audit-log", "freemium" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 51, "grade": "D", "agentReady": false, "rank": 934, "ranked": true, "rankOf": 1251, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 66, "payments": 15, "reliability": 35, "schema": 55, "security": 64, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-14" }, "negative": 0, "verdict": "The Control Room's /mcp endpoint gives an MCP client three standard tools to discover, run and read automations under RBAC, with each run in the audit log. No API rate limits, error catalogue, SLA or prices were found in public pages, and DiscoverAutomation and RunAutomation need an Enterprise licence with the Process Reasoning Engine in the US or Europe.", "bestFor": "A company already running Automation 360 bots that wants an assistant such as Copilot or Claude to find and start them.", "strengths": [ "MCP inbound at https://\u003ccontrol-room\u003e/mcp with DiscoverAutomation, RunAutomation, GetAutomationResult and custom inbound tools with typed input and output variables", "Each run started through MCP is logged as device acquired, bot sent, deployed and finished in the Control Room audit log", "Written API deprecation policy, with at least two years of support and at least a year's notice before end of life", "Filtering, sorting and pagination documented for list endpoints, with Swagger on every Control Room at /swagger/", "Community Edition is free with no credit card required" ], "weaknesses": [ "No API rate limits, 429 handling or retry guidance found in the public Control Room API pages", "The published response code table lists only generic HTTP statuses, with no error bodies", "DiscoverAutomation and RunAutomation need an Enterprise licence with the Process Reasoning Engine, supported in the US and Europe only", "Cloud prices are not published and no SLA was found in the product-specific terms", "MCP OAuth requires manual client setup in the Control Room and supports only the Manual OAuth type in the client" ], "agentNotes": [ "Call DiscoverAutomation with a specific query such as `Discover automations to create invoice in SAP`. It returns at most nine matches", "Keep the job ID from RunAutomation and poll GetAutomationResult until the status leaves Running/InProgress", "Send either `X-Authorization` with a token from the Authentication API or `Authorization: Bearer` from OAuth, never both in one request", "Match the case of every JSON parameter name. The Control Room API treats names as case-sensitive", "Use the v4 WLM endpoints. Eight v3 WLM endpoints were deprecated in v.43 and end with v.46" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 51 } ], "editorialScores": { "ergonomics": 60, "maintenance": 66, "payments": 15, "reliability": 35, "schema": 55, "security": 64, "transparency": 59 }, "provenanceScore": 88, "checked": { "categories": { "ergonomics": "2026-10-14", "maintenance": "2026-10-14", "payments": "2026-10-14", "reliability": "2026-10-14", "schema": "2026-10-14", "security": "2026-10-14", "transparency": "2026-10-14" }, "last": "2026-10-14", "lastMoved": "2026-10-27", "oldest": "2026-10-14", "stale": false, "staleAfterDays": 90 } }, "letme": { "capability": "https://letme.dev/desktop.rpa", "tool": "https://letme.dev/automation-anywhere" }, "area": "developer", "provenance": { "legalEntity": "Automation Anywhere, Inc.", "domain": "automationanywhere.com", "domainRegistered": "2006-02-15", "domainNote": "Cloud Control Rooms answer on customer subdomains of automationanywhere.digital, for example https://abc-prod-automationanywhere.digital per the MCP docs. www.automationanywhere.com/.well-known/security.txt returns 404.", "endpointOnVendorDomain": true, "terms": "https://www.automationanywhere.com/legal/terms", "privacy": "https://www.automationanywhere.com/legal/privacy", "statusPage": "https://status.automationanywhere.digital", "changelog": "https://docs.automationanywhere.com/r/automation-360/cloud-release-notes", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The terms link is the website terms, last modified 5 November 2018. Customer use is governed by the Intelligent Automation Agreement and product-specific terms at /legal/intelligent-automation-agreement and /legal/product-specific-terms.", "The privacy policy was last modified on 1 April 2026.", "The vulnerability disclosure policy sends reports to disclosure@automationanywhere.com, promises a response within five business days and allows monetary compensation at the company's discretion.", "The status site is a Site24x7 StatusIQ page. Incident entries were readable but their dates were not in the page we received.", "RDAP for automationanywhere.com gives a registration date of 2006-02-15." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/automation-anywhere.json", "live": { "slug": "automation-anywhere", "probe": { "target": "https://\u003ccontrol-room\u003e/mcp", "method": "get", "lastAt": "2026-11-01T05:17:57.857738872Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "DNS lookup failed", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 252, "samples30d": 4498, "days": [ { "date": "2026-10-14", "probes": 166, "ok": 0 }, { "date": "2026-10-15", "probes": 253, "ok": 0 }, { "date": "2026-10-16", "probes": 252, "ok": 0 }, { "date": "2026-10-17", "probes": 253, "ok": 0 }, { "date": "2026-10-18", "probes": 256, "ok": 0 }, { "date": "2026-10-19", "probes": 255, "ok": 0 }, { "date": "2026-10-20", "probes": 252, "ok": 0 }, { "date": "2026-10-21", "probes": 253, "ok": 0 }, { "date": "2026-10-22", "probes": 253, "ok": 0 }, { "date": "2026-10-23", "probes": 248, "ok": 0 }, { "date": "2026-10-24", "probes": 251, "ok": 0 }, { "date": "2026-10-25", "probes": 250, "ok": 0 }, { "date": "2026-10-26", "probes": 252, "ok": 0 }, { "date": "2026-10-27", "probes": 249, "ok": 0 }, { "date": "2026-10-28", "probes": 251, "ok": 0 }, { "date": "2026-10-29", "probes": 249, "ok": 0 }, { "date": "2026-10-30", "probes": 248, "ok": 0 }, { "date": "2026-10-31", "probes": 251, "ok": 0 }, { "date": "2026-11-01", "probes": 56, "ok": 0 } ], "outages": [ { "start": "2026-10-14T08:07:20.705930222Z", "end": "0001-01-01T00:00:00Z", "note": "DNS lookup failed" } ] }, "vendorStatus": { "page": "https://status.automationanywhere.digital", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-01T03:45:05.135286459Z" }, "securityTxt": { "url": "https://automationanywhere.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-31T15:39:46.097496229Z" }, "llmsTxt": { "url": "https://www.automationanywhere.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-31T15:09:58.564688054Z" }, "domain": { "domain": "automationanywhere.com", "registered": "2006-02-15", "source": "https://rdap.verisign.com/com/v1/domain/automationanywhere.com", "checkedAt": "2026-10-25T13:56:39.057101915Z" }, "pages": [ { "url": "https://docs.automationanywhere.com/r/automation-360/cloud-release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-31T06:09:01.038828391Z", "changedAt": "2026-10-31T06:09:01.038828391Z", "fingerprint": "a7ad3702cbe5" }, { "url": "https://www.automationanywhere.com/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-31T06:24:56.760323981Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "44f63a9a8a05" }, { "url": "https://www.automationanywhere.com/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-31T06:25:02.241695343Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4390efd1d56a" } ], "updatedAt": "2026-11-01T05:17:57.857738872Z" } }, "edges": [ { "by": 35, "category": "payments", "leads": "aura-autopilot", "name": "Payments \u0026 pricing", "reasons": { "a": "Open-source software with paid parts around it, so the pricing lines are read for what a run needs. No payment protocol (0). TypeSafe publishes Jev's price per million input tokens and Aura's plans are public, Indie from $10 a month billed annually (20). Autopilot is free under Apache-2.0, and Aura's two-week trial needs no card (20). No Ramen account is needed with one's own keys, but a person installs the editor plugin and gets a TypeSafe key or signs in to Aura in a browser, so 10 rather than the self-hosted rule's 20 (10). 50 in all.", "b": "No x402, MPP or L402 (0). No published prices for paid plans (0). Community Edition is free with no credit card required, but whether it includes API or MCP inbound access was not stated (15 of 20). A person signs up and an administrator creates the OAuth client (0)." }, "scores": { "a": 50, "b": 15 } }, { "by": 23, "category": "maintenance", "leads": "automation-anywhere", "name": "Maintenance \u0026 community", "reasons": { "a": "The launch post is dated 31 October 2026 and Aura 1.2.3 and 1.2.4 of 30 October 2026 ship Autopilot, so the last change is within 30 days (30). GitHub releases couldn't be read, and the two Aura release-note entries aren't three (0). Issue and pull-request replies couldn't be read; the project is days old, with Discord and support email as other channels (5 of 25). Not in the official MCP registry under any namespace (searched for autopilot and ramenvr) (0). Pinned dependencies, per-platform locks in packaging/, CI on three operating systems, conventional-commit checks and code-owner review (8 of 10). 43 in all.", "b": "Cloud build 53728 went out on 7 October 2026 (30). Dated updates on 16 September, 5 October and 7 October 2026 (20). Public release notes and a community forum. Support was not tested (10 of 15). No official SDK and no entry in the official MCP registry (3 of 15). No package to assess (3 of 10)." }, "scores": { "a": 43, "b": 66 } }, { "by": 19, "category": "schema", "leads": "aura-autopilot", "name": "Schema \u0026 documentation", "reasons": { "a": "MCP reading. All 14 tools (start_run, wait, probe, run_harness, snapshot, describe_frames, restart_level, report, frames and five file tools) have JSON Schema inputs, read in autopilot/mcp.py, session.py, external.py and files.py (25). No llms.txt on www.tryaura.dev (404). The agent skill, INSTRUCTIONS.md and KIT.md are Markdown written for the agent, and the README and CONTRIBUTING.md are in the repository (7 of 10). Descriptions say what each tool does and when not to use it (`frames` is for a describer subagent only, `describe_frames` is a fallback), with server instructions (17 of 20). Required fields and an enum on `kind`, but `report.outcome` is a free string with its values only in the description, numeric ranges sit in descriptions rather than the schema, and `probe` takes free-form Python (9 of 15). Prompt examples in the README and skill, plain-language errors in the MCP server and documented exit codes for headless runs (11 of 15). Version numbers and a protocol version, but no public changelog, and GitHub release notes couldn't be read (5 of 15). 74 in all.", "b": "Every Control Room serves Swagger at /swagger/, which needs a Control Room of one's own. The endpoint reference did not render in the pages we could fetch (15 of 25). llms.txt on the website covers marketing pages, and no Markdown docs or docs llms.txt were found (0). Overview pages describe each module's purpose and MCP tool pages say when to use each tool and what fails (10 of 20). MCP inbound variables are typed (String, Number, Boolean, List, Dictionary, DateTime, Record) and marked required or optional (9 of 15). The response code table lists only generic HTTP statuses, with tool troubleshooting notes (6 of 15). Versioned modules v1 to v4, dated deprecations and dated release notes (15)." }, "scores": { "a": 74, "b": 55 } }, { "by": 19, "category": "transparency", "leads": "automation-anywhere", "name": "Transparency \u0026 trust", "reasons": { "a": "Apache-2.0 for the repository, with bundled fonts under the SIL OFL (30). The repository's code docstrings and the Unreal README say what is shared and how it is redacted, but docs/run-data.md, which they cite, isn't published. Aura's terms (TribeVR Inc., 25 June 2026) and privacy policy (27 August 2026) don't mention Autopilot, opt Aura customers into training by default with a perpetual licence to that data, and state no retention period. Runs with one's own keys go to Aura's endpoint under an install token with no account and no terms named. Sent data is never deleted (10 of 30). No deprecation policy; the protocol rule to add optional fields is a contributor guideline (6 of 20). Sharing is disclosed in the setup screen, the README and the plugin docs with three ways to turn it off, but it is on by default, the documentation page doesn't say so, and it includes the user's own agent conversation (12 of 20). 58 in all.", "b": "Closed service with published website terms, an Intelligent Automation Agreement and product-specific terms (15). The privacy policy, modified 1 April 2026, gives retention rules such as up to 90 days for support data. No DPA or subprocessor list was read (16 of 30). A written API deprecation policy with minimum support and notice periods, and dated end-of-life notices (20). Regions are listed on the status site. Subprocessors were not found (8 of 20)." }, "scores": { "a": 55, "b": 74 } }, { "by": 11, "category": "security", "leads": "automation-anywhere", "name": "Security \u0026 auth", "reasons": { "a": "Local-software reading, as tokeneconomizer was read: 30 for what leaves the machine and credentials, 20 approvals and sandboxing, 15 injection, 15 audit, 20 programme. Run sharing is on by default and sends recordings, screenshots, agent traces with the code the agent read and, for MCP runs, the user's own Claude Code or Codex conversation to app.tryaura.dev, after redacting secrets, paths, user and host names and email addresses. Keys sit in plain text in autopilot.env, the file tools never read *.env, and the localhost control endpoint carries a random secret (12). File tools write only the run's folder, notes.md and lib.py, and the user can stop or steer a run from the tab. `autopilot connect codex` sets default_tools_approval_mode to approve, and on Windows and macOS the sandbox is a plain child process without keys but with network and disk (10). sandbox.py names prompt injection from a game's code as the reason for the sandbox, and the frame describer is given only open questions (11). Each run keeps its agent log, harness versions, traces, decisions, report and recording, and the Feed tab shows activity (13). SECURITY.md asks for GitHub private vulnerability reporting; no security.txt on www.tryaura.dev (404), no bounty or certification found, advisories couldn't be read. Releases are signed and immutable, and pull requests need a code owner's approval (7). 53 in all.", "b": "OAuth 2.0 bearer tokens or Authentication API tokens, with users authenticated through OIDC or SAML. No scopes beyond `openid` were documented for MCP (20 of 30). RBAC privileges such as View my bots and Run my bots limit discovery and runs, and missing required variables are prompted from the user (12 of 20). AI Governance logs for MCP inbound exist, with no prompt-injection guidance found (4 of 15). Audit log events for agent connection changes and every MCP-triggered run, plus an Audit API (15). A vulnerability disclosure policy with optional compensation and ISO 27001 and SOC 2 claimed on the website. No security.txt (13 of 20)." }, "scores": { "a": 53, "b": 64 } }, { "by": 9, "category": "ergonomics", "leads": "aura-autopilot", "name": "Agent ergonomics", "reasons": { "a": "MCP reading. 14 tools (15 for 11 to 30), with long descriptions on probe and run_harness and a long INSTRUCTIONS.md the skill says to read in full, with no toolsets (13 of 25). read_file takes offset and limit up to 2,000 lines, list_files returns at most 500, search at most 200 with a glob, frames up to 12 and run_harness takes seconds of play (16 of 20). Errors come back as isError with what to do next (open the editor, update the agent service, call wait), and headless runs exit 0, 1, 2 or 3 (16 of 20). readOnlyHint is set on the seven read tools and destructiveHint false on all, including probe, which the description says can change the game directly. One call runs at a time and a long one answers \"still going\" for `wait` to collect (14 of 20). Two required parameters on start_run with defaults of 10 minutes of exploration and a 30-minute limit; no SDKs, which a playtester doesn't need (10 of 15). 69 in all.", "b": "Three standard MCP tools plus the inbound tools an administrator adds, and DiscoverAutomation returns at most nine matches (22 of 25). Filtering, sorting and pagination documented for list endpoints (20). Generic HTTP statuses with no documented error bodies. GetAutomationResult returns error details for failed runs (9 of 20). No idempotency key or MCP tool annotations found, with 409 for duplicates (4 of 20). Two-step auth before calls, case-sensitive JSON names, and no official SDK found (5 of 15)." }, "scores": { "a": 69, "b": 60 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Ramen", "b": "Automation Anywhere", "name": "Vendor" }, { "a": "no (local only)", "b": "https://\u003ccontrol-room\u003e/mcp", "name": "Hosted endpoint" }, { "a": "stdio", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Your plan", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "Proprietary service under Automation Anywhere's customer agreement and product-specific terms", "name": "Licence" }, { "a": "14", "b": "3", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-07", "name": "Last release" }, { "a": "2026-06-25", "b": "2018-11-05", "name": "Terms last updated" }, { "a": "2026-08-27", "b": "2026-04-01", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "yes", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Aura Autopilot scores 55.5 (C) on agent readiness against Automation Anywhere's 51 (D), and leads in 4 of 7 scored categories. Automation Anywhere leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Aura Autopilot or Automation Anywhere?" }, { "answer": "Aura Autopilot needs an API key. Automation Anywhere takes an API key or an OAuth sign-in.", "question": "Do Aura Autopilot and Automation Anywhere need an API key?" }, { "answer": "Aura Autopilot runs on your own machine, with no hosted endpoint listed. Automation Anywhere has a hosted endpoint at https://\u003ccontrol-room\u003e/mcp.", "question": "Can an agent call Aura Autopilot and Automation Anywhere without installing anything?" }, { "answer": "Aura Autopilot is open source (Apache-2.0). No open-source release is listed for Automation Anywhere.", "question": "Are Aura Autopilot and Automation Anywhere open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 41 against 35", "Schema \u0026 documentation, 74 against 55", "Agent ergonomics, 69 against 60", "Payments \u0026 pricing, 50 against 15" ], "also": [ "Runs on your own machine", "Open source" ], "goodFor": "Agent-driven playtests of Unreal, Unity or Godot games in the editor or in CI", "slug": "aura-autopilot", "watchFor": "Run sharing is on by default and sends recordings, screenshots, agent traces with code excerpts and, for MCP runs, the user's Claude Code or Codex conversation to app.tryaura.dev" }, { "aheadOn": [ "Security \u0026 auth, 64 against 53", "Maintenance \u0026 community, 66 against 43", "Transparency \u0026 trust, 74 against 55" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "A company already running Automation 360 bots that wants an assistant such as Copilot or Claude to find and start them.", "slug": "automation-anywhere", "watchFor": "No API rate limits, 429 handling or retry guidance found in the public Control Room API pages" } ], "history": { "aura-autopilot": null, "automation-anywhere": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 50.9, "fromGrade": "D", "to": 51, "toGrade": "D" } ] }, "job": { "capability": "desktop.control", "name": "Desktop app control" }, "others": [ { "json": "https://www.anchorterminal.com/compare/aura-autopilot-vs-autohotkey.json", "title": "Aura Autopilot vs AutoHotkey", "url": "https://www.anchorterminal.com/compare/aura-autopilot-vs-autohotkey" }, { "json": "https://www.anchorterminal.com/compare/aura-autopilot-vs-autoit.json", "title": "Aura Autopilot vs AutoIt", "url": "https://www.anchorterminal.com/compare/aura-autopilot-vs-autoit" }, { "json": "https://www.anchorterminal.com/compare/aura-autopilot-vs-beam-win.json", "title": "Aura Autopilot vs Beam (beam.win)", "url": "https://www.anchorterminal.com/compare/aura-autopilot-vs-beam-win" }, { "json": "https://www.anchorterminal.com/compare/aura-autopilot-vs-robocorp.json", "title": "Aura Autopilot vs Robocorp", "url": "https://www.anchorterminal.com/compare/aura-autopilot-vs-robocorp" }, { "json": "https://www.anchorterminal.com/compare/aura-autopilot-vs-uipath.json", "title": "Aura Autopilot vs UiPath", "url": "https://www.anchorterminal.com/compare/aura-autopilot-vs-uipath" }, { "json": "https://www.anchorterminal.com/compare/autohotkey-vs-automation-anywhere.json", "title": "AutoHotkey vs Automation Anywhere", "url": "https://www.anchorterminal.com/compare/autohotkey-vs-automation-anywhere" }, { "json": "https://www.anchorterminal.com/compare/autoit-vs-automation-anywhere.json", "title": "AutoIt vs Automation Anywhere", "url": "https://www.anchorterminal.com/compare/autoit-vs-automation-anywhere" }, { "json": "https://www.anchorterminal.com/compare/automation-anywhere-vs-beam-win.json", "title": "Automation Anywhere vs Beam (beam.win)", "url": "https://www.anchorterminal.com/compare/automation-anywhere-vs-beam-win" }, { "json": "https://www.anchorterminal.com/compare/automation-anywhere-vs-robocorp.json", "title": "Automation Anywhere vs Robocorp", "url": "https://www.anchorterminal.com/compare/automation-anywhere-vs-robocorp" }, { "json": "https://www.anchorterminal.com/compare/automation-anywhere-vs-robot-framework.json", "title": "Automation Anywhere vs Robot Framework", "url": "https://www.anchorterminal.com/compare/automation-anywhere-vs-robot-framework" }, { "json": "https://www.anchorterminal.com/compare/automation-anywhere-vs-uipath.json", "title": "Automation Anywhere vs UiPath", "url": "https://www.anchorterminal.com/compare/automation-anywhere-vs-uipath" }, { "json": "https://www.anchorterminal.com/compare/aura-autopilot-vs-robot-framework.json", "title": "Aura Autopilot vs Robot Framework", "url": "https://www.anchorterminal.com/compare/aura-autopilot-vs-robot-framework" } ], "panel": null, "scores": [ { "aura-autopilot": 41, "automation-anywhere": 35, "by": 6, "edge": "aura-autopilot", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aura-autopilot": 74, "automation-anywhere": 55, "by": 19, "edge": "aura-autopilot", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "aura-autopilot": 69, "automation-anywhere": 60, "by": 9, "edge": "aura-autopilot", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "aura-autopilot": 53, "automation-anywhere": 64, "by": 11, "edge": "automation-anywhere", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "aura-autopilot": 50, "automation-anywhere": 15, "by": 35, "edge": "aura-autopilot", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "aura-autopilot": 43, "automation-anywhere": 66, "by": 23, "edge": "automation-anywhere", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "aura-autopilot": 55, "automation-anywhere": 74, "by": 19, "edge": "automation-anywhere", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Aura Autopilot scores 55.5 (C) on agent readiness against Automation Anywhere's 51 (D), and leads in 4 of 7 scored categories. Automation Anywhere leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do desktop app control.", "tasks": null, "tutorials": [], "verdicts": { "aura-autopilot": "Apache-2.0, with typed MCP tools carrying read-only hints, a separate process for model-written code and headless exit codes for CI. It is days old with no changelog, needs a TypeSafe Jev key or an Aura account, and by default shares recordings, agent traces and the user's own agent conversation with Ramen unless turned off.", "automation-anywhere": "The Control Room's /mcp endpoint gives an MCP client three standard tools to discover, run and read automations under RBAC, with each run in the audit log. No API rate limits, error catalogue, SLA or prices were found in public pages, and DiscoverAutomation and RunAutomation need an Enterprise licence with the Process Reasoning Engine in the US or Europe." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/aura-autopilot-vs-automation-anywhere", "json": "https://www.anchorterminal.com/compare/aura-autopilot-vs-automation-anywhere.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aura-autopilot-vs-automation-anywhere.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/aura-autopilot-vs-automation-anywhere.min.md" }, "markdown": "Aura Autopilot scores 55.5 (C) on agent readiness against Automation Anywhere's 51 (D), and leads in 4 of 7 scored categories. Automation Anywhere leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do desktop app control.\n\n- Aura Autopilot: grade C, 55.5/100, rank #787 of 1251. Markdown https://www.anchorterminal.com/tools/aura-autopilot.md · JSON https://www.anchorterminal.com/api/v1/tools/aura-autopilot.json\n- Automation Anywhere: grade D, 51/100, rank #934 of 1251. Markdown https://www.anchorterminal.com/tools/automation-anywhere.md · JSON https://www.anchorterminal.com/api/v1/tools/automation-anywhere.json\n- Best desktop and mobile app automation for AI agents: https://www.anchorterminal.com/best/desktop-automation/index.md\n- All 27 desktop comparisons: https://www.anchorterminal.com/compare/desktop-automation/index.md\n\n## Which one, for what\n\n### Aura Autopilot (C)\n\nGood for: Agent-driven playtests of Unreal, Unity or Godot games in the editor or in CI\n\nAhead on:\n- Reliability, 41 against 35\n- Schema \u0026 documentation, 74 against 55\n- Agent ergonomics, 69 against 60\n- Payments \u0026 pricing, 50 against 15\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\n\nWatch for: Run sharing is on by default and sends recordings, screenshots, agent traces with code excerpts and, for MCP runs, the user's Claude Code or Codex conversation to app.tryaura.dev\n\n### Automation Anywhere (D)\n\nGood for: A company already running Automation 360 bots that wants an assistant such as Copilot or Claude to find and start them.\n\nAhead on:\n- Security \u0026 auth, 64 against 53\n- Maintenance \u0026 community, 66 against 43\n- Transparency \u0026 trust, 74 against 55\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No API rate limits, 429 handling or retry guidance found in the public Control Room API pages\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Aura Autopilot +35\n\n- Aura Autopilot (50): Open-source software with paid parts around it, so the pricing lines are read for what a run needs. No payment protocol (0). TypeSafe publishes Jev's price per million input tokens and Aura's plans are public, Indie from $10 a month billed annually (20). Autopilot is free under Apache-2.0, and Aura's two-week trial needs no card (20). No Ramen account is needed with one's own keys, but a person installs the editor plugin and gets a TypeSafe key or signs in to Aura in a browser, so 10 rather than the self-hosted rule's 20 (10). 50 in all.\n- Automation Anywhere (15): No x402, MPP or L402 (0). No published prices for paid plans (0). Community Edition is free with no credit card required, but whether it includes API or MCP inbound access was not stated (15 of 20). A person signs up and an administrator creates the OAuth client (0).\n\n### Maintenance \u0026 community: Automation Anywhere +23\n\n- Aura Autopilot (43): The launch post is dated 31 October 2026 and Aura 1.2.3 and 1.2.4 of 30 October 2026 ship Autopilot, so the last change is within 30 days (30). GitHub releases couldn't be read, and the two Aura release-note entries aren't three (0). Issue and pull-request replies couldn't be read; the project is days old, with Discord and support email as other channels (5 of 25). Not in the official MCP registry under any namespace (searched for autopilot and ramenvr) (0). Pinned dependencies, per-platform locks in packaging/, CI on three operating systems, conventional-commit checks and code-owner review (8 of 10). 43 in all.\n- Automation Anywhere (66): Cloud build 53728 went out on 7 October 2026 (30). Dated updates on 16 September, 5 October and 7 October 2026 (20). Public release notes and a community forum. Support was not tested (10 of 15). No official SDK and no entry in the official MCP registry (3 of 15). No package to assess (3 of 10).\n\n### Schema \u0026 documentation: Aura Autopilot +19\n\n- Aura Autopilot (74): MCP reading. All 14 tools (start_run, wait, probe, run_harness, snapshot, describe_frames, restart_level, report, frames and five file tools) have JSON Schema inputs, read in autopilot/mcp.py, session.py, external.py and files.py (25). No llms.txt on www.tryaura.dev (404). The agent skill, INSTRUCTIONS.md and KIT.md are Markdown written for the agent, and the README and CONTRIBUTING.md are in the repository (7 of 10). Descriptions say what each tool does and when not to use it (`frames` is for a describer subagent only, `describe_frames` is a fallback), with server instructions (17 of 20). Required fields and an enum on `kind`, but `report.outcome` is a free string with its values only in the description, numeric ranges sit in descriptions rather than the schema, and `probe` takes free-form Python (9 of 15). Prompt examples in the README and skill, plain-language errors in the MCP server and documented exit codes for headless runs (11 of 15). Version numbers and a protocol version, but no public changelog, and GitHub release notes couldn't be read (5 of 15). 74 in all.\n- Automation Anywhere (55): Every Control Room serves Swagger at /swagger/, which needs a Control Room of one's own. The endpoint reference did not render in the pages we could fetch (15 of 25). llms.txt on the website covers marketing pages, and no Markdown docs or docs llms.txt were found (0). Overview pages describe each module's purpose and MCP tool pages say when to use each tool and what fails (10 of 20). MCP inbound variables are typed (String, Number, Boolean, List, Dictionary, DateTime, Record) and marked required or optional (9 of 15). The response code table lists only generic HTTP statuses, with tool troubleshooting notes (6 of 15). Versioned modules v1 to v4, dated deprecations and dated release notes (15).\n\n### Transparency \u0026 trust: Automation Anywhere +19\n\n- Aura Autopilot (55): Apache-2.0 for the repository, with bundled fonts under the SIL OFL (30). The repository's code docstrings and the Unreal README say what is shared and how it is redacted, but docs/run-data.md, which they cite, isn't published. Aura's terms (TribeVR Inc., 25 June 2026) and privacy policy (27 August 2026) don't mention Autopilot, opt Aura customers into training by default with a perpetual licence to that data, and state no retention period. Runs with one's own keys go to Aura's endpoint under an install token with no account and no terms named. Sent data is never deleted (10 of 30). No deprecation policy; the protocol rule to add optional fields is a contributor guideline (6 of 20). Sharing is disclosed in the setup screen, the README and the plugin docs with three ways to turn it off, but it is on by default, the documentation page doesn't say so, and it includes the user's own agent conversation (12 of 20). 58 in all.\n- Automation Anywhere (74): Closed service with published website terms, an Intelligent Automation Agreement and product-specific terms (15). The privacy policy, modified 1 April 2026, gives retention rules such as up to 90 days for support data. No DPA or subprocessor list was read (16 of 30). A written API deprecation policy with minimum support and notice periods, and dated end-of-life notices (20). Regions are listed on the status site. Subprocessors were not found (8 of 20).\n\n### Security \u0026 auth: Automation Anywhere +11\n\n- Aura Autopilot (53): Local-software reading, as tokeneconomizer was read: 30 for what leaves the machine and credentials, 20 approvals and sandboxing, 15 injection, 15 audit, 20 programme. Run sharing is on by default and sends recordings, screenshots, agent traces with the code the agent read and, for MCP runs, the user's own Claude Code or Codex conversation to app.tryaura.dev, after redacting secrets, paths, user and host names and email addresses. Keys sit in plain text in autopilot.env, the file tools never read *.env, and the localhost control endpoint carries a random secret (12). File tools write only the run's folder, notes.md and lib.py, and the user can stop or steer a run from the tab. `autopilot connect codex` sets default_tools_approval_mode to approve, and on Windows and macOS the sandbox is a plain child process without keys but with network and disk (10). sandbox.py names prompt injection from a game's code as the reason for the sandbox, and the frame describer is given only open questions (11). Each run keeps its agent log, harness versions, traces, decisions, report and recording, and the Feed tab shows activity (13). SECURITY.md asks for GitHub private vulnerability reporting; no security.txt on www.tryaura.dev (404), no bounty or certification found, advisories couldn't be read. Releases are signed and immutable, and pull requests need a code owner's approval (7). 53 in all.\n- Automation Anywhere (64): OAuth 2.0 bearer tokens or Authentication API tokens, with users authenticated through OIDC or SAML. No scopes beyond `openid` were documented for MCP (20 of 30). RBAC privileges such as View my bots and Run my bots limit discovery and runs, and missing required variables are prompted from the user (12 of 20). AI Governance logs for MCP inbound exist, with no prompt-injection guidance found (4 of 15). Audit log events for agent connection changes and every MCP-triggered run, plus an Audit API (15). A vulnerability disclosure policy with optional compensation and ISO 27001 and SOC 2 claimed on the website. No security.txt (13 of 20).\n\n### Agent ergonomics: Aura Autopilot +9\n\n- Aura Autopilot (69): MCP reading. 14 tools (15 for 11 to 30), with long descriptions on probe and run_harness and a long INSTRUCTIONS.md the skill says to read in full, with no toolsets (13 of 25). read_file takes offset and limit up to 2,000 lines, list_files returns at most 500, search at most 200 with a glob, frames up to 12 and run_harness takes seconds of play (16 of 20). Errors come back as isError with what to do next (open the editor, update the agent service, call wait), and headless runs exit 0, 1, 2 or 3 (16 of 20). readOnlyHint is set on the seven read tools and destructiveHint false on all, including probe, which the description says can change the game directly. One call runs at a time and a long one answers \"still going\" for `wait` to collect (14 of 20). Two required parameters on start_run with defaults of 10 minutes of exploration and a 30-minute limit; no SDKs, which a playtester doesn't need (10 of 15). 69 in all.\n- Automation Anywhere (60): Three standard MCP tools plus the inbound tools an administrator adds, and DiscoverAutomation returns at most nine matches (22 of 25). Filtering, sorting and pagination documented for list endpoints (20). Generic HTTP statuses with no documented error bodies. GetAutomationResult returns error details for failed runs (9 of 20). No idempotency key or MCP tool annotations found, with 409 for duplicates (4 of 20). Two-step auth before calls, case-sensitive JSON names, and no official SDK found (5 of 15).\n\n## Score by category\n\n| Category | Weight | Aura Autopilot | Automation Anywhere | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 41 | 35 | Aura Autopilot +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 55 | Aura Autopilot +19 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 60 | Aura Autopilot +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 53 | 64 | Automation Anywhere +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 15 | Aura Autopilot +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 43 | 66 | Automation Anywhere +23 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 55 | 74 | Automation Anywhere +19 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **55.5 · C** | **51 · D** | |\n\n## Facts side by side\n\n| Fact | Aura Autopilot | Automation Anywhere |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Ramen | Automation Anywhere |\n| Hosted endpoint | no (local only) | `https://\u003ccontrol-room\u003e/mcp` |\n| Transports | stdio | HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Your plan | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 | Proprietary service under Automation Anywhere's customer agreement and product-specific terms |\n| Tools exposed | 14 | 3 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-10-07 |\n| Terms last updated | 2026-06-25 | 2018-11-05 |\n| Privacy policy last updated | 2026-08-27 | 2026-04-01 |\n| Customer content may train models | yes, with an opt-out | yes |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n\n## How the scores have moved\n\n### Aura Autopilot\n\nNo score change since it was listed.\n\n### Automation Anywhere\n\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**Aura Autopilot.** Apache-2.0, with typed MCP tools carrying read-only hints, a separate process for model-written code and headless exit codes for CI. It is days old with no changelog, needs a TypeSafe Jev key or an Aura account, and by default shares recordings, agent traces and the user's own agent conversation with Ramen unless turned off.\n\n**Automation Anywhere.** The Control Room's /mcp endpoint gives an MCP client three standard tools to discover, run and read automations under RBAC, with each run in the audit log. No API rate limits, error catalogue, SLA or prices were found in public pages, and DiscoverAutomation and RunAutomation need an Enterprise licence with the Process Reasoning Engine in the US or Europe.\n\n## Before you call either\n\n### Aura Autopilot\n\n1. Check the game's project is open in the editor with the Autopilot tab connected before calling start_run; otherwise it answers that the agent service isn't running.\n2. When a call answers \"still going\", call `wait` until it returns; don't start another tool call meanwhile.\n3. Pass the user's request in their own words with kind verify, goal or explore, and read the INSTRUCTIONS.md that start_run names in parts with Autopilot's read_file.\n4. Tell the user that run data is shared by default and how to turn it off (the Settings page, AUTOPILOT_SHARE=0 or -PlaytestShare=0) before the first run.\n5. Never ask the user to paste a TypeSafe or provider key into the conversation; keys belong in autopilot.env or the Autopilot tab.\n\n### Automation Anywhere\n\n1. Call DiscoverAutomation with a specific query such as `Discover automations to create invoice in SAP`. It returns at most nine matches\n2. Keep the job ID from RunAutomation and poll GetAutomationResult until the status leaves Running/InProgress\n3. Send either `X-Authorization` with a token from the Authentication API or `Authorization: Bearer` from OAuth, never both in one request\n4. Match the case of every JSON parameter name. The Control Room API treats names as case-sensitive\n5. Use the v4 WLM endpoints. Eight v3 WLM endpoints were deprecated in v.43 and end with v.46\n\n## Questions\n\n### Which is better for AI agents, Aura Autopilot or Automation Anywhere?\n\nAura Autopilot scores 55.5 (C) on agent readiness against Automation Anywhere's 51 (D), and leads in 4 of 7 scored categories. Automation Anywhere leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Aura Autopilot and Automation Anywhere need an API key?\n\nAura Autopilot needs an API key. Automation Anywhere takes an API key or an OAuth sign-in.\n\n### Can an agent call Aura Autopilot and Automation Anywhere without installing anything?\n\nAura Autopilot runs on your own machine, with no hosted endpoint listed. Automation Anywhere has a hosted endpoint at https://\u003ccontrol-room\u003e/mcp.\n\n### Are Aura Autopilot and Automation Anywhere open source?\n\nAura Autopilot is open source (Apache-2.0). No open-source release is listed for Automation Anywhere.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aura-autopilot-vs-automation-anywhere.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aura-autopilot-vs-automation-anywhere.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aura-autopilot\", \"b\": \"automation-anywhere\"}`. From a terminal: `anchor compare aura-autopilot automation-anywhere`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/aura-autopilot.json and https://www.anchorterminal.com/api/v1/tools/automation-anywhere.json\n\n## Other comparisons with Aura Autopilot or Automation Anywhere\n\n- [Aura Autopilot vs AutoHotkey](https://www.anchorterminal.com/compare/aura-autopilot-vs-autohotkey.md)\n- [Aura Autopilot vs AutoIt](https://www.anchorterminal.com/compare/aura-autopilot-vs-autoit.md)\n- [Aura Autopilot vs Beam (beam.win)](https://www.anchorterminal.com/compare/aura-autopilot-vs-beam-win.md)\n- [Aura Autopilot vs Robocorp](https://www.anchorterminal.com/compare/aura-autopilot-vs-robocorp.md)\n- [Aura Autopilot vs UiPath](https://www.anchorterminal.com/compare/aura-autopilot-vs-uipath.md)\n- [AutoHotkey vs Automation Anywhere](https://www.anchorterminal.com/compare/autohotkey-vs-automation-anywhere.md)\n- [AutoIt vs Automation Anywhere](https://www.anchorterminal.com/compare/autoit-vs-automation-anywhere.md)\n- [Automation Anywhere vs Beam (beam.win)](https://www.anchorterminal.com/compare/automation-anywhere-vs-beam-win.md)\n- [Automation Anywhere vs Robocorp](https://www.anchorterminal.com/compare/automation-anywhere-vs-robocorp.md)\n- [Automation Anywhere vs Robot Framework](https://www.anchorterminal.com/compare/automation-anywhere-vs-robot-framework.md)\n- [Automation Anywhere vs UiPath](https://www.anchorterminal.com/compare/automation-anywhere-vs-uipath.md)\n- [Aura Autopilot vs Robot Framework](https://www.anchorterminal.com/compare/aura-autopilot-vs-robot-framework.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-01", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Aura Autopilot vs Automation Anywhere", "url": "" } ], "description": "Aura Autopilot scores 55.5 (C) to Automation Anywhere's 51 (D) for desktop app control. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Aura Autopilot C 55.5", "Automation Anywhere D 51", "scores" ], "h1": "Aura Autopilot vs Automation Anywhere", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/aura-autopilot-vs-automation-anywhere", "published": "2026-10-01", "section": "tools", "title": "Aura Autopilot vs Automation Anywhere for AI agents (2026)", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/aura-autopilot-vs-automation-anywhere" }, "tokens": { "markdown": 4700, "slim": 2880 }, "version": 1 }