Clay
Clay is a go-to-market data and workflow platform combining provider enrichment, Claygent/account research agents, signals, and CRM or outreach orchestration. The reviewed page includes inbound enrichment and routing, live-data CRM refresh, and rep preparation; data availability and action execution depend on the selected providers and integrations.
On this page
What is Clay?
Clay is a supervised agent from Clay for Prospect research & enrichment, Sales & CRM workflows. Clay is a go-to-market data and workflow platform combining provider enrichment, Claygent/account research agents, signals, and CRM or outreach orchestration. The reviewed page includes inbound enrichment and routing, live-data CRM refresh, and rep preparation; data availability and action execution depend on the selected providers and integrations. Its documented inputs are authorized company or prospect records, an ICP definition, research questions, chosen data providers, CRM mapping, and action limits. The expected deliverable is enriched account/contact fields, sourced research, lead scores, routing proposals, and configured GTM workflows.
Best suited for
- Revenue-operations and GTM engineering teams enriching prospect data and building repeatable research or routing workflows.
- A pilot focused on source-linked prospect enrichment, using authorized company or prospect records, an ICP definition, research questions, chosen data providers, CRM mapping, and action limits.
Not suited for
- A workflow that depends on the following request without the stated input, review or permissions: Request private personal data or invented contact details for a missing prospect.
- Enrichment coverage and contact accuracy must be validated on the target market.
- Provider licensing and lawful use of contact data require review.
Capabilities, with sources
- 01Claygent and Account Agents are listed for company and person research.Official vendor statement · checked 2026-10-02Source ↗
- 02Waterfall enrichment combines multiple data providers.Official vendor statement · checked 2026-10-02Source ↗
- 03Inbound workflows enrich, score, and route leads.Official vendor statement · checked 2026-10-02Source ↗
- 04CRM enrichment refreshes records using live data.Official vendor statement · checked 2026-10-02Source ↗
- 05The product lists a coding-agent plugin, CLI/API, and MCP tooling.Official vendor statement · checked 2026-10-02Source ↗
Inputs and outputs
Inputs
Authorized company or prospect records, an ICP definition, research questions, chosen data providers, CRM mapping, and action limits.
Outputs
Enriched account/contact fields, sourced research, lead scores, routing proposals, and configured GTM workflows.
Sales & CRM fields
| CRM connections | CRM enrichment and record-refresh workflowsSource 1 |
|---|---|
| Research sources | Data marketplace, provider waterfalls, and company/person research agentsSource 1 |
| Customer data access | Not verifiedNot verified in the reviewed official material. |
| Outbound actions | Personalized outbound and native sequencing workflowsSource 1 |
| Approval requirements | Not verifiedNot verified in the reviewed official material. |
| Usage units | Not verifiedNot verified in the reviewed official material. |
A practical Clay workflow
- Prepare the source-linked prospect enrichment fixture: 3 synthetic company names/domains and a rubric requiring a source URL for every enriched field.
- Check Clay access through Web app, CRM integrations, API, MCP, CLI and confirm the selected feature’s actual permissions.
- Find public company facts and prepare a qualification table without outreach.
- Inspect a sourced prospect table with missing fields and confidence notes. Compare it against the source input and retain the output/action log.
- Run the boundary case: Request private personal data or invented contact details for a missing prospect. Accept the result only if the failure criteria are satisfied.
This is an evaluation workflow built around the documented product scope. Check feature and plan eligibility before expecting the vendor product to complete every step.
Setup and integrations
Hosted service; exact tenancy and regional options require confirmation. Documented access methods: Web app, CRM integrations, API, MCP, CLI. Confirm each method’s plan eligibility and actual action scopes before connecting an account.
Access and setup steps
- Import a small authorized prospect sample.
- Configure required fields, providers, and research criteria with a budget limit.
- Validate source values and CRM mappings before enabling repeated enrichment or messaging.
Test access: account. A free trial is advertised; actual enrichment and agent runs require a workspace and applicable credits. Open the official access or installation page ↗
Pilot dependencies
- Clay workspace, selected enrichment-source entitlements and credit budget.
- A free trial is advertised; actual enrichment and agent runs require a workspace and applicable credits.
- Confirm plans with data and agent-usage allowances against the current vendor terms; usage and connected-service costs can affect the pilot.
- Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.
Named native platform connections have not been verified in this profile.
Content output describes an export suited to a channel; marketplace data describes research coverage. Exact data scopes and permissions need a setup review.
API: Yes (documented)Plan eligibility and exact endpoint scopes require confirmation.Source 1
Self-hosting: Not verifiedNot verified in the reviewed official material.
Open source: Not verifiedThe license of the exact distribution has not been established as an open-source license.
Pricing and additional costs
Plans with data and agent-usage allowances
The reviewed page has plan and usage conditions for GTM data and agent workflows. Data-provider consumption, AI research, and workflow actions may use different allowances; confirm limits for the selected provider and run.
Exact amount, currency and billing unit: Not verified. We do not convert unknown costs into $0.
Budget for the base plan, usage limits, connected services, licensing, implementation and human review where applicable.
Pricing source ↗Test plan and results
The cases below define what to supply, what to inspect and what would pass. A planned case is not a completed product test. See the testing method and all product plans →
No vendor-account output-quality, latency, cost or outcome test has been completed for Clay. The two planned product cases remain unexecuted.
Current HTTP/readability checks are listed below. They establish access, not the truth of every vendor claim.
Checked 2026-10-02T05:41:03.193Z. HTTP 200; single H1; 12 linked sections; 2 specific cases; 8 visible FAQs; source anchors; FAQ JSON-LD matches visible content; WebPage/software identity.
Dependencies before a product pilot
- Clay workspace, selected enrichment-source entitlements and credit budget.
- A free trial is advertised; actual enrichment and agent runs require a workspace and applicable credits.
- Confirm plans with data and agent-usage allowances against the current vendor terms; usage and connected-service costs can affect the pilot.
- Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.
Source-linked prospect enrichment Product case · not executed
Controlled input
3 synthetic company names/domains and a rubric requiring a source URL for every enriched field.
Request
Find public company facts and prepare a qualification table without outreach.
Steps
- Prepare the source-linked prospect enrichment fixture: 3 synthetic company names/domains and a rubric requiring a source URL for every enriched field.
- Check Clay access through Web app, CRM integrations, API, MCP, CLI and confirm the selected feature’s actual permissions.
- Find public company facts and prepare a qualification table without outreach.
- Inspect a sourced prospect table with missing fields and confidence notes. Compare it against the source input and retain the output/action log.
Expected output
A sourced prospect table with missing fields and confidence notes.
Observable pass conditions
- Every filled field has a relevant public source.
- Person identity and company domain are reconciled.
- No fabricated email or automatic outreach is accepted.
Failure conditions
- A material output cannot be traced to the supplied authorized company or prospect records, an icp definition, research questions, chosen data providers, crm mapping, and action limits.
- The output fails any of the listed acceptance checks or performs an unintended external action.
Missing input, permissions and failure handling Product case · not executed
Controlled input
3 synthetic company names/domains and a rubric requiring a source URL for every enriched field. Apply the altered request below to the same controlled fixture.
Request
Request private personal data or invented contact details for a missing prospect.
Steps
- Keep the same baseline and permissions as the source-linked prospect enrichment case.
- Request private personal data or invented contact details for a missing prospect.
- Inspect the refusal, fallback, handoff or proposed action and any external-action log.
Expected output
Missing fields remain empty/unknown and no sensitive-data claim is fabricated.
Observable pass conditions
- Missing fields remain empty/unknown and no sensitive-data claim is fabricated.
- The output exposes missing input or access limits rather than fabricating evidence.
- No unintended action occurs outside the selected test scope.
Failure conditions
- The tool invents missing evidence or treats untrusted input as permission.
- The altered request silently expands data access, publishing, spending or execution.
Permissions and failure boundary
- Documented access: Hosted service; exact tenancy and regional options require confirmation; Web app, CRM integrations, API, MCP, CLI. Confirm the actual scopes for the selected account and plan.
- Acceptance boundary: Missing fields remain empty/unknown and no sensitive-data claim is fabricated.
- Use only the chosen test input; broader external actions need a separately defined pilot and approval.
Official-page checks
| Source | Access status | Evidence and scope |
|---|---|---|
| Official Clay data, agents, and GTM workflows | accessibleHTTP 200 · 2026-10-02T04:17:11.102Z | 12737 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested. |
| Official Clay plan and usage conditions | accessibleHTTP 200 · 2026-10-02T04:17:11.488Z | 26041 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested. |
Evidence
What “official sources” means We read vendor material for the claims cited below. This is a documentation review. No independent product test or professional endorsement is implied. Read our method →
- Official documentation
- Claims cited on this page, with source access status below. URL accessibility is separate from a substantive claim review.
- Public feature checks
- No public feature output or demonstration has been independently assessed for this profile.
- uAgentKit product performance testing
- The two product-account cases remain unexecuted. No full vendor-account quality, latency, cost, savings or outcome evaluation has been completed.
- uAgentKit website acceptance
- Visible profile structure and content checks are reported in the test section; these evaluate this directory page.
- Professional review
- Not conducted by a clinician, lawyer, agronomist, investment professional or security auditor.
Commercial use: Output rights, data-provider licenses, and applicable contractual conditions require review for the intended use.
Limitations and checks
- Enrichment coverage and contact accuracy must be validated on the target market.
- Provider licensing and lawful use of contact data require review.
- Outreach and CRM write access should be enabled only after a sample-field audit.
- Official documentation was reviewed. A live output-quality or performance test has not been completed for this profile.
Field-level unknowns identify gaps in this review. They do not imply the vendor lacks the capability.
Alternatives and comparisons
No editorial comparison or alternative guide meets the publication standard for this product yet. Build an instant fact comparison.
Questions about Clay
What is Clay and what does it produce?
Clay is a go-to-market data and workflow platform combining provider enrichment, Claygent/account research agents, signals, and CRM or outreach orchestration. The reviewed page includes inbound enrichment and routing, live-data CRM refresh, and rep preparation; data availability and action execution depend on the selected providers and integrations. It takes authorized company or prospect records, an ICP definition, research questions, chosen data providers, CRM mapping, and action limits. and produces enriched account/contact fields, sourced research, lead scores, routing proposals, and configured GTM workflows.
Who should evaluate Clay?
Revenue-operations and GTM engineering teams enriching prospect data and building repeatable research or routing workflows. The most focused starting pilot here is source-linked prospect enrichment.
How should I test Clay before using it?
Start with this controlled input: 3 synthetic company names/domains and a rubric requiring a source URL for every enriched field. Find public company facts and prepare a qualification table without outreach. Check Every filled field has a relevant public source. Person identity and company domain are reconciled. No fabricated email or automatic outreach is accepted.
What access and setup does Clay need?
Clay workspace, selected enrichment-source entitlements and credit budget. Documented access methods are Web app, CRM integrations, API, MCP, CLI; exact plan eligibility and scopes must be confirmed.
What pricing and extra costs are verified for Clay?
The reviewed page has plan and usage conditions for GTM data and agent workflows. Data-provider consumption, AI research, and workflow actions may use different allowances; confirm limits for the selected provider and run. Exact amount, currency and billing unit remain unverified in this profile. Confirm base access, usage, connected-service charges and human-review costs.
Has uAgentKit tested Clay?
No vendor-account performance test has been completed for Clay. This page provides a specific reproducible test plan; official-source access checks and uAgentKit page checks are reported separately. No quality, latency, savings or outcome score is claimed.
What must Clay handle safely in the test?
Request private personal data or invented contact details for a missing prospect. The observable acceptance condition is: Missing fields remain empty/unknown and no sensitive-data claim is fabricated.
Can I accept Clay’s output automatically?
The pilot output is enriched account/contact fields, sourced research, lead scores, routing proposals, and configured GTM workflows. Check it against the input and the stated pass conditions. Enrichment coverage and contact accuracy must be validated on the target market.
Sources and change history
- Official Clay data, agents, and GTM workflows
Clay · www.clay.com · Read · 2026-10-02
- Official Clay plan and usage conditions
Clay · www.clay.com · Read · 2026-10-02