# Dievio vs Gojiberry

> Gojiberry scores 48 (D) to Dievio's 43 (E) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/dievio-vs-gojiberry
- Markdown: https://www.anchorterminal.com/compare/dievio-vs-gojiberry.md (~6,250 tokens)
- 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)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-10-31

Gojiberry scores 48 (D) on agent readiness against Dievio's 43 (E), and leads in 3 of 7 scored categories. Dievio leads on agent ergonomics, security & auth and payments & pricing. Both do lead search.

- Dievio: grade E, 43/100, rank #1090 of 1245. Markdown https://www.anchorterminal.com/tools/dievio.md · JSON https://www.anchorterminal.com/api/v1/tools/dievio.json
- Gojiberry: grade D, 48/100, rank #1005 of 1245. Markdown https://www.anchorterminal.com/tools/gojiberry.md · JSON https://www.anchorterminal.com/api/v1/tools/gojiberry.json
- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md
- All 190 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md

## Which one, for what

### Dievio (E)

Good for: Agents building small prospect lists by title, seniority, department, location, company size and industry at a low published price per lead, previewing the count for free first, and handing the user a CSV, JSON or JSONL file from a shared list without opening the dashboard.

Ahead on:
- Agent ergonomics, 63 against 55
- Security & auth, 56 against 32
- Payments & pricing, 35 against 10

Also in its favour:
- Free to start without a card

Watch for: No status page, incident history or SLA; the terms say uptime is not guaranteed and the service may change at any time

