Enrichment platforms usually price API access above UI access, which quietly punishes automation. Clay charging the same rate removes the reason to avoid the connection. The cap matters more: an agent enriching a list can spend a lot quickly, and a per-rep ceiling is the difference between a surprise and a budget. One consent detail to expect — clients registered through open DCR show as 'Unverified application', which is normal here and not a warning to click past without reading.
Clay's endpoint over their GTM data platform. Tools run scoped to one workspace, chosen at the consent screen rather than inherited from the account.
Clay's enrichment and table work through the platform's API. The endpoint requires authorisation before it will list tools, so the surface here is what Clay documents.
OAuth 2.1 with PKCE and open dynamic client registration, scope mcp. MCP calls consume the workspace's Clay credits at the in-product rate, admins can cap credits per rep, and 500 free credits are granted to start.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen