FullEnrich API + MCP vs Gojiberry

FullEnrich API + MCP

Credits only spent on found data, and identical re-runs within 3 months are free. Enrichment sources are third-party providers the vendor doesn't name.

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.

FullEnrich API + MCP

1. Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again
2. Expect 30 to 90 seconds a contact. Use the webhook or poll get_enrichment_results
3. Ask for mobiles only when needed. They cost 10 credits against 1 for a work email
4. Call list_industries and list_seniorities before filtering search
5. Use the 0-credit test contacts in the docs to check an integration

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