Automation Anywhere OAuth Scopes

OAuth 2.0 searched

Automation Anywhere publishes 2 OAuth 2.0 scopes via the authorization_code and refresh_token flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Automation Anywhere API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

RPAIntelligent AutomationAgentic Process AutomationAI AgentsWorkflow AutomationDocument AutomationProcess OrchestrationEnterprise AutomationBotsA2A

Scopes: 2 Flows: authorization_code, refresh_token Method: searched

Scopes (2)

Scope	Description	Flows
odin:build	Create and modify agents, workflows, smart tables, interfaces and knowledge bases -- the same toolkit surface Autopilot uses.
odin:use	Ask existing agents, run published tools, search a knowledge base and query smart tables.

📄 Provider scope reference: https://ai-kb.automationanywhere.com/ekb-as-mcp/authentication

Source

OAuth Scopes

generated: '2026-09-17'
method: searched
source: >-
  https://api.getodin.ai/.well-known/oauth-authorization-server,
  https://ai-kb.automationanywhere.com/ekb-as-mcp/authentication,
  https://ai-kb.automationanywhere.com/ekb-as-mcp/overview
provider: Automation Anywhere
providerId: automation-anywhere
docs: https://ai-kb.automationanywhere.com/ekb-as-mcp/authentication
summary: >-
  OAuth scopes exist on one Automation Anywhere surface: the Enterprise Knowledge
  MCP servers. The authorization server metadata advertises exactly two, and the
  product deliberately keeps them on separate audiences so a "use" grant cannot
  escalate into a "build" grant. The Automation 360 Control Room API is JWT
  bearer with role-based permissions and has no OAuth scope surface, so none is
  derived for it.
authorization_server: https://api.getodin.ai
metadata_document: well-known/automation-anywhere-ekb-oauth-authorization-server.json
flows:
  - type: authorization_code
    pkce: S256
    dynamic_client_registration: https://api.getodin.ai/oauth/mcp/register
  - type: refresh_token
scopes:
  - name: odin:build
    consent_label: Build in your workspace
    audience: /builder/mcp
    description: >-
      Create and modify agents, workflows, smart tables, interfaces and knowledge
      bases -- the same toolkit surface Autopilot uses.
  - name: odin:use
    consent_label: Use your agents and tools
    audience: /runtime/mcp
    description: >-
      Ask existing agents, run published tools, search a knowledge base and query
      smart tables.
constraints:
  - A token issued for Runtime is rejected by Builder and vice versa (audience binding).
  - The MCP service holds no credentials of its own; every call forwards the user's token or API key.
  - Project membership, roles and knowledge-base Access Tags still apply on top of the scope.
  - Denied consent returns error=access_denied to the client.
control_room:
  oauth_scopes: false
  model: >-
    JWT bearer plus Control Room roles and permissions (for example AAE_Admin,
    AAE_Bot Insight Admin); permissions are granted per role and per folder, not
    per OAuth scope.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/automation-anywhere-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.