Prospect Data You Can Wire Into Your Own Pipeline

Yes. REST API v2 sits at https://api.cleanlist.ai/api/v2 with around 30 endpoints (workspace and identity, search, lead lists, enrichment, skills, sync and export) and a published OpenAPI 3.x spec. You mint a clapi_ Bearer token from the dashboard with no approval queue and no sales call, and every endpoint checks one of 14 OAuth scopes, so a read-only key cannot start a paid enrichment. Access needs Pro at $89 a seat a month or above, or an AppSumo Tier 5+ license. Call GET /whoami first to confirm the identity, scopes, plan and organization a key resolves to.

Clu allows 60 requests per minute per organization and 30 per API key. People Search has a separate hard cap of 60 searches per UTC day per key, which is the limit most agent workloads hit first, so plan pagination and caching around it. Going over any limit returns HTTP 429 with a Retry-After header and a rate_limited error body. AppSumo lifetime licenses without a paid plan are held to 30 requests per minute per organization.

No. The v2 API is poll-based. Asynchronous enrichment returns a workflow_id that you poll until the status is terminal, with exponential backoff as the recommended pattern. Synchronous operations (company enrichment, search, CRM sync, exports) answer in the same request. A scheduled job that enriches a list therefore needs a second scheduled step that polls for completion. Older tutorials that describe receiving a webhook are documenting the frozen v1 surface.

Yes, through a generic HTTP node. There is no native Clu app in the n8n, Make or Zapier directories. Point an HTTP step at https://api.cleanlist.ai/api/v2, send your clapi_ Bearer token, and handle completion in a second scheduled step, since v2 has no webhooks. For HubSpot and Salesforce you can often skip the automation platform: POST /sync/crm pushes leads directly at 0.2 credits per lead, and POST /sync/sequencer pushes to Lemlist. Clu's own Sequences send email from your own inbox, with call tasks, inside the app, and there is no dialer. For any other tool, it hands over the record.

Put every paid bulk job behind a signed quote. Call POST /credits/estimate, get back an HMAC-signed quote_id with a 5 minute TTL, and pass that quote_id on the request that spends. The run cannot exceed its quote, and a stalled agent just lets the quote expire. Records the waterfall cannot resolve settle their reserved credits back. The MCP server enforces the same quote against the same wallet, so the cap holds whether the caller is your code or Claude.

No. The REST API takes structured filters (job title, seniority, department, headcount, industry, location and similar), and there is no natural-language search endpoint. Natural language lives one layer up, in Clu and in the MCP server, where the model turns your instruction into the same filter payload a script would send. For plain-English list requests, connect the MCP server. For a script, build the filter object against the published OpenAPI spec.

About 10,000 credits for verified emails, at 1 credit each. On Pro that's the 10,000-credit level at $449 a month, or on Starter or Pro a one-off 10,000-credit top-up for $449. Adding a phone number takes each record to 11 credits, or 110,000 for the file, so run the phone pass only on the accounts you will call. Records the waterfall cannot resolve settle their reserved credits back, so real spend usually lands below the worst case. Quote the job with POST /credits/estimate first and the returned quote_id caps the run.

Clu people and company search runs on firmographic and role attributes (job title, seniority, department, headcount, industry, location, funding stage and similar), 20+ filters in total. There are no intent-data, technographic or revenue-range filters, and no job-change detection or alerting. If your scoring model needs one of those signals, source it separately and join on the company domain, or filter first and let a skill (5 credits per lead) research only the records that survive.