Can AI agents automate Clay?

Clay is automatable today through its Public API. This record is the Clay.com go-to-market product (people and company search, enrichment functions, and workflows). It is not Clay.earth. The Public API base used in the authentication examples is https://api.clay.com/public/v0. Every request sends a Clay API key in the clay-api-key header. Create a key under Settings, Account, API keys (beta). That key is separate from CLI sign-in. clay api-keys create shows the key only once. The developer platform is available on all Clay plans, including free and trial. Search result limits depend on the plan: the plugin docs list Free at 50 results per request and 100 per month, and paid self-serve at 500 per request and 1 million per year. Tables are read-only. Structured table queries need Enterprise API table sync. Workflows from the CLI and plugin are in beta. Sequencer launch, pause, and resume stay in the Clay app. The clay CLI is JSON-first, with structured errors and exit codes, and signs in with clay login or clay login --device. It runs on Mac and Linux, and on Windows through WSL. Editor or Admin access is required to authorize a workspace. Clay also hosts an MCP server at https://api.clay.com/v3/mcp. Platform clients register with OAuth 2.0 Dynamic Client Registration, PKCE, and the mcp scope. Access tokens last one hour. A workspace admin must allow the client, including the Unknown toggle for DCR clients. The plugin docs say the Clay plugin installs Clay's skills and the CLI. It does not include an MCP server, so it does not install the MCP for Reps toolset. The product guide describes that MCP surface as 150+ data providers, research agents, and Functions inside ChatGPT, Claude, and Codex. Routine-run webhooks are signed POSTs; delivery is not guaranteed. https://developers.clay.com/llms.txt is a first-party developer index for agents, CLIs, and APIs. https://www.clay.com/llms.txt returned 404. Official language SDKs were 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 a clay-api-key calls the Public API without a browser login, while CLI sign-in and MCP OAuth both need a user consent step and MCP also needs the workspace client policy.

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