MyEmailVerifier for AI agents
Agents read MyEmailVerifier at once. Changes and sends are held for a person's approval by default.
About MyEmailVerifier
MyEmailVerifier checks individual email addresses for deliverability and risk signals such as disposable, role-based, catch-all, and greylisted status.
What an agent can do in MyEmailVerifier
Every MyEmailVerifier action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in MyEmailVerifier without asking first. 0 actions.
None in this connector.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 2 actions.
- Verify EmailVerify one email address for deliverability and return MyEmailVerifier's status, diagnosis, and risk flags. Each request consumes one verification credit.
- Verify EmailsVerify 1 to 5 email addresses serially and return one ordered outcome per input. Each provider request is expected to consume one verification credit; locally invalid and unattempted items consume non
Changes wait in Needs you
Changes and sends in MyEmailVerifier are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
MyEmailVerifier questions
Can an agent change data in MyEmailVerifier on its own?
Not by default. Changes and sends in MyEmailVerifier are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in MyEmailVerifier?
This connector lists 0 read actions. Reads run at once, without waiting for approval.
How does MyEmailVerifier connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.