Gojiberry vs Prospeo API + MCP

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.

Prospeo API + MCP

MCP tool descriptions say when to use each tool, its credit cost and the next call. No status page, SLA or changelog.

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

Prospeo API + MCP

1. Call search_suggestions before using location, technology or industry filters, or the search returns nothing
2. Pass person_id values from search into bulk_enrich_person, 25 at a time
3. Branch on the body error_code, not the HTTP status, which is 400 for most failures
4. Set enrich_mobile only when needed. A mobile costs 10 credits against 1 for an email
5. Use Enrich Person. The old Email Finder endpoint was removed in March 2026