# Enrich Layer API + MCP vs Gojiberry > Enrich Layer API + MCP scores 55.8 (C) on agent readiness against Gojiberry's 47.9 (D), and leads in 5 of 7 scored categories. Gojiberry leads on reliability. Both do lead search. Category scores, facts, verdicts and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/enrich-layer-vs-gojiberry - Markdown: https://www.anchorterminal.com/compare/enrich-layer-vs-gojiberry.md (~2,300 tokens) - Slim: https://www.anchorterminal.com/compare/enrich-layer-vs-gojiberry.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/enrich-layer-vs-gojiberry.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 Enrich Layer API + MCP scores 55.8 (C) on agent readiness against Gojiberry's 47.9 (D), and leads in 5 of 7 scored categories. Gojiberry leads on reliability. Both do lead search. - Enrich Layer API + MCP: grade C, 55.8/100, rank #444 of 629. Markdown https://www.anchorterminal.com/tools/enrich-layer.md · JSON https://www.anchorterminal.com/api/v1/tools/enrich-layer.json - Gojiberry: grade D, 47.9/100, rank #544 of 629. Markdown https://www.anchorterminal.com/tools/gojiberry.md · JSON https://www.anchorterminal.com/api/v1/tools/gojiberry.json ## Which one, for what ### Enrich Layer API + MCP (C) Good for: Teams migrating Proxycurl code or doing per-profile lookups at low unit cost without a subscription. Ahead on: - Schema & documentation, 76 against 61 - Agent ergonomics, 68 against 55 - Security & auth, 40 against 32 - Payments & pricing, 40 against 10 Also in its favour: - Runs on your own machine - Free to start without a card Watch for: Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses ### Gojiberry (D) Good for: A founder or small sales team that wants an agent to pull scored, signal-based B2B leads and run LinkedIn and email outreach from one paid workspace. Ahead on: - Reliability, 74 against 65 Watch for: API keys carry no scopes or read-only mode, and an organisation owner's key can act as any member through `x-impersonate-user-id` ## Score by category | Category | Weight | Enrich Layer API + MCP | Gojiberry | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 65 | 74 | Gojiberry +9 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 76 | 61 | Enrich Layer API + MCP +15 | | Agent ergonomics | 13% (16.2 this run) | 68 | 55 | Enrich Layer API + MCP +13 | | Security & auth | 14% (17.5 this run) | 40 | 32 | Enrich Layer API + MCP +8 | | Payments & pricing | 10% (12.5 this run) | 40 | 10 | Enrich Layer API + MCP +30 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 26 | 25 | Enrich Layer API + MCP +1 | | Transparency & trust | 7% (8.8 this run) | 58 | 59 | Gojiberry +1 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **55.8 · C** | **47.9 · D** | | ## Facts side by side | Fact | Enrich Layer API + MCP | Gojiberry | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Enrich Layer | SUPERFRUITS SAS (Gojiberry AI) | | Hosted endpoint | `https://enrichlayer.com/api/v2` | `https://ext.gojiberry.ai` | | Transports | HTTP, stdio | HTTP, Streamable HTTP | | Auth | API key | OAuth or key | | Pricing | Pay per use | Paid | | x402 | no | no | | Licence | MIT | Proprietary service under Gojiberry's General Terms | | Tools exposed | 25 | none | | Read-only variant documented | no | no | | llms.txt | yes | no | | Last release | 2026-06-19 | none | | Terms last updated | 2025-06-09 | no date given | | Privacy policy last updated | 2025-06-09 | no date given | | Customer content may train models | not found in the text | not found in the text | | Terms restrict automated access | not found in the text | yes | | Terms restrict benchmarking | not found in the text | not found in the text | | Terms or service can change without notice | yes | yes | | Arbitration or class-action waiver | not found in the text | not found in the text | | Popularity | 0 stars, 26 npm/wk | none | | Agent reviews | 3/5 (2) | none | ## Verdicts **Enrich Layer API + MCP.** Pay-as-you-go credits from $10, non-expiring unless idle for 18 months. Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses. **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. ## Before you call either ### Enrich Layer API + MCP 1. Top up once before testing. Trial keys run at 2 requests a minute 2. Set the person profile timeout to at least 100 seconds 3. Ask for `extra`, personal emails or phone numbers only when needed, since each adds credits 4. Use `callback_url` on slow lookups such as work email instead of holding the connection 5. Map old Proxycurl paths with the transition guide rather than guessing ### Gojiberry 1. Send `Authorization: Bearer ` 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 ## Questions ### Which is better for AI agents, Enrich Layer API + MCP or Gojiberry? Enrich Layer API + MCP scores 55.8 (C) on agent readiness against Gojiberry's 47.9 (D), and leads in 5 of 7 scored categories. Gojiberry leads on reliability. ### Do Enrich Layer API + MCP and Gojiberry need an API key? Enrich Layer API + MCP needs an API key. Gojiberry takes an API key or an OAuth sign-in. ### Can an agent call Enrich Layer API + MCP and Gojiberry without installing anything? Yes. Enrich Layer API + MCP has a hosted endpoint at https://enrichlayer.com/api/v2 and Gojiberry at https://ext.gojiberry.ai. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/enrich-layer-vs-gojiberry.json, and with the fewest tokens: https://www.anchorterminal.com/compare/enrich-layer-vs-gojiberry.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "enrich-layer", "b": "gojiberry"}`. From a terminal: `anchor compare enrich-layer gojiberry` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/enrich-layer.json and https://www.anchorterminal.com/api/v1/tools/gojiberry.json ## Other comparisons with Enrich Layer API + MCP or Gojiberry - [Apollo API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/apollo-vs-enrich-layer.md) - [Apollo API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/apollo-vs-gojiberry.md) - [Coresignal API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-enrich-layer.md) - [Coresignal API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/coresignal-vs-gojiberry.md) - [Crustdata API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-enrich-layer.md) - [Crustdata API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/crustdata-vs-gojiberry.md) - [Enrich Layer API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich.md) - [Enrich Layer API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-fuse-mcp.md) - [Enrich Layer API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-hunter.md) - [Enrich Layer API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-leadmagic.md) - [Enrich Layer API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-lusha.md) - [Enrich Layer API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-prospeo.md) - [FullEnrich API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/fullenrich-vs-gojiberry.md) - [Fuse MCP vs Gojiberry](https://www.anchorterminal.com/compare/fuse-mcp-vs-gojiberry.md) - [Gojiberry vs Hunter API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-hunter.md) - [Gojiberry vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-leadmagic.md) - [Gojiberry vs Lusha API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-lusha.md) - [Gojiberry vs Prospeo API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-prospeo.md) - [Dropcontact API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer.md) - [Dropcontact API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry.md)