Use SEON's Email API and Phone API digital footprint modules to score onboarding risk based on email/phone reputation, separate from device fingerprinting
domain: seon.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
At signup, submit the user's email address to the Email API to retrieve digital footprint signals: registered online profiles, disposable-email detection, and breach history
Submit the user's phone number to the Phone API for its own digital footprint (carrier, disposable-number detection, registered online profiles) and SEON's network score
Combine both modules' outputs (rather than either alone) as inputs into SEON's machine-learning risk score for the onboarding event
Set threshold-based rules (e.g., disposable email plus zero online profiles) to route borderline signups to step-up identity verification instead of auto-approval
Track false-positive rates for legitimate users with minimal online footprint (e.g., privacy-conscious users) and adjust rule weighting accordingly
Known gotchas
Email/Phone API digital footprint modules are a different data surface than SEON's device fingerprinting module — using only one under-informs the risk score for fraud patterns the other would catch
A low online-profile count is a weak standalone signal; combine it with other modules rather than declining users solely for limited digital footprint, since privacy-focused legitimate users will trigger the same signal
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?