Head to head · Lead search · October 2026 research run
Gojiberry vs Lusha API + MCP
Lusha API + MCP scores 62.3 (B) on agent readiness against Gojiberry's 47.9 (D), and leads in 6 of 7 scored categories. Both do lead search.
Which one, for what
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.
Also in its favour
- No incidents deducted, where Lusha API + MCP loses 4 points for them
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
Good for Sales teams that want contact and company enrichment, signals and prospecting from one vendor, with a free plan to start.
Ahead on
- Schema & documentation, 83 against 61
- Security & auth, 59 against 32
- Payments & pricing, 40 against 10
- Maintenance & community, 82 against 25
- Transparency & trust, 80 against 59
Watch for
At least 1 credit per request even when nothing matches
Score by category
| Category | Weight this run | Gojiberry | Lusha API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 74 | 75 | Lusha API + MCP +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 61 | 83 | Lusha API + MCP +22 |
| Agent ergonomics | 13%16.2 | 55 | 51 | Gojiberry +4 |
| Security & auth | 14%17.5 | 32 | 59 | Lusha API + MCP +27 |
| Payments & pricing | 10%12.5 | 10 | 40 | Lusha API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 25 | 82 | Lusha API + MCP +57 |
| Transparency & trust | 7%8.8 | 59 | 80 | Lusha API + MCP +21 |
| Negative events | ≤15 | 0 | -4 | |
| Total | 47.9 · D | 62.3 · B |
Facts side by side
| Fact | Gojiberry | Lusha API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | SUPERFRUITS SAS (Gojiberry AI) | Lusha |
| Hosted endpoint | https://ext.gojiberry.ai | https://api.lusha.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Gojiberry's General Terms | none |
| Tools exposed | none | 50 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | com.lusha.mcp/mcp |
| Last release | none | 2026-09-23 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2026-09-01 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | none | 3/5 (2) |
Verdicts
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.
Lusha API + MCP
API key on every plan, including Free with 40 credits a month. At least 1 credit per request even when nothing matches.
Before you call either
Gojiberry
- Send
Authorization: Bearer <key>to https://mcp.gojiberry.ai. The value must start with the word Bearer or the connection fails - Create resources in the order list, source agent, campaign. A source agent with no campaign only finds leads
- Adding a contact to a list enrols it in the linked campaign, which sends LinkedIn or email messages. Ask the user before list writes
- 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
- Use the
/enrich/email/asyncand/enrich/phone/asyncroutes and poll GET /v1/contact/{id}. The synchronous routes can take minutes
Lusha API + MCP
- Batch up to 25 contacts a request. A single bulk request costs 1 credit, not 1 per contact
- Ask for phones only when needed. A phone is 5 credits against 1 for an email
- Use the Buying Group endpoint. Decision Makers was retired on 2026-09-04
- Use
/v3/lookalike/contactsfor contact lookalikes - Back off exponentially on 429. Free keys stop at 100 requests a day
Questions
Which is better for AI agents, Gojiberry or Lusha API + MCP?
Lusha API + MCP scores 62.3 (B) on agent readiness against Gojiberry's 47.9 (D), and leads in 6 of 7 scored categories.
Do Gojiberry and Lusha API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Gojiberry and Lusha API + MCP without installing anything?
Yes. Gojiberry has a hosted endpoint at https://ext.gojiberry.ai and Lusha API + MCP at https://api.lusha.com.
Other comparisons with Gojiberry or Lusha API + MCP
- Apollo API + MCP vs Gojiberry
- Apollo API + MCP vs Lusha API + MCP
- Coresignal API + MCP vs Gojiberry
- Coresignal API + MCP vs Lusha API + MCP
- Crustdata API + MCP vs Gojiberry
- Crustdata API + MCP vs Lusha API + MCP
- Enrich Layer API + MCP vs Gojiberry
- Enrich Layer API + MCP vs Lusha API + MCP
- FullEnrich API + MCP vs Gojiberry
- FullEnrich API + MCP vs Lusha API + MCP
- Fuse MCP vs Gojiberry
- Fuse MCP vs Lusha API + MCP
- Gojiberry vs Hunter API + MCP
- Gojiberry vs LeadMagic API + MCP
- Gojiberry vs Prospeo API + MCP
- LeadMagic API + MCP vs Lusha API + MCP
- Lusha API + MCP vs Prospeo API + MCP
- Dropcontact API + MCP vs Gojiberry
- Dropcontact API + MCP vs Lusha API + MCP
- Hunter API + MCP vs Lusha API + MCP
Machine-readable
- This page as Markdown
/compare/gojiberry-vs-lusha.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/gojiberry.json·/api/v1/tools/lusha.json - From a terminal
anchor compare gojiberry lusha(the CLI) - Over MCP
compare_tools {"a": "gojiberry", "b": "lusha"}at/mcp, no key