Explorium AgentSource vs Gojiberry

Explorium AgentSource

AgentSource v2 has a public OpenAPI 3.1 file, Markdown docs, a 200 queries a minute limit with Retry-After, public credit prices and a 100-credit trial. No status page or published SLA was found, each company shares one API key with no scopes, and the vendor's two published price tables disagree.

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.

Explorium AgentSource

1. Send the key in the api_key header to https://api.explorium.ai and use /v2 paths. v1 is deprecated
2. Point MCP clients at https://mcp-v2.explorium.ai/mcp. The site's agent files still name the v1 server at mcp.explorium.ai
3. Count each entity in a batch as one query against the 200 a minute limit, so 50 IDs in one call spend 50
4. Call the statistics endpoint first to size an audience for free. Fetch costs 1 credit a result, or 2 with the Bombora intent filter
5. Call /v2/autocomplete before filtering on category, tech stack or job title, and never mix two category types in one request

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