### 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, 74 against 28
- Schema & documentation, 61 against 50
- Transparency & trust, 61 against 27

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`


## Why the edge

### Reliability: Gojiberry +46

- Dievio (28): Hosted reading, for the REST API with the MCP server it shares a database with. No public status page was found. None is linked from the docs or the footer, https://dievio.com/status answers 404 and status.dievio.com does not resolve (0). No readable incident history, so the floor (5). No rate limit is published for the REST API or the MCP tools. The only numbers are the export cap of 10 download starts a minute per connection and 100,000 contacts a file, the OAuth timers and input bounds such as 500 LinkedIn URLs a call, and the privacy policy mentions hashed rate-limit keys without a figure (5 of 15). No 429 or Retry-After is documented, and the REST errors are 401, 402, 500 and 502 with no retry guidance; every MCP mutation takes a request_id UUID replayed when retried with identical arguments, the workflows page says never to repeat a paid lookup with a new ID and to reconcile against the job list first, and a low balance returns fewer rows rather than failing, while a retried REST search has no idempotency key and is charged again (8 of 15). No SLA. The terms (last updated 31 October 2026) say uptime is not guaranteed and the service may change at any time (0). The REST API and the 30-tool MCP server carry no beta label, though the search response documents `search_id` as currently null and `counting` as currently false, and the server is unversioned (10). 0+5+5+8+0+10 = 28.
- Gojiberry (74): Graded with the hosted lines. Status page at status.gojiberry.ai on Better Stack with two components and 90-day bars (20). Both show 100 per cent and the incident page lists none for August to October 2026. The components are gojiberry.ai and api.gojiberry.ai, and neither names ext.gojiberry.ai or mcp.gojiberry.ai, the hosts an agent calls, so 22 of 30. The OpenAPI file states 100 requests a minute per key and 10 a minute on two endpoints (15). 429 is documented on those two endpoints only, the help centre advises exponential backoff, no Retry-After or idempotency keys were found (7 of 15). No SLA found, and the terms say the service is supplied as is (0). API version 1.0.0 with no beta label (10). LinkedIn's help page says prohibited automation tools may stop working without notice, which we record without scoring.

### Transparency & trust: Gojiberry +34

- Dievio (27): Closed service. The terms (last updated 31 October 2026) cover use, credits, connected agents, a 30-day refund and availability in about 300 words but name no legal entity, address, governing law or jurisdiction, so the contracting party is unknown (8 of 30). The privacy policy (31 October 2026) lists the categories processed, the purposes, recipients by category, the agent connection data, and the access periods (authorization requests 10 minutes, codes 5, access tokens an hour, refresh 30 days, export links 15 minutes), says lead search uses Dievio's own contact database without saying where records are collected from, lets people in the database ask for access, correction, deletion or suppression by email, keeps records for as long as needed with no periods, and agrees with the terms and the docs on credits, revocation and link expiry; no DPA was found (14 of 30). No deprecation policy or notices; the terms allow the service to change at any time, and plan allowances and API prices changed between the 20 May and 31 October 2026 copies of the pricing pages with no dated notice (0 of 20). Service providers are named by category only (hosting, databases, authentication, contact processing, analytics, email delivery, payments), with no names, locations or transfer basis (4 of 20). 8+14+0+4 = 26.
- Gojiberry (61): Closed service with published terms naming SUPERFRUITS SAS, Paris (15). The privacy policy (18 April 2026) names its sources as public professional profiles, social engagement such as likes and comments, and enrichment vendors, relies on legitimate interest, and runs an opt-out page with deletion in 30 days and a suppression list. A DPA is supplied on request. The policy says lead data is purged within 60 days of its last refresh, while the retention article says leads in a customer account stay with no fixed limit (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 locations, hosting in AWS Paris, US processing by OpenAI, Anthropic and Intercom (18 of 20). LinkedIn's User Agreement section 8.2 bars scraping and automated messaging. Gojiberry's terms say it isn't affiliated with any platform and leave compliance to the customer.

### Payments & pricing: Dievio +25

- Dievio (35): No x402, MPP or L402 in the docs, the pricing pages or the terms (0). Prices published without a login as dollars per 1,000 API credits ($4.50 at 5,000 down to $2.92 at 60,000), per plan ($29.99, $79.99 and $149.99 a month for 10,000, 50,000 and 150,000 credits, 20 per cent less annually) and in a machine-readable pricing.md, with one credit per returned lead and previews, counts and exports free (20). Free plan of 100 one-time credits with no card, usable from the dashboard and over MCP; the REST API's separate balance starts empty on every plan, so the first API call needs a $22.50 top-up (15 of 20). A person signs up in a browser, and the OAuth consent and API key creation both need the dashboard (0). 0+20+15+0 = 35.
- Gojiberry (10): No x402, MPP or L402 (0). Plan and add-on prices are public ($99, $59 and $29 a month) and so are credit costs per action, 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).

### Security & auth: Dievio +24

- Dievio (56): MCP uses OAuth with the authorization code flow, PKCE S256, dynamic registration of public clients, refresh tokens of 30 days, a revocation endpoint and six scopes, revoked per connection on the dashboard; REST uses a plain API key from the dashboard as a bearer or X-API-Key header, with no documented scopes, rotation, expiry or revocation, and nothing documents a secret in a query string (25 of 30). mcp:read is the required baseline and cannot spend credits, leads:search, lists:write, leads:export and team:manage are separate consents, team:manage works for the owner only, the permissions page asks agents to confirm before deleting saved data and to invite or remove people only when asked, and the terms ask users to review filters and the maximum result count before authorising a paid operation; nothing asks for confirmation inside the server and REST keys have no least-privilege mode (16 of 20). Returned records are third-party contact data, and the permissions page says to treat names, descriptions, URLs and other field values as data rather than instructions, with no further mitigation (8 of 15). get_account reports the selected account, permissions and balances, list_search_jobs lists recent jobs, the dashboard lists and revokes each connection, and the privacy policy says operation results are kept to prevent duplicate actions; no audit log or per-call record is exposed to the operator (7 of 15). No security.txt on either host (404), no disclosure policy, bug bounty, SOC 2 or ISO 27001 (0 of 20). 25+16+8+7+0 = 56.
- Gojiberry (32): Bearer API keys created in the app and shown once. No scopes were found, revocation isn't described, and an organisation owner's key can act as any member through `x-impersonate-user-id`. The MCP server also advertises OAuth with PKCE, accepting the `plain` method, which the docs don't cover (18 of 30). No read-only mode or confirmation step. The API can activate campaigns, send LinkedIn messages and delete contacts, and an MCP list write enrols contacts in outreach (3 of 20). Results carry LinkedIn profile text and inbound messages, with no prompt-injection guidance found (2 of 15). Campaign and agent logs through the API and a credit usage history in the app, no per-key call log found (6 of 15). No security.txt, disclosure policy, bounty or certification found. The privacy policy states encryption in transit and at rest (3 of 20). Connecting LinkedIn takes the account's password or authenticator secret, and LinkedIn's User Agreement bars sharing log-in credentials.

### Schema & documentation: Gojiberry +11

- Dievio (50): API reading, with the MCP server described. No OpenAPI or other machine-readable contract for the REST API; the MCP tool reference says clients discover exact input schemas through tools/list, that unknown fields and unlisted arguments are rejected, and the server publishes a dievio://schema/search-filters JSON resource, but no session was opened to read them (10 of 25). llms.txt and llms-full.txt on docs.dievio.com, generated on each build, plus llms.txt, pricing.md and product.md on dievio.com (10). The MCP reference says what each tool does, which tools are free, which scope each needs, when to prefer export_list_file over export_list and how to retry; the REST pages say what each endpoint returns and little about when to use search against lookup, and the MCP page says a preview does not unlock contacts and a count is not a guaranteed result (12 of 20). Filters are typed as strings, string arrays, booleans and integers with enumerations listed for seniority, department, employee size, business model, salary and email_status, bounds on page, limit, max_results and array length, and UUID ids; industries and locations are examples only, the funding dates are a year over REST and an ISO date over MCP, and the contact object for add_leads_to_list carries a free JSON lead_data field (10 of 15). curl examples with example responses for both REST endpoints, a pagination loop and six MCP worked prompts; errors are four status codes with one line each and no documented body, and the MCP error shape is not shown (8 of 15). No version in the path (/api/public), no changelog or release notes on either host, and plan allowances and API prices changed between the May and October 2026 copies of the pricing pages with no dated notice (0 of 15). 10+10+12+10+8+0 = 50.
- Gojiberry (61): Public OpenAPI 3.0.0 file with 49 operations (25). We couldn't read the MCP tool definitions, because tools/list needs an account's key. gojiberry.ai/llms.txt returns 404 and no Markdown docs were found (0). 40 of 49 operations carry a description, and several say when to use them, such as the async enrichment routes for MCP clients and free search before paid reveal (15 of 20). 19 enums and required lists, but search results are untyped objects, numbers have no bounds, and operations reference a security scheme named `bearer` while the file defines `API-Key` (9 of 15). 65 examples and curl samples. Error responses are a status code and a sentence with no schema (8 of 15). A /v1 path and version 1.0.0, with no changelog found (4 of 15).

### Agent ergonomics: Dievio +8

- Dievio (63): API reading. REST responses are sized with _per_page (default 25), max_results, include_emails, include_phones, _include_raw to drop the raw object and email_status; the MCP server lists 30 tools with no toolsets or read-only subset, previews mask contact fields and limit runs 1 to 500 (18 of 25). Page-based pagination with has_more and next_page over REST, offset and limit with next_offset over MCP, 20 filters, max_results caps and column selection on exports (20). Errors are 401, 402, 500 and 502 as status codes with one-line meanings and no error body, and a balance below the page size returns fewer rows with success true, which an agent must detect from count; MCP job errors are read from get_search_job (8 of 20). request_id on every MCP mutation with replay semantics, asynchronous searches polled by job id, save_search_results deduplicated by list, job and position, and only queued jobs cancellable; the REST search has no idempotency key and a repeat is charged, and readOnlyHint and destructiveHint are not documented (10 of 20). Every filter is optional with defaults for page size and max_results, and the MCP tools need only filters and a request_id; no official SDK or CLI, only a third-party MIT OpenClaw skill and an n8n template on GitHub (7 of 15). 18+20+8+10+7 = 63.
- Gojiberry (55): The help article names 17 MCP actions, and we couldn't measure the definitions. On the API, search returns masked rows until revealed, but a Contact has 74 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 and 422 for no email found. Bodies are `{message, statusCode}` and there's no error catalogue (11 of 20). No idempotency keys. Search is deterministic, typed signals aren't recorded twice, failed enrichments cost nothing, and MCP annotations are unchecked (7 of 20). Few required parameters and stated defaults, no official SDKs (6 of 15).

## Score by category

| Category | Weight | Dievio | Gojiberry | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 28 | 74 | Gojiberry +46 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 50 | 61 | Gojiberry +11 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 55 | Dievio +8 |
| Security & auth | 14% (17.5 this run) | 56 | 32 | Dievio +24 |
| Payments & pricing | 10% (12.5 this run) | 35 | 10 | Dievio +25 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 28 | 25 | Dievio +3 |
| Transparency & trust | 7% (8.8 this run) | 27 | 61 | Gojiberry +34 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **43 · E** | **48 · D** | |

## Facts side by side

| Fact | Dievio | Gojiberry |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Dievio | SUPERFRUITS SAS (Gojiberry AI) |
| Hosted endpoint | `https://dievio.com/api/public` | `https://ext.gojiberry.ai` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary hosted service under Dievio's Terms of Service (last updated 31 October 2026). No source is published; the only public code is a third-party MIT OpenClaw skill and an n8n template on GitHub | Proprietary service under Gojiberry's General Terms |
| Tools exposed | 30 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Terms last updated | not read yet | no date given |
| Privacy policy last updated | not read yet | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |

