RealPhoneValidation offers real-time phone number validation services, providing information on connectivity, phone type, carrier, and more.
RealPhoneValidation offers real-time phone number validation services, providing information on connectivity, phone type, carrier, and more. On Nagent, Realphonevalidation is exposed as a fully-configurable phone & sms integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Realphonevalidation into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Realphonevalidation to automate the kinds of tasks phone & sms teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Realphonevalidation into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Realphonevalidation, with input parameters and output schema. Drop these into any step of an agent built in Helix.
REALPHONEVALIDATION_CHECK_FRAUDTool to check phone number for fraud risk using Fraud Check API. Provides a phone risk score and many actionable data points including phone type, carrier, location, and recommendation (block, flag, allow). Use when you need to identify possible fraudulent phone numbers. US numbers only.
Input parameters
10-digit US phone number, numeric digits only
Response format: 'json' or 'xml'. Defaults to 'json'. XML output is not supported by this tool.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REALPHONEVALIDATION_EMAIL_VERIFYTool to validate an email address and check connectivity and disposability. Use after gathering an email to ensure it's deliverable and not disposable.
Input parameters
Email address to verify
Unique API token provided by RealPhoneValidation
Response format: 'json' or 'xml'. Defaults to 'json'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REALPHONEVALIDATION_LOOKUP_DNCTool to check Do Not Call list status for US phone numbers. Determines if number is on National, State, or DMA Do Not Call lists, identifies cell vs landline, and checks for known TCPA litigators. Requires SAN number from FTC.
Input parameters
10-digit US phone number, numeric digits only
Your RealValidation API token
Response format: 'json' or 'xml'. Defaults to XML if omitted
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REALPHONEVALIDATION_RPV_ACTIVETool to determine if a phone number is active on a valid phone service provider. Use after collecting the user's phone number for real-time verification.
Input parameters
10-digit US phone number, numeric digits only
Unique API token provided by RealPhoneValidation
Response format. JSON or XML. XML output is not supported by this tool.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REALPHONEVALIDATION_RPV_REASSIGNED_NUMBER_LOOKUPTool to check if a phone number has been reassigned since a given consent date. Use when verifying number ownership status after obtaining user consent.
Input parameters
10-digit US phone number (digits only)
RealPhoneValidation API token
Response format: 'json' or 'xml'. Defaults to 'json'.
Date you received permission to contact in YYYY-MM-DD format
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REALPHONEVALIDATION_RPV_SCRUB_PLUSTool to scrub a phone number for connection status and type. Use to validate a US phone number's status and line type.
Input parameters
10-digit US phone number. Accepts formats like '7275555555', '727-555-5555', '(727) 555-5555', or '+17275555555'
API token provided by RealPhoneValidation
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REALPHONEVALIDATION_RPV_WIRELESS_IDTool to identify whether a US phone number is landline or wireless. Use when conducting TCPA compliance checks.
Input parameters
10-digit US phone number, numeric digits only
Your RealValidation API token
Response format: 'json' or 'xml'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REALPHONEVALIDATION_VALIDATE_PHONE_SCRUBTool to validate US phone numbers using budget-friendly Scrub API. Determines connectivity status quickly (under 2 seconds). Best for organizations with large lists/databases on tight budgets that only need connection status. Optional Iscell and Carrier fields available for additional charge.
Input parameters
10-digit US phone number, numeric digits only
Unique API token provided by RealPhoneValidation
Response format. JSON or XML. XML output is not supported by this tool.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REALPHONEVALIDATION_VALIDATE_PHONE_TURBO_STANDARDTool to perform real-time US phone validation using Turbo Standard API. Provides connection status and phone type (Mobile, Landline, VoIP). Optimized for web forms and apps when only connection status and phone type are needed. Faster than Turbo V3 when only basic validation is required. Returns results in about 2 seconds.
Input parameters
10-digit US phone number, numeric digits only
Unique API token provided by RealValidation
Response format: 'json' or 'xml'. Defaults to XML if omitted
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REALPHONEVALIDATION_VALIDATE_PHONE_TURBO_V3Tool to perform comprehensive real-time phone validation using Turbo V3 API. Returns connection status, phone type (landline, cell, VoIP), carrier ID, caller name (when available), and caller type (consumer, business). Use when complete phone data overview is required in web forms. US numbers only.
Input parameters
10-digit US phone number, numeric digits only
Response format: 'json' or 'xml'. Defaults to XML if omitted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 69 agents privately built on Nagent that already use Realphonevalidation.
Build on Nagent
Connect Realphonevalidation to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Realphonevalidation, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Realphonevalidation is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Realphonevalidation is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Realphonevalidation steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Realphonevalidation event fires, the agent kicks off automatically.
Every Realphonevalidation action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Realphonevalidation ships with 10 pre-built phone & sms actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Realphonevalidation together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Realphonevalidation-based workflows tailored to your business.