Gojiberry vs People Data Labs

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.

People Data Labs

Monthly dated release notes, a free sandbox with synthetic data, response headers that report credits and rate limits, and a free plan of 100 records a month make the API easy to start with. No OpenAPI file was found, keys carry no scopes and may travel in the URL, and the agreement allows changes without notice.

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

People Data Labs

1. Send the key in the X-Api-Key header. The api_key query parameter puts the secret in URLs and logs
2. Build and test queries against https://sandbox.api.peopledatalabs.com/v5/... first. It costs no credits and allows five calls a minute
3. Set size deliberately on search. Every record returned costs one credit, and responses over 1 MB fail
4. Treat 404 on enrichment as no match, not an error, and 402 as credits exhausted. Neither is worth a retry
5. On 429, wait until the x-ratelimit-reset time. Limits are fixed-window per key and per endpoint