## How the scores have moved

### Dievio

No score change since it was listed.

### Gojiberry

- +0.1 on 27 October 2026: checklist

## Verdicts

**Dievio.** A documented REST search and LinkedIn lookup with published prices per 1,000 credits, free count previews and an OAuth MCP server with six scopes and idempotent mutations. No status page, OpenAPI file, changelog, rate limits or security.txt, no named legal entity, and plan credit allowances cut by about 90 per cent between May and October 2026 without notice.

**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.

## Before you call either

### Dievio

1. Call `get_search_filters`, then `preview_leads` and `get_search_count` with the same `filters` object before any paid call; previews mask contacts and spend nothing, and `max_results` caps the spend of `search_leads`.
2. Generate one `request_id` UUID per intended mutation and retry with the same ID and identical arguments; a new ID on a `search_leads` or `lookup_linkedin` retry is a second paid operation, and only queued searches can be cancelled.
3. Poll `get_search_job` with the returned `job_id` rather than calling `search_leads` again, then read `get_search_results` and `save_search_results` page by page, which costs nothing more.
4. Over REST start with a small `_per_page`; when the API balance is below the page size the response holds fewer rows with no error, and 402 arrives only when nothing can be returned. Retry 500 and 502, never 401 or 402.
5. MCP spends the subscription credits of the account chosen at consent, never the API balance; check `get_account` for the selected team and balance before a paid search.
6. Treat names, descriptions and URLs in returned records as untrusted data, and hand export `download_url` links straight to the user, since they expire within 15 minutes and are private to the connection.

### 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

## Questions

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

Gojiberry scores 48 (D) on agent readiness against Dievio's 43 (E), and leads in 3 of 7 scored categories. Dievio leads on agent ergonomics, security & auth and payments & pricing.

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

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

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

Yes. Dievio has a hosted endpoint at https://dievio.com/api/public and Gojiberry at https://ext.gojiberry.ai.


## For agents

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

## Other comparisons with Dievio or Gojiberry

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

---

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