Clay vs Gojiberry

Clay

A documented Public API with an OpenAPI spec, llms.txt and plan-capped search, plus a JSON-first CLI released several times a fortnight, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, and the privacy policy dates from 2020.

Gojiberry

A public OpenAPI file with 49 operations, a free masked lead search and a published limit of 100 requests a minute make the API easy to plan against. Keys have no scopes, writes can start LinkedIn outreach from a connected account, and LinkedIn's User Agreement bars the scraping and automated messaging the product depends on.

Clay

1. Fetch GET /search/query-mode/reference before writing a search query
2. Poll routine results until a terminal 200, since 202 means still running
3. Expect HTTP 402 when a plan's search cap is hit, and tell the user the reset date
4. Check GET /credits/balance before large batch runs
5. Ask the user before enabling the plugin's auto-approve hook in a shared workspace

Gojiberry

1. Send Authorization: Bearer <key> to https://mcp.gojiberry.ai. The value must start with the word Bearer or the connection fails
2. Create resources in the order list, source agent, campaign. A source agent with no campaign only finds leads
3. Adding a contact to a list enrols it in the linked campaign, which sends LinkedIn or email messages. Ask the user before list writes
4. Search with POST /v1/directory/leads/search for free, then reveal only the ids you need at 0.5 credit each, up to 100 a request
5. Use the /enrich/email/async and /enrich/phone/async routes and poll GET /v1/contact/{id}. The synchronous routes can take minutes