# Gojiberry vs Retriever

> Gojiberry scores 48.9 (D) to Retriever's 32 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/gojiberry-vs-retriever
- Markdown: https://www.anchorterminal.com/compare/gojiberry-vs-retriever.md (~5,050 tokens)
- Slim: https://www.anchorterminal.com/compare/gojiberry-vs-retriever.min.md (~980 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/gojiberry-vs-retriever.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Gojiberry scores 48.9 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on schema & documentation, agent ergonomics and payments & pricing. Both do lead search.

- Gojiberry: grade D, 48.9/100, rank #1192 of 1557. Markdown https://www.anchorterminal.com/tools/gojiberry.md · JSON https://www.anchorterminal.com/api/v1/tools/gojiberry.json
- Retriever: grade F, 32/100, rank #1455 of 1557. Markdown https://www.anchorterminal.com/tools/retriever.md · JSON https://www.anchorterminal.com/api/v1/tools/retriever.json
- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md
- All 253 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md

## Which one, for what

### 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, 70 against 45
- Security & auth, 31 against 23
- Maintenance & community, 20 against 5
- Transparency & trust, 61 against 49

Also in its favour:
- No incidents deducted, where Retriever loses 15 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`

### Retriever (F)

Good for: A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.

Ahead on:
- Schema & documentation, 82 against 71
- Agent ergonomics, 75 against 55
- Payments & pricing, 30 against 15

Watch for: Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted


## Why the edge

### Reliability: Gojiberry +25

- Gojiberry (70): Graded with the hosted lines. Status page at status.gojiberry.ai on Better Stack with two components, gojiberry.ai and api.gojiberry.ai, and 90-day bars. Neither names ext.gojiberry.ai or mcp.gojiberry.ai, the hosts an agent calls, so the page has no component for the product (15, was 20). Both show 100 per cent, and the incident history lists none for September, October or November 2026 (August per the 8 October check). The page has not been shown to post any incident, so 20 rather than a clean record (was 22, an in-between value; tldv, zamp). The quickstart and the OpenAPI file state 100 requests a minute and 100,000 a day per account, shared by all keys and MCP connections, with lower limits on some endpoints (15). 429 line 7 to 10. Requests over a limit now get `429 Too Many Requests` with a `Retry-After` header and the instruction to wait that long before retrying. No idempotency keys or safe-retry guidance for writes, so Retry-After alone (10). No SLA found, and the terms say the service is supplied as is (0). API version 1.0 with no beta label (10). 15 + 20 + 15 + 10 + 0 + 10 = 70.
- Retriever (45): No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists "Dedicated support & SLA" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).

### Agent ergonomics: Retriever +20

- Gojiberry (55): On the API, search returns masked rows until revealed, but a Contact has 75 fields and no field selection (14 of 25). `page` and `limit` on lists, eleven filters on contacts and fifteen on lead search (17 of 20). Status codes are documented per operation, with 402 for credits, 409 and 422. Bodies are `{message, statusCode}` and there's no error catalogue (11 of 20). No idempotency keys. Search is deterministic, a deleted contact can't be created again, and failed enrichments cost nothing. The MCP page says tools that change data are flagged, which we couldn't read from the server (7 of 20). Few required parameters and stated defaults, no official SDKs (6 of 15). 14 + 17 + 11 + 7 + 6 = 55.
- Retriever (75): 67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15).

### Payments & pricing: Retriever +15

- Gojiberry (15): No x402, MPP or L402 (0). The Pro plan is public at $99 a month, and credit costs per action are published, but no dollar price per credit was found (10). There's a free trial, and the help centre says the subscription then starts on the saved payment method, so we read it as needing a card. We didn't open the signup form (0). A person signs up in a browser and the terms forbid account creation by bots (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
- Retriever (30): No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0).

### Maintenance & community: Gojiberry +15

- Gojiberry (20): No changelog or dated API release was found. The developer docs carry no dates, and their sitemap stamps record no change. The newest dated evidence is help-centre editing. The MCP article is dated 29 September 2026 and the API article 21 August 2026, so the partial credit for activity inside 90 days is kept (15 of 30). No dated releases to count (0). Live chat and hello@gojiberry.ai for support, not tested, and no public changelog (5 of 15). No readable registry page names the server and no official SDKs exist (0). Package health 5 to 0, an in-between value with no package behind it. 15 + 0 + 5 + 0 + 0 = 20.
- Retriever (5): No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.

### Transparency & trust: Gojiberry +12

- Gojiberry (61): Closed service with published terms naming SUPERFRUITS SAS, Paris, unchanged since 14 October 2025 (15). The privacy policy was rewritten on 13 October 2026. It names its sources as public professional profiles, public social engagement and enrichment vendors, relies on legitimate interest, and runs an opt-out page with a suppression list. Retention for lead data is now set by purpose with no fixed period, so the earlier conflict with the retention article (60 days against no limit) is gone, and no period replaces it. A DPA is supplied on request (19 of 30). No deprecation policy. The terms allow discontinuing parts of the service with or without notice (3 of 20). Nine sub-processors listed with purposes and locations in the help centre (updated 25 September 2026), hosting in AWS eu-west-3, US processing by OpenAI, Anthropic and Intercom (18 of 20). 15 + 19 + 3 + 18 = 55.
- Retriever (49): Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed "with reasonable notice" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20).

### Schema & documentation: Retriever +11

- Gojiberry (71): Gojiberry moved its developer docs to dev.gojiberry.ai (Mintlify), and ext.gojiberry.ai/documentation now redirects there. Public OpenAPI 3.0.0 file, version 1.0, with 56 operations on 45 paths, linked from the docs' llms.txt under OpenAPI Specs (25). llms.txt 0 to 10. dev.gojiberry.ai serves llms.txt and every page as Markdown. 47 of 56 operations carry a description, and many say when to use them, such as the async enrichment routes for MCP clients and free search before paid reveal (15 of 20). 25 enums, 23 required lists and 50 required parameters, but search results are untyped objects and only four length bounds appear (9 of 15). 73 examples and curl samples. Error responses are a status code and a sentence, none of the 53 error responses has a body schema (8 of 15). A /v1 path and version 1.0, with no changelog found (4 of 15). 25 + 10 + 15 + 9 + 8 + 4 = 71.
- Retriever (82): OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). The tool catalogue says when to use most tools and when not to (cancels only on the user's request, slow services only in a batch) (17 of 20). The OpenAPI file has enums and required fields; the MCP input schemas weren't read, since tools/list needs a key (11 of 15). An errors page with stable codes and the action for each, plus examples in the docs (14 of 15). Routes are versioned under /v1 but there's no public changelog (5 of 15).

## Score by category

| Category | Weight | Gojiberry | Retriever | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 70 | 45 | Gojiberry +25 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 71 | 82 | Retriever +11 |
| Agent ergonomics | 13% | 55 | 75 | Retriever +20 |
| Security & auth | 14% | 31 | 23 | Gojiberry +8 |
| Payments & pricing | 10% | 15 | 30 | Retriever +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 20 | 5 | Gojiberry +15 |
| Transparency & trust | 7% | 61 | 49 | Gojiberry +12 |
| Negative events | ≤15 | 0 | -15 | |
| **Total** | | **48.9 · D** | **32 · F** | |

## Facts side by side

| Fact | Gojiberry | Retriever |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | SUPERFRUITS SAS (Gojiberry AI) | Retriever |
| Hosted endpoint | `https://ext.gojiberry.ai` | `https://api.retriever.run/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under Gojiberry's General Terms | none |
| Tools exposed | none | 67 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Terms last updated | no date given | 2026-08-30 |
| Privacy policy last updated | no date given | 2026-08-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |

