MoltSets API: a detailed buyer's breakdown.

MoltSets describes an identity-resolution and contact-enrichment API accepting an email address, LinkedIn URL, IP address, or a person’s name and company. Its public product page lists business and personal emails, mobile numbers, business profiles, and people and company search. The offering is API and MCP oriented rather than a conventional manual prospecting interface. That makes it relevant to workflows where an application already holds partial identity information and needs additional context. It should not be mistaken for a managed outbound service or a promise that every input resolves successfully.

The public API page documents examples including reverse email lookup, LinkedIn to best email, IP to company, and business-email search by name and company domain. These are distinct starting points for different operational situations: a form submission can begin with email, an approved professional profile can begin with a LinkedIn URL, and an account-analysis workflow can begin with an IP address. Returned information still needs interpretation. In particular, a company association from an IP lookup should not automatically be treated as identification of a specific individual or evidence of buying interest.

The developer overview specifies POST requests under a common tools base URL, JSON bodies, Bearer authentication, a Content-Type header, and a non-empty User-Agent header. The authentication page says requests without User-Agent are rejected with a 403 response before authentication is checked. This small implementation detail matters for custom clients that send minimal headers. Keys can be created and revoked through the application, and the documentation recommends separate keys for different environments or agents. No key values or private account material are included in this review.

The overview documents a consistent response envelope containing results, status, and metadata. Completed calls return HTTP 200, with status distinguishing a successful match from not_found; unmatched result fields may be empty or null. That means an integration cannot rely on HTTP success alone to determine whether a useful record was returned. A proposed CRM workflow should inspect the status and result fields, preserve existing values where no new information exists, and record an unmatched outcome without treating it as an application crash or inventing missing identity details.

The official documentation index explains that each email includes a last_validated_at field within a 90-day freshness window, but that timestamp can be null for catch-all domains or validation errors. It describes risk_score as a send-safety grade, not a measure of whether the address belongs to the person searched. A indicates validated deliverability, C indicates a catch-all domain, D represents negative evidence such as abuse or do-not-mail signals, and F means no evidence. Buyers should not collapse identity confidence, validation recency, deliverability, and permission into one supposedly definitive quality score.

MoltSets states that mobile numbers are carrier-validated in real time and that its mobile offering does not include landlines. Its documentation also describes multi-provider waterfalls, but the reviewed pages do not establish a complete named supplier list or a guaranteed match rate by geography. The product supports personal-email and audience-identifier use cases as well as business contacts. Those broader capabilities should not be imported indiscriminately into a B2B outreach program. Teams need a field-level policy deciding which data is appropriate for their geography, purpose, and legal obligations.

The public API page describes wiring the HTTPS API into Clay, n8n, a CRM, or a custom product. Separately, the official MCP server documentation explains access from Claude, Claude Code, and other compatible MCP clients. These are different implementation routes: a deterministic application can make REST requests, while an approved agent can use MCP tools within its permissions. Neither statement proves an existing SalesPutty connection or a turnkey connector for every CRM. Agent access also deserves explicit limits on data retrieval, retention, and onward sharing rather than unrestricted enrichment by default.

The homepage lists a free tier with 1,000 lifetime enrichment calls and 100 total search records, without a card requirement. Solo is $27 per month with 1,000 enrichment records and 500 search records per five-hour window. Pro is $97 per month with 15,000 enrichment records and 7,500 search records per five-hour window. Team is $397 per month with 150,000 enrichment records and 75,000 search records per five-hour window, plus a published personal-email allowance of 75,000 per week. The advertised unlimited plans are subject to fair use, not unconstrained instantaneous throughput.

The homepage separately advertises carrier-verified mobiles at 15 cents per mobile, so buyers should not assume every phone lookup is included in the base unlimited-data wording. MoltSets is a plausible fit for technical operators enriching inbound records, filling missing CRM fields, or building approved prospect lists through code or AI workflows. The trade-offs are implementation effort, window-based capacity limits, additional mobile costs, and the need to interpret risk signals correctly. This review does not claim hands-on tests, verified match-rate superiority, consent detection, guaranteed delivery, or guaranteed sales outcomes.

SalesPutty offers managed, lawful US and Canada B2B outreach, with a 14-day preparation period, an included CRM, unlimited users, and a contact dashboard. The focus is confirmed-interest warm leads, without guarantees. This service description does not mean a live integration with this vendor has been implemented or verified.