{
  "data": {
    "a": {
      "slug": "fullenrich",
      "name": "FullEnrich API + MCP",
      "vendor": "FullEnrich",
      "vendorUrl": "https://fullenrich.com",
      "company": "fullenrich.com",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Waterfall contact enrichment that queries 25+ data providers for work emails, personal emails and mobile numbers, plus people and company search and lookup and reverse email lookup.",
      "url": "https://www.anchorterminal.com/tools/fullenrich",
      "markdownUrl": "https://www.anchorterminal.com/tools/fullenrich.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fullenrich.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fullenrich.json",
      "dns": "fullenrich.grade.anchorterminal.com",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://app.fullenrich.com/api/v2",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Bearer API key in the Authorization header for REST. The hosted MCP server at https://mcp.fullenrich.com/mcp signs in with your FullEnrich account over OAuth. Webhooks carry an X-Signature-SHA1 header, an HMAC-SHA1 of the raw body keyed with your API key.",
      "pricing": "freemium",
      "pricingNotes": "Free trial with 50 credits and no card. Pro from $29 a month for 500 credits ($55 for 1,000, about $0.055 a credit), scaling to $3,500 a month for 100,000 credits, with cheaper annual billing and Enterprise on quote. Credits are spent only on found data. A work email costs 1 credit, a personal email 3, a mobile number 10, a reverse email match 1, and each search result 0.25 (free to export again). Unused credits roll over for 3 months on monthly plans and 12 on annual (https://fullenrich.com/pricing.md, checked 2026-11-04).",
      "priceSummary": "$29 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "endpoints": []
      },
      "toolCount": 13,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://docs.fullenrich.com",
      "llmsTxt": "https://docs.fullenrich.com/llms.txt",
      "openapi": "https://docs.fullenrich.com/api/v2/reference/openapi.yaml",
      "registryName": "io.github.FullEnrich/fullenrich",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.finder",
        "data.person",
        "data.company"
      ],
      "tags": [
        "hosted",
        "freemium",
        "no-card",
        "mcp",
        "llms-txt",
        "openapi",
        "webhooks",
        "async-jobs",
        "closed-source",
        "lead-search",
        "enrichment"
      ],
      "lastRelease": "2026-08-27",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 64.7,
        "grade": "B",
        "agentReady": false,
        "rank": 571,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 4,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 66,
          "maintenance": 48,
          "payments": 60,
          "reliability": 70,
          "schema": 76,
          "security": 57,
          "transparency": 68
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": 0,
        "verdict": "Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.",
        "bestFor": "Maximising find rate on known contacts, especially mobiles, without a long-term contract.",
        "strengths": [
          "Credits only spent on found data, and identical re-runs within 3 months are free",
          "50 trial credits with no card, API and MCP included",
          "Hosted MCP with OAuth and 13 tools, listed in the official registry under io.github.FullEnrich",
          "OpenAPI file with per-operation error codes, llms.txt and a Markdown pricing page",
          "SOC 2 Type 2 per the trust page, with data hosted in the EU"
        ],
        "weaknesses": [
          "Enrichment sources are data providers the vendor doesn't name",
          "Status page covers the web app only, not the API or MCP",
          "No safe-retry guidance for writes and no SLA",
          "Public product changelog stopped at November 2024 and now answers an error",
          "Webhooks signed with HMAC-SHA1 keyed with the API key itself"
        ],
        "agentNotes": [
          "Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again",
          "Expect 30 to 90 seconds a contact. Use the webhook or poll `get_enrichment_results`",
          "Ask for mobiles only when needed. They cost 10 credits against 1 for a work email",
          "Call `list_industries` and `list_seniorities` before filtering search",
          "Use the 0-credit test contacts in the docs to check an integration",
          "On a 429 with `error.rate.limit`, wait a minute before retrying. The limit is 60 calls a minute on every endpoint"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 64.7
          }
        ],
        "editorialScores": {
          "ergonomics": 66,
          "maintenance": 48,
          "payments": 60,
          "reliability": 70,
          "schema": 76,
          "security": 57,
          "transparency": 56
        },
        "provenanceScore": 80,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl https://app.fullenrich.com/api/v2/account/credits -H \"Authorization: Bearer $FULLENRICH_API_KEY\"",
        "claudeCode": "claude mcp add --transport http fullenrich https://mcp.fullenrich.com/mcp",
        "config": {
          "mcpServers": {
            "fullenrich": {
              "url": "https://mcp.fullenrich.com/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/fullenrich"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Pro, 500 credits",
          "unit": "month",
          "usd": 29
        },
        {
          "item": "Pro, 1,000 credits",
          "unit": "month",
          "usd": 55
        },
        {
          "item": "Pro, 15,000 credits",
          "unit": "month",
          "usd": 720
        },
        {
          "item": "Credit on Pro 1,000",
          "unit": "credit",
          "usd": 0.055,
          "note": "one found work email; a mobile is 10 credits, a personal email 3, a search result 0.25"
        }
      ],
      "provenance": {
        "legalEntity": "FullEnrich Corp",
        "domain": "fullenrich.com",
        "domainRegistered": "2023-04-08",
        "endpointOnVendorDomain": true,
        "terms": "https://fullenrich.com/tos",
        "privacy": "https://fullenrich.com/privacy-policy",
        "statusPage": "https://status.fullenrich.com",
        "changelog": "https://fullenrich.com/changelog",
        "securityTxt": "none",
        "checked": "2026-11-04",
        "notes": [
          "The public changelog's newest entry is 30 November 2024 per the 1 October 2026 check; on 4 November 2026 the page answered 400 \"Invalid page\". The MCP package keeps its own CHANGELOG in github.com/FullEnrich/fullenrich-skills, latest 1.0.4 on 2026-08-27",
          "The status page has one component, app.fullenrich.com/app, and none for the API. Its robots.txt is an empty 200 (no rules)",
          "fullenrich.com/.well-known/security.txt answered 404 on 4 November 2026"
        ],
        "score": 80
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/fullenrich.json",
      "live": {
        "slug": "fullenrich",
        "probe": {
          "target": "https://app.fullenrich.com/api/v2",
          "method": "get",
          "lastAt": "2026-11-18T21:50:49.339051353Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 162,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 70,
          "p95ms24h": 200,
          "samples24h": 242,
          "samples30d": 7829,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-29",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 220,
              "ok": 220
            }
          ],
          "since": "2026-10-08T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.fullenrich.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-18T18:52:34.881009858Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "io.github.FullEnrich/fullenrich",
            "version": "1.0.4",
            "seenAt": "2026-11-17T22:21:47.712728033Z"
          }
        ],
        "securityTxt": {
          "url": "https://fullenrich.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:30:44.620498156Z"
        },
        "llmsTxt": {
          "url": "https://docs.fullenrich.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:14:23.32534156Z"
        },
        "domain": {
          "domain": "fullenrich.com",
          "registered": "2023-04-08",
          "source": "https://rdap.verisign.com/com/v1/domain/fullenrich.com",
          "checkedAt": "2026-11-15T15:35:42.320531936Z"
        },
        "pages": [
          {
            "url": "https://fullenrich.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-18T21:44:06.599489896Z",
            "changedAt": "2026-11-06T13:32:21.946678463Z",
            "fingerprint": "21cc3cbeed28"
          },
          {
            "url": "https://fullenrich.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-04T08:24:22.224697456Z",
            "changedAt": "2026-10-28T04:18:22.922082282Z",
            "fingerprint": "b320816d19e5"
          },
          {
            "url": "https://fullenrich.com/pricing.md",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-18T21:44:09.142785901Z",
            "changedAt": "2026-11-12T17:40:02.88622103Z",
            "fingerprint": "b4baf1057ebb"
          },
          {
            "url": "https://fullenrich.com/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:44:10.618855428Z",
            "changedAt": "2026-11-06T13:32:25.990764115Z",
            "fingerprint": "754c6d67f3dd"
          },
          {
            "url": "https://fullenrich.com/tos",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:44:13.044119701Z",
            "changedAt": "2026-11-06T13:32:28.60618135Z",
            "fingerprint": "b39985f843fd"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.fullenrich.com/mcp",
          "checkedAt": "2026-11-18T04:24:01.822997057Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:44:40.155434389Z"
        },
        "updatedAt": "2026-11-18T21:50:49.339051353Z"
      },
      "streak": {
        "days": 41,
        "from": "2026-10-08",
        "sinceWatching": true,
        "best": 41
      }
    },
    "answer": "FullEnrich API + MCP scores 64.7 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics.",
    "b": {
      "slug": "retriever",
      "name": "Retriever",
      "vendor": "Retriever",
      "vendorUrl": "https://retriever.run",
      "company": "retriever.run",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Retriever is a hosted prospecting agent that finds and qualifies companies and contacts, enriches them with emails and phone numbers, and runs email and LinkedIn outreach, through a REST API and a remote MCP server.",
      "url": "https://www.anchorterminal.com/tools/retriever",
      "markdownUrl": "https://www.anchorterminal.com/tools/retriever.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/retriever.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/retriever.json",
      "dns": "retriever.grade.anchorterminal.com",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://api.retriever.run/mcp",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Bearer API key (`ret_live_...`) made in the app under Settings \u003e API keys after a browser signup, shown once. The MCP server also takes OAuth 2.1 with dynamic client registration and PKCE, and the access token it issues is an ordinary API key named after the connection. No scopes or expiry were found: a key works as its creator in that person's organisation. Keys are revoked one by one in Settings; removing a connector doesn't revoke its key. The MCP docs also accept the key in the URL as `?api_key=`, with a warning about logs.",
      "pricing": "paid",
      "pricingNotes": "Starter from $80 a month billed quarterly for 6,000 credits ($0.0134 a credit), up to 40,000 credits a month, with one-off top-ups and credits kept 12 months. Email senders $2 each or $30 for unlimited, LinkedIn senders $10 an account. Credits per action are published, a work email 4 to 12, a phone 15 to 60, a company 0.5 to 2. Enterprise is through sales. No free tier or no-card trial was found; the terms say only that free tiers may be offered.",
      "priceSummary": "$0.0134 / credit",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the pricing page, the docs, llms.txt or the OpenAPI file, 18 November 2026. Credits come with a subscription bought in the app.",
        "endpoints": []
      },
      "toolCount": 67,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://docs.retriever.run",
      "llmsTxt": "https://docs.retriever.run/llms.txt",
      "openapi": "https://docs.retriever.run/openapi.yaml",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.finder",
        "data.company",
        "web.search",
        "web.scrape"
      ],
      "tags": [
        "hosted",
        "mcp",
        "remote-mcp",
        "oauth",
        "openapi",
        "llms-txt",
        "closed-source",
        "paid",
        "subscription",
        "linkedin",
        "outreach",
        "no-status-page",
        "platform-rules",
        "eu"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 32,
        "grade": "F",
        "agentReady": false,
        "rank": 1455,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 21,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 5,
          "payments": 30,
          "reliability": 45,
          "schema": 82,
          "security": 23,
          "transparency": 49
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": -15,
        "warnings": [
          {
            "kind": "platform-rules",
            "name": "Breaks the rules of the platforms it acts on",
            "text": "Retriever connects a customer's LinkedIn accounts and sends invitations, messages, profile visits and post likes from them on a schedule, with messages a model writes, which LinkedIn's rules on automated activity forbid.",
            "deduct": -15,
            "since": "2026-11-18",
            "sources": [
              "https://docs.retriever.run/mcp/tools.md",
              "https://retriever.run/pricing",
              "https://www.linkedin.com/help/linkedin/answer/90586",
              "https://www.linkedin.com/help/linkedin/answer/a1341387"
            ]
          }
        ],
        "verdict": "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.",
        "bestFor": "A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.",
        "strengths": [
          "OpenAPI 3.1 file, llms.txt and Markdown docs, with an errors page of stable codes and the action to take for each",
          "Remote MCP server with OAuth 2.1, dynamic client registration and PKCE, so a client connects without pasting a key",
          "Rate limits published per key and class (30 a minute for runs, 120 for services, 600 for reads and MCP messages), with Retry-After on 429",
          "Idempotency keys on run creation and a recipe for safe retries, plus read-only, destructive and idempotent hints on the MCP tools",
          "Credits per action and the dollar price per credit published without a login"
        ],
        "weaknesses": [
          "Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted",
          "No status page, changelog, security.txt, disclosure policy or certification found",
          "Keys have no scopes or expiry, and the MCP docs accept the key in the URL as `?api_key=`",
          "No free tier or trial without a card found; access needs a browser signup and a subscription from $80 a month",
          "The terms and privacy policy name only \"Retriever\" under French law, with no company number or address, and the privacy policy doesn't mention connected LinkedIn or email accounts"
        ],
        "agentNotes": [
          "Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account",
          "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",
          "Run `getEmail`, `getPhoneNumber` and `webResearch` through `service_batch_execute`, even for one person; `service_execute` refuses them",
          "Check `credits` before a paid run, and call `service_inspect` for a service's `thingsToKnow` and credit cost before executing it",
          "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"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "F",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 32
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 5,
          "payments": 30,
          "reliability": 45,
          "schema": 82,
          "security": 23,
          "transparency": 43
        },
        "provenanceScore": 54,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -s https://api.retriever.run/credits -H \"Authorization: Bearer $RETRIEVER_API_KEY\"",
        "claudeCode": "claude mcp add --transport http --scope user retriever https://api.retriever.run/mcp",
        "config": {
          "mcpServers": {
            "retriever": {
              "url": "https://api.retriever.run/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/retriever"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Credit, Starter plan",
          "unit": "credit",
          "usd": 0.0134,
          "note": "$80 a month billed quarterly for 6,000 credits"
        },
        {
          "item": "Work email found",
          "unit": "tx",
          "usd": 0.06,
          "note": "4 to 12 credits, about $0.06 to $0.18 per the pricing page"
        },
        {
          "item": "Phone number found",
          "unit": "tx",
          "usd": 0.22,
          "note": "15 to 60 credits, about $0.22 to $0.89 per the pricing page"
        },
        {
          "item": "LinkedIn sender",
          "unit": "account-month",
          "usd": 10,
          "note": "Per connected LinkedIn account"
        }
      ],
      "provenance": {
        "legalEntity": "Retriever",
        "domain": "retriever.run",
        "domainRegistered": "2026-04-07",
        "endpointOnVendorDomain": true,
        "terms": "https://retriever.run/terms",
        "privacy": "https://retriever.run/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The terms and privacy policy, both last updated 30 August 2026, name the entity only as Retriever, choose French law and the Paris courts, and give emma@retriever.run as the contact. No company number, address or register entry was found; the French company register (annuaire-entreprises.data.gouv.fr) answered with a bot check, so it wasn't searched.",
          "retriever.run/robots.txt allows every crawler. docs.retriever.run publishes rules that didn't close the pages read. The site carries a content-signals preamble in robots.txt with no ai-input=no.",
          "RDAP gives retriever.run a registration date of 7 April 2026.",
          "/.well-known/security.txt answered 404. No status page or changelog is linked from the site or the docs.",
          "The privacy policy names Vercel, Railway, Supabase, Anthropic and OpenAI as examples of subprocessors and says personal data isn't sold. It doesn't cover the LinkedIn and email accounts customers connect, or the data providers named on the pricing page."
        ],
        "score": 54
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/retriever.json",
      "live": {
        "slug": "retriever",
        "probe": {
          "target": "https://api.retriever.run/mcp",
          "method": "get",
          "lastAt": "2026-11-18T21:51:12.571692585Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 193,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 201,
          "p95ms24h": 385,
          "samples24h": 172,
          "samples30d": 172,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 172,
              "ok": 172
            }
          ],
          "since": "2026-11-18T04:42:08.539827226Z"
        },
        "securityTxt": {
          "url": "https://retriever.run/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:31:40.595836687Z"
        },
        "llmsTxt": {
          "url": "https://docs.retriever.run/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:58.22750683Z"
        },
        "pages": [
          {
            "url": "https://retriever.run/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:43.303154652Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "df5f8e8262ec"
          },
          {
            "url": "https://retriever.run/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:45.492573613Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "7d5324c0992b"
          }
        ],
        "updatedAt": "2026-11-18T21:52:45.492573613Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 43,
        "category": "maintenance",
        "leads": "fullenrich",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from `server.json` and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.",
          "b": "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."
        },
        "scores": {
          "a": 48,
          "b": 5
        }
      },
      {
        "by": 34,
        "category": "security",
        "leads": "fullenrich",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Bearer API key for REST, no scopes found. The MCP signs in with OAuth and holds no static secret in the client. Webhooks are signed with HMAC-SHA1 keyed with the API key itself (20 of 30). The MCP isn't read-only, and confirmation before enrichment is recommended but left to the client. Workspace admins can set monthly credit limits per member, which block further credit-consuming MCP actions, and the skills add a confirmation before any sequencer change and honour opt-out and do-not-contact signals (10 of 20). Results are mostly structured contact fields (8 of 15). A free credits endpoint, and per-member usage views that include MCP activity, no per-call log found (7 of 15; was 5, aligned with people-data-labs' usage view). SOC 2 Type 2 per the trust page, with the report on request, vulnerability reports to support@fullenrich.com per the repository's SECURITY.md, security.txt 404 on 4 November, no bug bounty (12 of 20, as people-data-labs). 20+10+8+7+12 = 57.",
          "b": "The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as `?api_key=` (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0)."
        },
        "scores": {
          "a": 57,
          "b": 23
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "fullenrich",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.",
          "b": "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)."
        },
        "scores": {
          "a": 60,
          "b": 30
        }
      },
      {
        "by": 25,
        "category": "reliability",
        "leads": "fullenrich",
        "name": "Reliability",
        "reasons": {
          "a": "Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says \"No incidents reported\" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code `error.rate.limit` and the message \"Too many requests. Try again in 1m\", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.",
          "b": "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 \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10)."
        },
        "scores": {
          "a": 70,
          "b": 45
        }
      },
      {
        "by": 19,
        "category": "transparency",
        "leads": "fullenrich",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service with terms naming FullEnrich Corp. The skills and registry repo is MIT (15). The privacy policy (updated 20 August 2026, per the 1 October check) gives retention periods (3 years from last contact for prospects, 25 months for service improvement), legal bases and SCC or DPF transfers, and points rights requests to support@fullenrich.com. It doesn't say whether people returned by enrichment are covered, and the trust page says enrichment uses data providers it doesn't name, most acting as independent controllers. An opt-out page exists at fullenrich.com/optout (18 of 30). v1 and v2 APIs run side by side with no dated deprecation found (3 of 20). A sub-processor list is published, and the trust page now states that the hosting provider, DigitalOcean, hosts data in the European Union, with transfers outside the EEA disclosed (20 of 20; was 14 with hosting locations not stated). 15+18+3+20 = 56.",
          "b": "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)."
        },
        "scores": {
          "a": 68,
          "b": 49
        }
      },
      {
        "by": 9,
        "category": "ergonomics",
        "leads": "retriever",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "13 MCP tools with short descriptions. Search returns a free preview of 10 results plus a count, and bulk output goes to CSV or JSON exports rather than the chat (17 of 25). Structured filters for people and companies, single-record lookups and export endpoints (16 of 20). The OpenAPI file documents error codes per operation, 20 named codes in all, for missing fields, an enrichment still in progress, unknown keys and the rate limit, which an agent can act on (14 of 20; was 8). Asynchronous enrichment with polling or a signed webhook, identical inputs within 3 months return without a new charge, and the MCP guide asks for a balance check and confirmation before paid steps. No tool annotations confirmed (12 of 20). No official SDKs found (7 of 15). 17+16+14+12+7 = 66.",
          "b": "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)."
        },
        "scores": {
          "a": 66,
          "b": 75
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "FullEnrich",
        "b": "Retriever",
        "name": "Vendor"
      },
      {
        "a": "https://app.fullenrich.com/api/v2",
        "b": "https://api.retriever.run/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, Streamable HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "13",
        "b": "67",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "io.github.FullEnrich/fullenrich",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-08-27",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2026-08-20",
        "b": "2026-08-30",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-20",
        "b": "2026-08-30",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "3.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "FullEnrich API + MCP scores 64.7 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics.",
        "question": "Which is better for AI agents, FullEnrich API + MCP or Retriever?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do FullEnrich API + MCP and Retriever need an API key?"
      },
      {
        "answer": "Yes. FullEnrich API + MCP has a hosted endpoint at https://app.fullenrich.com/api/v2 and Retriever at https://api.retriever.run/mcp.",
        "question": "Can an agent call FullEnrich API + MCP and Retriever without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 70 against 45",
          "Security \u0026 auth, 57 against 23",
          "Payments \u0026 pricing, 60 against 30",
          "Maintenance \u0026 community, 48 against 5",
          "Transparency \u0026 trust, 68 against 49"
        ],
        "also": [
          "Free to start without a card",
          "No incidents deducted, where Retriever loses 15 points for them"
        ],
        "goodFor": "Maximising find rate on known contacts, especially mobiles, without a long-term contract.",
        "slug": "fullenrich",
        "watchFor": "Enrichment sources are data providers the vendor doesn't name"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 82 against 76",
          "Agent ergonomics, 75 against 66"
        ],
        "also": null,
        "goodFor": "A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.",
        "slug": "retriever",
        "watchFor": "Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted"
      }
    ],
    "history": {
      "fullenrich": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 62.2,
          "fromGrade": "B",
          "to": 64.7,
          "toGrade": "B"
        },
        {
          "causes": [
            "evidence",
            "correction"
          ],
          "date": "2026-11-04",
          "delta": 2.5,
          "from": 59.7,
          "fromGrade": "C",
          "to": 62.2,
          "toGrade": "B"
        },
        {
          "causes": [
            "evidence"
          ],
          "date": "2026-10-28",
          "delta": 0.1,
          "from": 59.6,
          "fromGrade": "C",
          "to": 59.7,
          "toGrade": "C"
        }
      ],
      "retriever": null
    },
    "job": {
      "capability": "lead.search",
      "name": "Lead search"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-fullenrich.json",
        "title": "Apollo API + MCP vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-retriever.json",
        "title": "Apollo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-fullenrich.json",
        "title": "Clay vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-retriever.json",
        "title": "Clay vs Retriever",
        "url": "https://www.anchorterminal.com/compare/clay-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.json",
        "title": "Coresignal API + MCP vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-retriever.json",
        "title": "Coresignal API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-fullenrich.json",
        "title": "Crustdata API + MCP vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-retriever.json",
        "title": "Crustdata API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-fullenrich.json",
        "title": "Dievio vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-retriever.json",
        "title": "Dievio vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich.json",
        "title": "Enrich Layer API + MCP vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.json",
        "title": "Enrich Layer API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich.json",
        "title": "Explorium AgentSource vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.json",
        "title": "Explorium AgentSource vs Retriever",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp.json",
        "title": "FullEnrich API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-gojiberry.json",
        "title": "FullEnrich API + MCP vs Gojiberry",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-gojiberry"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-hunter.json",
        "title": "FullEnrich API + MCP vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-hunter"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-leadmagic.json",
        "title": "FullEnrich API + MCP vs LeadMagic API + MCP",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-leadmagic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-lusha.json",
        "title": "FullEnrich API + MCP vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs.json",
        "title": "FullEnrich API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-prospeo.json",
        "title": "FullEnrich API + MCP vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach.json",
        "title": "FullEnrich API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-zoominfo.json",
        "title": "FullEnrich API + MCP vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.json",
        "title": "Fuse MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever.json",
        "title": "Gojiberry vs Retriever",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever.json",
        "title": "LeadMagic API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lusha-vs-retriever.json",
        "title": "Lusha API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/lusha-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.json",
        "title": "People Data Labs vs Retriever",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/prospeo-vs-retriever.json",
        "title": "Prospeo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/prospeo-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach.json",
        "title": "Retriever vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zoominfo.json",
        "title": "Retriever vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-fullenrich.json",
        "title": "Clearbit vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-retriever.json",
        "title": "Clearbit vs Retriever",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-fullenrich.json",
        "title": "Databar vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/databar-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-retriever.json",
        "title": "Databar vs Retriever",
        "url": "https://www.anchorterminal.com/compare/databar-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.json",
        "title": "Dropcontact API + MCP vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever.json",
        "title": "Dropcontact API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.json",
        "title": "FullContact vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever.json",
        "title": "FullContact vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.json",
        "title": "FullEnrich API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce.json",
        "title": "Retriever vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-retriever.json",
        "title": "Hunter API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-retriever"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 25,
        "edge": "fullenrich",
        "fullenrich": 70,
        "key": "reliability",
        "name": "Reliability",
        "retriever": 45,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 6,
        "edge": "retriever",
        "fullenrich": 76,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "retriever": 82,
        "weight": 13
      },
      {
        "by": 9,
        "edge": "retriever",
        "fullenrich": 66,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "retriever": 75,
        "weight": 13
      },
      {
        "by": 34,
        "edge": "fullenrich",
        "fullenrich": 57,
        "key": "security",
        "name": "Security \u0026 auth",
        "retriever": 23,
        "weight": 14
      },
      {
        "by": 30,
        "edge": "fullenrich",
        "fullenrich": 60,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "retriever": 30,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 43,
        "edge": "fullenrich",
        "fullenrich": 48,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "retriever": 5,
        "weight": 7
      },
      {
        "by": 19,
        "edge": "fullenrich",
        "fullenrich": 68,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "retriever": 49,
        "weight": 7
      }
    ],
    "summary": "FullEnrich API + MCP scores 64.7 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics. Both do lead search.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "fullenrich": "Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.",
      "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever",
    "json": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever.min.md"
  },
  "markdown": "FullEnrich API + MCP scores 64.7 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics. Both do lead search.\n\n- FullEnrich API + MCP: grade B, 64.7/100, rank #571 of 1557. Markdown https://www.anchorterminal.com/tools/fullenrich.md · JSON https://www.anchorterminal.com/api/v1/tools/fullenrich.json\n- 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\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 253 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md\n\n## Which one, for what\n\n### FullEnrich API + MCP (B)\n\nGood for: Maximising find rate on known contacts, especially mobiles, without a long-term contract.\n\nAhead on:\n- Reliability, 70 against 45\n- Security \u0026 auth, 57 against 23\n- Payments \u0026 pricing, 60 against 30\n- Maintenance \u0026 community, 48 against 5\n- Transparency \u0026 trust, 68 against 49\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where Retriever loses 15 points for them\n\nWatch for: Enrichment sources are data providers the vendor doesn't name\n\n### Retriever (F)\n\nGood for: A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.\n\nAhead on:\n- Schema \u0026 documentation, 82 against 76\n- Agent ergonomics, 75 against 66\n\nWatch for: Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted\n\n\n## Why the edge\n\n### Maintenance \u0026 community: FullEnrich API + MCP +43\n\n- FullEnrich API + MCP (48): Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from `server.json` and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.\n- 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.\n\n### Security \u0026 auth: FullEnrich API + MCP +34\n\n- FullEnrich API + MCP (57): Bearer API key for REST, no scopes found. The MCP signs in with OAuth and holds no static secret in the client. Webhooks are signed with HMAC-SHA1 keyed with the API key itself (20 of 30). The MCP isn't read-only, and confirmation before enrichment is recommended but left to the client. Workspace admins can set monthly credit limits per member, which block further credit-consuming MCP actions, and the skills add a confirmation before any sequencer change and honour opt-out and do-not-contact signals (10 of 20). Results are mostly structured contact fields (8 of 15). A free credits endpoint, and per-member usage views that include MCP activity, no per-call log found (7 of 15; was 5, aligned with people-data-labs' usage view). SOC 2 Type 2 per the trust page, with the report on request, vulnerability reports to support@fullenrich.com per the repository's SECURITY.md, security.txt 404 on 4 November, no bug bounty (12 of 20, as people-data-labs). 20+10+8+7+12 = 57.\n- Retriever (23): The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as `?api_key=` (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).\n\n### Payments \u0026 pricing: FullEnrich API + MCP +30\n\n- FullEnrich API + MCP (60): No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.\n- 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).\n\n### Reliability: FullEnrich API + MCP +25\n\n- FullEnrich API + MCP (70): Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says \"No incidents reported\" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code `error.rate.limit` and the message \"Too many requests. Try again in 1m\", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.\n- 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 \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).\n\n### Transparency \u0026 trust: FullEnrich API + MCP +19\n\n- FullEnrich API + MCP (68): Closed service with terms naming FullEnrich Corp. The skills and registry repo is MIT (15). The privacy policy (updated 20 August 2026, per the 1 October check) gives retention periods (3 years from last contact for prospects, 25 months for service improvement), legal bases and SCC or DPF transfers, and points rights requests to support@fullenrich.com. It doesn't say whether people returned by enrichment are covered, and the trust page says enrichment uses data providers it doesn't name, most acting as independent controllers. An opt-out page exists at fullenrich.com/optout (18 of 30). v1 and v2 APIs run side by side with no dated deprecation found (3 of 20). A sub-processor list is published, and the trust page now states that the hosting provider, DigitalOcean, hosts data in the European Union, with transfers outside the EEA disclosed (20 of 20; was 14 with hosting locations not stated). 15+18+3+20 = 56.\n- 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).\n\n### Agent ergonomics: Retriever +9\n\n- FullEnrich API + MCP (66): 13 MCP tools with short descriptions. Search returns a free preview of 10 results plus a count, and bulk output goes to CSV or JSON exports rather than the chat (17 of 25). Structured filters for people and companies, single-record lookups and export endpoints (16 of 20). The OpenAPI file documents error codes per operation, 20 named codes in all, for missing fields, an enrichment still in progress, unknown keys and the rate limit, which an agent can act on (14 of 20; was 8). Asynchronous enrichment with polling or a signed webhook, identical inputs within 3 months return without a new charge, and the MCP guide asks for a balance check and confirmation before paid steps. No tool annotations confirmed (12 of 20). No official SDKs found (7 of 15). 17+16+14+12+7 = 66.\n- 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).\n\n## Score by category\n\n| Category | Weight | FullEnrich API + MCP | Retriever | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 70 | 45 | FullEnrich API + MCP +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 76 | 82 | Retriever +6 |\n| Agent ergonomics | 13% | 66 | 75 | Retriever +9 |\n| Security \u0026 auth | 14% | 57 | 23 | FullEnrich API + MCP +34 |\n| Payments \u0026 pricing | 10% | 60 | 30 | FullEnrich API + MCP +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 48 | 5 | FullEnrich API + MCP +43 |\n| Transparency \u0026 trust | 7% | 68 | 49 | FullEnrich API + MCP +19 |\n| Negative events | ≤15 | 0 | -15 | |\n| **Total** | | **64.7 · B** | **32 · F** | |\n\n## Facts side by side\n\n| Fact | FullEnrich API + MCP | Retriever |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | FullEnrich | Retriever |\n| Hosted endpoint | `https://app.fullenrich.com/api/v2` | `https://api.retriever.run/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Tools exposed | 13 | 67 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.FullEnrich/fullenrich` | not listed |\n| Last release | 2026-08-27 | none |\n| Terms last updated | 2026-08-20 | 2026-08-30 |\n| Privacy policy last updated | 2026-08-20 | 2026-08-30 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Agent reviews | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### FullEnrich API + MCP\n\n- +2.5 on 13 November 2026: checklist\n- +2.5 on 4 November 2026 (C to B): new evidence, correction\n- +0.1 on 28 October 2026: new evidence\n\n### Retriever\n\nNo score change since it was listed.\n\n## Verdicts\n\n**FullEnrich API + MCP.** Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.\n\n**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.\n\n## Before you call either\n\n### FullEnrich API + MCP\n\n1. Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again\n2. Expect 30 to 90 seconds a contact. Use the webhook or poll `get_enrichment_results`\n3. Ask for mobiles only when needed. They cost 10 credits against 1 for a work email\n4. Call `list_industries` and `list_seniorities` before filtering search\n5. Use the 0-credit test contacts in the docs to check an integration\n6. On a 429 with `error.rate.limit`, wait a minute before retrying. The limit is 60 calls a minute on every endpoint\n\n### Retriever\n\n1. Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account\n2. 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\n3. Run `getEmail`, `getPhoneNumber` and `webResearch` through `service_batch_execute`, even for one person; `service_execute` refuses them\n4. Check `credits` before a paid run, and call `service_inspect` for a service's `thingsToKnow` and credit cost before executing it\n5. 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\n\n## Questions\n\n### Which is better for AI agents, FullEnrich API + MCP or Retriever?\n\nFullEnrich API + MCP scores 64.7 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics.\n\n### Do FullEnrich API + MCP and Retriever need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call FullEnrich API + MCP and Retriever without installing anything?\n\nYes. FullEnrich API + MCP has a hosted endpoint at https://app.fullenrich.com/api/v2 and Retriever at https://api.retriever.run/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fullenrich-vs-retriever.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fullenrich-vs-retriever.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fullenrich\", \"b\": \"retriever\"}`. From a terminal: `anchor compare fullenrich retriever`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fullenrich.json and https://www.anchorterminal.com/api/v1/tools/retriever.json\n\n## Other comparisons with FullEnrich API + MCP or Retriever\n\n- [Apollo API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/apollo-vs-fullenrich.md)\n- [Apollo API + MCP vs Retriever](https://www.anchorterminal.com/compare/apollo-vs-retriever.md)\n- [Clay vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clay-vs-fullenrich.md)\n- [Clay vs Retriever](https://www.anchorterminal.com/compare/clay-vs-retriever.md)\n- [Coresignal API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.md)\n- [Coresignal API + MCP vs Retriever](https://www.anchorterminal.com/compare/coresignal-vs-retriever.md)\n- [Crustdata API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-fullenrich.md)\n- [Crustdata API + MCP vs Retriever](https://www.anchorterminal.com/compare/crustdata-vs-retriever.md)\n- [Dievio vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dievio-vs-fullenrich.md)\n- [Dievio vs Retriever](https://www.anchorterminal.com/compare/dievio-vs-retriever.md)\n- [Enrich Layer API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich.md)\n- [Enrich Layer API + MCP vs Retriever](https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.md)\n- [Explorium AgentSource vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich.md)\n- [Explorium AgentSource vs Retriever](https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.md)\n- [FullEnrich API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp.md)\n- [FullEnrich API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/fullenrich-vs-gojiberry.md)\n- [FullEnrich API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-hunter.md)\n- [FullEnrich API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-leadmagic.md)\n- [FullEnrich API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-lusha.md)\n- [FullEnrich API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs.md)\n- [FullEnrich API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-prospeo.md)\n- [FullEnrich API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach.md)\n- [FullEnrich API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-zoominfo.md)\n- [Fuse MCP vs Retriever](https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.md)\n- [Gojiberry vs Retriever](https://www.anchorterminal.com/compare/gojiberry-vs-retriever.md)\n- [LeadMagic API + MCP vs Retriever](https://www.anchorterminal.com/compare/leadmagic-vs-retriever.md)\n- [Lusha API + MCP vs Retriever](https://www.anchorterminal.com/compare/lusha-vs-retriever.md)\n- [People Data Labs vs Retriever](https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.md)\n- [Prospeo API + MCP vs Retriever](https://www.anchorterminal.com/compare/prospeo-vs-retriever.md)\n- [Retriever vs RocketReach API](https://www.anchorterminal.com/compare/retriever-vs-rocketreach.md)\n- [Retriever vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/retriever-vs-zoominfo.md)\n- [Clearbit vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-fullenrich.md)\n- [Clearbit vs Retriever](https://www.anchorterminal.com/compare/clearbit-vs-retriever.md)\n- [Databar vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/databar-vs-fullenrich.md)\n- [Databar vs Retriever](https://www.anchorterminal.com/compare/databar-vs-retriever.md)\n- [Dropcontact API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.md)\n- [Dropcontact API + MCP vs Retriever](https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md)\n- [FullContact vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.md)\n- [FullContact vs Retriever](https://www.anchorterminal.com/compare/fullcontact-vs-retriever.md)\n- [FullEnrich API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.md)\n- [Retriever vs ZeroBounce](https://www.anchorterminal.com/compare/retriever-vs-zerobounce.md)\n- [Hunter API + MCP vs Retriever](https://www.anchorterminal.com/compare/hunter-vs-retriever.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "FullEnrich API + MCP vs Retriever",
        "url": ""
      }
    ],
    "description": "FullEnrich scores 64.7 (B) to Retriever's 32 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "FullEnrich API + MCP B 64.7",
      "Retriever F 32",
      "scores"
    ],
    "h1": "FullEnrich API + MCP vs Retriever",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/fullenrich-vs-retriever",
    "published": "2026-10-01",
    "section": "tools",
    "title": "FullEnrich vs Retriever for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever"
  },
  "tokens": {
    "markdown": 5250,
    "slim": 1080
  },
  "version": 1
}