## How the scores have moved

### Gojiberry

- +0.7 on 13 November 2026: checklist
- +0.2 on 4 November 2026: product, correction
- +0.1 on 27 October 2026: checklist

### Retriever

No score change since it was listed.

## Verdicts

**Gojiberry.** A public OpenAPI file with 56 operations linked from the developer docs' llms.txt, a free masked lead search and published limits of 100 requests a minute with Retry-After make the API easy to plan against. Keys have no scopes, an owner's key can act as any member, and writes can start LinkedIn and email outreach from connected accounts.

**Retriever.** Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.

## Before you call either

### Gojiberry

1. Connect MCP clients to https://mcp.gojiberry.ai/mcp and sign in to Gojiberry. Custom clients must send a `User-Agent` header or get a 403
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
5. On a 429, wait for the `Retry-After` seconds before retrying. Limits are shared by every key and MCP connection of the account

### Retriever

1. Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account
2. Send an `Idempotency-Key` with each run and replay with the same key after a timeout, so a retry doesn't start a second billed run
3. Run `getEmail`, `getPhoneNumber` and `webResearch` through `service_batch_execute`, even for one person; `service_execute` refuses them
4. Check `credits` before a paid run, and call `service_inspect` for a service's `thingsToKnow` and credit cost before executing it
5. On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again

