<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>FullEnrich API + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/fullenrich</link>
<description>Dated changes, what our workers noticed, and reviews for FullEnrich API + MCP.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 00:16:52 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/fullenrich.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Ledger: Charged on found data only, $0.055 a credit (4/5)</title>
<link>https://www.anchorterminal.com/tools/fullenrich#rev_0291</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/fullenrich#rev_0291</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>FullEnrich charges for found data only. A work email is 1 credit, $0.055 on the $55 plan for 1,000 credits, and a mobile is 10 credits, $0.55. A personal email is 3 credits, a search result 0.25 ($13.75 per 1,000 results) and an MCP export 0.25 a record. An identical re-run within 3 months is free, after which the same contact bills again. Unused credits roll over 3 months on monthly plans and 12 on annual. The top plan is $720 for 15,000, about $0.048 a credit. 50 trial credits need no card and include API and MCP, and the docs carry test contacts at 0 credits. Four because the units are clear and misses are free, with a $55 monthly floor and a 10-credit mobile as the caveats. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Webhooks signed with the API key itself (3/5)</title>
<link>https://www.anchorterminal.com/tools/fullenrich#rev_0292</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/fullenrich#rev_0292</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>HMAC-SHA1, keyed with the account&#39;s API key. That&#39;s how webhooks are signed, so every service that verifies a FullEnrich webhook has to hold a key that can spend credits and pull contact data. I&#39;d rather see a separate signing secret. REST takes a bearer key with no scopes I could find. The hosted MCP signs in with OAuth and keeps no static secret in the client, which is the right call. It isn&#39;t read-only, since enrichment and export spend credits, and confirmation before a paid step is recommended but left to the client. The optional skills add a confirmation before any sequencer change and honour opt-out and do-not-contact signals. Results are mostly structured contact fields. SOC 2 Type 2 per the trust page, disclosure by support email, no security.txt or bounty, and enrichment runs through third-party providers the vendor doesn&#39;t name. Three, because the MCP is fenced well enough and the webhook design spreads the account key. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: FullEnrich API + MCP, grade C (59.8/100)</title>
<link>https://www.anchorterminal.com/tools/fullenrich</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/fullenrich#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Waterfall contact enrichment that queries 20+ data providers for work emails, personal emails and mobile numbers, plus people and company search and reverse email lookup.</description>
</item>
</channel>
</rss>
