Sanaf AI
Start free
Email

Bouncer, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Bouncer account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Email
  • Connects with a key
  • 9 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Bouncer is

Bouncer is an email verification and validation service that helps ensure email deliverability by verifying email addresses through real-time and batch processing APIs.

You paste in a key from your own Bouncer account. It is kept encrypted, and you can withdraw it from inside Bouncer whenever you like.

How a run works

One message in, the work done in Bouncer.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Bouncer. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Bouncer account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

9 tools it already has

What it can do in Bouncer

These are the ready-made tools your AI employee already has in Bouncer. It is not limited to them, but it never has to be taught these.

  • 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.
  • Create Batch RequestTool to initiate a batch email verification request. use when you have multiple emails to verify in one api call. returns a batch id and initial status.
  • 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.
  • Delete batch requestTool to delete a batch verification request. use when you need to remove all associated emails and results for a specific batch after confirming that the batch data is no longer re
  • 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.
  • Finish BatchTool to mark a batch verification process as finished. use after batch processing completes to stop further verifications and reclaim unused credits.
  • Get Batch ResultsTool to retrieve the results of a batch verification process. use after submitting a batch to fetch all processed email verification outcomes.
  • 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.
  • Verify EmailTool to verify a single email address in real-time. use when validating email entry form inputs instantly.
Access, and who is in charge of it

You stay the boss of your Bouncer account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Bouncer account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Bouncer is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Bouncer and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Bouncer

Can an AI employee really work inside Bouncer?
Yes. It signs in to your own Bouncer account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Bouncer?
No. Nothing moves and nothing is replaced. Your records stay in Bouncer, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Bouncer account?
You paste in a key from your own Bouncer account. It is kept encrypted, and you can withdraw it from inside Bouncer whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Bouncer?
It has 9 ready-made tools in Bouncer today, among them Check Toxicity List Job Status, Create Batch Request and Create Toxicity List Job. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Bouncer and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Bouncer and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Bouncer?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Bouncer is written down with what it did and when.