Bouncer is an email verification and validation service that helps ensure email deliverability by verifying email addresses through real-time and batch processing APIs.
Bouncer is an email verification and validation service that helps ensure email deliverability by verifying email addresses through real-time and batch processing APIs. On Nagent, Bouncer is exposed as a fully-configurable email integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Bouncer into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Bouncer to automate the kinds of tasks email 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 Bouncer 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 Bouncer, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BOUNCER_CHECK_TOXICITY_LIST_JOB_STATUSTool to check the status of a specific toxicity list job. Use after creating a toxicity list job to poll its status until completion.
Input parameters
Unique identifier of the toxicity list job to query
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
BOUNCER_CREATE_BATCH_REQUESTInitiates an asynchronous batch email verification request. Use when you have multiple emails to verify. Returns a batch ID for tracking - use BOUNCER_GET_BATCH_RESULTS to retrieve verification results after processing completes, or provide a callback URL.
Input parameters
List of email objects to verify in the batch
Webhook URL to receive a POST notification when batch processing completes. The callback will include the batchId and final status.
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
BOUNCER_CREATE_TOXICITY_LIST_JOBTool to create a toxicity analysis job for a list of email addresses. Use when you need to batch-process toxicity checks for multiple emails at once.
Input parameters
List of email addresses to analyze for toxicity
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
BOUNCER_DELETE_BATCH_REQUESTDeletes a batch email verification request and all associated emails and results. Use when you need to permanently remove batch data. This operation is idempotent - calling it multiple times on the same batch ID is safe and returns success. Data is automatically deleted by Bouncer after 60 days if not deleted manually.
Input parameters
The unique identifier of the batch to delete. This is the batchId returned when creating a batch request.
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
BOUNCER_DELETE_TOXICITY_LIST_JOBTool to delete a specific toxicity list job. Use when you need to remove a completed or unwanted toxicity analysis job after confirming its ID.
Input parameters
The unique identifier of the toxicity list job to delete
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
BOUNCER_FINISH_BATCHTool to mark a batch verification process as finished early. Use when you need to stop batch processing before all emails are verified and reclaim credits for unprocessed emails. IMPORTANT: The batch must be in 'processing' status - cannot finish a batch that is 'queued' or already 'completed'.
Input parameters
Unique identifier of the batch to finish. Must be a batch currently in 'processing' status. Obtain this ID from the response of a Create Batch Request action.
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
BOUNCER_GET_BATCH_RESULTSTool to retrieve the results of a batch verification process. Use after submitting a batch to fetch all processed email verification outcomes. Note: If the batch is still processing, the API will return a 405 status indicating results are not yet available. Wait for the batch to complete before retrieving results.
Input parameters
Unique identifier of the batch to retrieve results for.
Filter which email statuses to include in results; one of: 'all', 'deliverable', 'risky', 'undeliverable', 'unknown'.
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
BOUNCER_GET_CREDITSTool to retrieve the current credit balance for the account. Use when you need to check available credits before performing verification operations.
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
BOUNCER_VERIFY_DOMAINTool to verify the validity and configuration of a domain. Use when you need to confirm the domain's MX records and catch-all behavior.
Input parameters
Domain name to verify (e.g., 'usebouncer.com').
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
BOUNCER_VERIFY_EMAILTool to verify a single email address in real-time. Use when validating email entry form inputs instantly.
Input parameters
Email address to verify in real-time.
Timeout for verification in seconds (default: 10).
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 74 agents privately built on Nagent that already use Bouncer.
Build on Nagent
Connect Bouncer 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 Bouncer, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Bouncer is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Bouncer 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 Bouncer 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 Bouncer event fires, the agent kicks off automatically.
Every Bouncer 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 Bouncer ships with 10 pre-built email actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Bouncer together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Bouncer-based workflows tailored to your business.