Can AI agents automate Hex?

Hex is automatable today through its public API. This record is the Hex analytics workspace (notebooks, published apps, Threads, and workspace admin). It is not Looker, Tableau, or Metabase. For most workspaces the API base is https://app.hex.tech/api/v1. Single-tenant, EU, and HIPAA workspaces replace app.hex.tech with their Hex host. Requests send Authorization Bearer. Personal access tokens are prefixed hxtp_, mirror the user's permissions, require Editor or higher, and must expire. Workspace tokens are prefixed hxtw_, are created by Admins, can be scoped, and can be set never to expire. Core Admin APIs are on Team and Enterprise. The Observability API is Enterprise-only. Users are limited to 60 requests per minute and 25 concurrent kernels across the UI and API runs. The API overview shows JSON request bodies for runs, groups, collections, and data connections. The hex CLI is on Team and Enterprise, requires a personal access token, and an admin must enable API access before tokens can be created. It installs on macOS and Linux, not native Windows. Commands include project, cell, run, thread, user, and connection. Global --json exists. CI can pass a workspace token with hex auth login --token-from-env. The docs say the CLI is actively developed and commands may change. Hex hosts an MCP server at https://app.hex.tech/mcp, with the same custom-host rule. It is in beta, on Team and Enterprise, and needs Explorer or higher. Project editing tools need Editor or higher. Auth is OAuth. MCP access is not turned off by the workspace API-access setting. Knowledge tools search projects and run Threads. Editing tools create SQL, Python, and Markdown cells on the draft notebook and do not modify published app versions. Publishing stays in the Hex app. https://hex.tech/llms.txt is a first-party agent index that points at the MCP server, the public API, and the CLI. https://learn.hex.tech/llms.txt returned 404. The pricing page lists a Free plan and paid plans. A public installable SDK outside the in-product hextoolkit examples was not established. Connector catalogs were not opened. Computer-use viability is unassessed. API, MCP, and CLI each score 7. API is the best path because it is the HTTP contract for published runs and admin, without the CLI's macOS or Linux install or the MCP server's beta label.

Best path today: api · Overall automatability: 7/10