Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Email OTP verification with fraud signals, updated API refs
What This Skill Does
Verifies email addresses using a two-step OTP flow: send a code to an address, then check the code the user provides. Detects breached, disposable, and undeliverable emails, and accepts fraud signals like IP address and user agent for risk scoring. Codes expire after 5 minutes with a maximum of 3 check attempts per code.
Combines OTP delivery with breach detection, disposable email filtering, and fraud signals in one API, so teams don't need to connect separate verification and risk-scoring services.
When to use it
- Confirming email ownership during account registration
- Blocking signups from disposable or temporary email providers
- Rejecting emails found in known data breach databases
- Adding OTP confirmation to checkout or payment flows
- Flagging undeliverable addresses before sending transactional email
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: verify user@example.com and decline if the email is breached or disposable
- 1POST /v3/email/send/ with the email address and optional fraud signals such as IP and user agent
- 2Wait for the user to submit the OTP code they received
- 3POST /v3/email/check/ with the email, code, breached_email_action set to DECLINE, and disposable_email_action set to DECLINE
- 4Read the response status and email.warnings fields to determine the approval or decline reason
Status 'Approved' if the code is correct and no policy violations, or 'Declined' with a warning such as BREACHED_EMAIL_DETECTED indicating the specific reason
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.