## Questions

### Which is better for AI agents, Gojiberry or Retriever?

Gojiberry scores 48.9 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on schema & documentation, agent ergonomics and payments & pricing.

### Do Gojiberry and Retriever need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Gojiberry and Retriever without installing anything?

Yes. Gojiberry has a hosted endpoint at https://ext.gojiberry.ai and Retriever at https://api.retriever.run/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/gojiberry-vs-retriever.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gojiberry-vs-retriever.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "gojiberry", "b": "retriever"}`. From a terminal: `anchor compare gojiberry retriever`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gojiberry.json and https://www.anchorterminal.com/api/v1/tools/retriever.json

## Other comparisons with Gojiberry or Retriever

- [Apollo API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/apollo-vs-gojiberry.md)
- [Apollo API + MCP vs Retriever](https://www.anchorterminal.com/compare/apollo-vs-retriever.md)
- [Clay vs Gojiberry](https://www.anchorterminal.com/compare/clay-vs-gojiberry.md)
- [Clay vs Retriever](https://www.anchorterminal.com/compare/clay-vs-retriever.md)
- [Coresignal API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/coresignal-vs-gojiberry.md)
- [Coresignal API + MCP vs Retriever](https://www.anchorterminal.com/compare/coresignal-vs-retriever.md)
- [Crustdata API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/crustdata-vs-gojiberry.md)
- [Crustdata API + MCP vs Retriever](https://www.anchorterminal.com/compare/crustdata-vs-retriever.md)
- [Dievio vs Gojiberry](https://www.anchorterminal.com/compare/dievio-vs-gojiberry.md)
- [Dievio vs Retriever](https://www.anchorterminal.com/compare/dievio-vs-retriever.md)
- [Enrich Layer API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/enrich-layer-vs-gojiberry.md)
- [Enrich Layer API + MCP vs Retriever](https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.md)
- [Explorium AgentSource vs Gojiberry](https://www.anchorterminal.com/compare/explorium-agentsource-vs-gojiberry.md)
- [Explorium AgentSource vs Retriever](https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.md)
- [FullEnrich API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/fullenrich-vs-gojiberry.md)
- [FullEnrich API + MCP vs Retriever](https://www.anchorterminal.com/compare/fullenrich-vs-retriever.md)
- [Fuse MCP vs Gojiberry](https://www.anchorterminal.com/compare/fuse-mcp-vs-gojiberry.md)
- [Fuse MCP vs Retriever](https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.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 People Data Labs](https://www.anchorterminal.com/compare/gojiberry-vs-people-data-labs.md)
- [Gojiberry vs Prospeo API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-prospeo.md)
- [Gojiberry vs RocketReach API](https://www.anchorterminal.com/compare/gojiberry-vs-rocketreach.md)
- [Gojiberry vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-zoominfo.md)
- [LeadMagic API + MCP vs Retriever](https://www.anchorterminal.com/compare/leadmagic-vs-retriever.md)
- [Lusha API + MCP vs Retriever](https://www.anchorterminal.com/compare/lusha-vs-retriever.md)
- [People Data Labs vs Retriever](https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.md)
- [Prospeo API + MCP vs Retriever](https://www.anchorterminal.com/compare/prospeo-vs-retriever.md)
- [Retriever vs RocketReach API](https://www.anchorterminal.com/compare/retriever-vs-rocketreach.md)
- [Retriever vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/retriever-vs-zoominfo.md)
- [Clearbit vs Gojiberry](https://www.anchorterminal.com/compare/clearbit-vs-gojiberry.md)
- [Clearbit vs Retriever](https://www.anchorterminal.com/compare/clearbit-vs-retriever.md)
- [Databar vs Gojiberry](https://www.anchorterminal.com/compare/databar-vs-gojiberry.md)
- [Databar vs Retriever](https://www.anchorterminal.com/compare/databar-vs-retriever.md)
- [Dropcontact API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry.md)
- [Dropcontact API + MCP vs Retriever](https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md)
- [FullContact vs Gojiberry](https://www.anchorterminal.com/compare/fullcontact-vs-gojiberry.md)
- [FullContact vs Retriever](https://www.anchorterminal.com/compare/fullcontact-vs-retriever.md)
- [Gojiberry vs ZeroBounce](https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce.md)
- [Retriever vs ZeroBounce](https://www.anchorterminal.com/compare/retriever-vs-zerobounce.md)
- [Hunter API + MCP vs Retriever](https://www.anchorterminal.com/compare/hunter-vs-retriever.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
