Use Signup Risk API to evaluate demo requests, contact forms, waitlists, and other inbound submissions before they enter your CRM or sales queue. Get an explainable allow, review, or block recommendation from one server-side API.
200 requests/month · No credit card required
Lead forms are easy to submit, but not every submission deserves the same routing or sales attention. Disposable inboxes, malformed domains, placeholder-style identity details, role accounts, and other registration context can help your application decide which submissions should flow directly into sales, which need additional review, and which should be suppressed.
Disposable email addresses can create short-lived submissions that add noise to CRM, demo, waitlist, or nurture workflows.
Placeholder-style identity details, questionable domains, or weak name-to-email alignment can justify additional review before a submission is treated as sales-ready.
Without an automated routing checkpoint, low-quality submissions can consume sales time, distort funnel metrics, and clutter CRM workflows.
A consumer mailbox, role address, or unfamiliar provider may still represent a legitimate lead. These attributes should inform routing, not automatically disqualify the submission.
Add Signup Risk API at form submission time so your application can route inbound leads using the evidence available before sales or marketing workflows begin.
Send the email address and optionally include the person’s name and submission IP for additional context.
Signup Risk API evaluates disposable-email usage, domain infrastructure, provider type, role addresses, typo domains, synthetic identity patterns, name alignment, and optional IP reputation.
Use the allow, review, or block recommendation to send lower-risk leads directly into normal sales workflows, route uncertain submissions for additional review, or suppress very-high-risk attempts according to your own policy.
Classify common consumer, business, education, government, and unknown email providers to add context to lead routing.
Identify shared or functional addresses such as sales@, support@, info@, billing@, or admin@ so your workflow can route them appropriately.
Detect confirmed, likely, and suspicious disposable-email usage that may justify additional scrutiny before a submission enters automated sales workflows.
Evaluate domain existence and mail-related DNS infrastructure (MX, SPF, DMARC, and reserved domains) while distinguishing authoritative findings from temporary lookup failures.
When a name is supplied, evaluate how well it aligns with the email address and whether the supplied identity appears plausible.
Detect known provider-domain typos and guarded near-match domains that may indicate a mistyped email address before the lead enters CRM.
Identify placeholder-style email patterns and other synthetic submission characteristics that may justify additional review.
When IP context is available, evaluate datacenter, VPN, proxy, or Tor usage as one part of the broader submission decision. Raw submission IPs are not returned in the API response.
Provider type and role-address status are context, not automatic disqualifiers. A Gmail address may represent a legitimate buyer, and a role address may represent a real business inquiry. Signup Risk API combines these findings with the rest of the available evidence rather than treating them as standalone verdicts.
Send the submission into the normal CRM or sales workflow when the available evidence contains few meaningful risk factors.
Route uncertain submissions for additional qualification, confirmation, enrichment, or manual review before assigning sales attention.
Suppress very-high-risk submissions before they create unnecessary CRM records, automated sequences, or sales tasks according to your own policy.
Visitor submits a demo, contact, waitlist, or lead form
Your backend sends email, optional name, and optional submission IP
Signup Risk API returns the decision, checks, explanation, and metadata
Your application routes the submission into the appropriate CRM or review workflow
Use the recommendation directly for simple routing, or inspect the check-level evidence to combine Signup Risk API with your existing lead-scoring, enrichment, CRM, or sales-qualification rules.
The goal is not to reject every unusual submission. It is to prevent sales and marketing workflows from treating every form fill as equally valuable when the available evidence supports different routing.
Evaluate submissions before disposable, malformed, placeholder-style, or otherwise higher-risk entries create unnecessary CRM records and automated workflows.
Keep lower-risk submissions moving while reserving additional qualification, confirmation, enrichment, or review for leads with stronger risk factors.
Help sales teams spend more time on submissions that deserve follow-up instead of manually sorting through obvious noise.
Signup Risk API recommends allow, review, or block; your application decides what those outcomes mean for CRM creation, assignment, nurture, enrichment, or suppression.
Add Signup Risk API to your inbound forms and start making explainable allow, review, or block decisions before submissions create CRM records, automated workflows, or sales tasks.
200 requests/month · No credit card required
