Email Validation Jobs
by Tuski in Email & messaging
Create an email validation job from a JSON list of addresses or CSV text (send exactly one). Poll its status, then fetch results as JSON or CSV. Billing counts only testable addresses, fixed at creation; unreachable, disposable and typo domains are free.
POST https://agents.tuski.ai/zcj/y01zd9v65ez7/api/v1/email-validation/jobs
Last 30 days
- Uptime
- 94.4%
- Response time
- 2.2 s typical, 4.6 s slowest 5%
- Last check
- 3 h ago
- Next check
- any minute now
How to call it
POST https://agents.tuski.ai/zcj/y01zd9v65ez7/api/v1/email-validation/jobs
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://agents.tuski.ai/zcj/y01zd9v65ez7/api/v1/email-validation/jobs
content-type: application/json
{
"emails": [
"[email protected]"
]
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
csv_text | string | No | CSV content containing the addresses. Send exactly one of emails or csv_text. |
emails | array of string (email) | No | Addresses to validate. Send exactly one of emails or csv_text. |
Example response
The listing has no example response.
Call it from code
The curl command shows the payment challenge.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://agents.tuski.ai/zcj/y01zd9v65ez7/api/v1/email-validation/jobs' \
-H 'content-type: application/json' \
--data-raw '{"emails":["[email protected]"]}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://agents.tuski.ai/zcj/y01zd9v65ez7/api/v1/email-validation/jobs' \
-H 'content-type: application/json' \
--data-raw '{"emails":["[email protected]"]}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeWe don't show code that pays this service: it uses a payment scheme other than exact, which needs a different client setup.
Security scan
- Payment address changed recently in payment
Payment address changed from 0xa7ceb58c7532756ac2946c706f07bbcf3ec79008 to 0x19624986fbaebefc8d7894fd2f02f11acf045eb8
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 3.5 s | $0.01 |
| 6 h ago | Expected HTTP 402, got 504 | 504 | 5.3 s | - |
| 10 h ago | Passed | 402 | 2.2 s | $0.01 |
| 14 h ago | Passed | 402 | 2.5 s | $0.01 |
| 18 h ago | Passed | 402 | 2.2 s | $0.01 |
| 22 h ago | Passed | 402 | 1.6 s | $0.01 |
| 25 h ago | Passed | 402 | 2.0 s | $0.01 |
| 29 h ago | Passed | 402 | 2.4 s | $0.01 |
| 32 h ago | Passed | 402 | 1.6 s | $0.01 |
| 36 h ago | Passed | 402 | 1.8 s | $0.01 |
| 40 h ago | Passed | 402 | 2.5 s | $0.01 |
| 43 h ago | Passed | 402 | 2.2 s | $0.01 |
| 47 h ago | Passed | 402 | 4.6 s | $0.01 |
| 2 days ago | Passed | 402 | 2.8 s | $0.01 |
| 2 days ago | Passed | 402 | 2.0 s | $0.01 |
History
| 14 Oct 2026 | Payment address changed from 0xa7ceb58c7532756ac2946c706f07bbcf3ec79008 to 0x19624986fbaebefc8d7894fd2f02f11acf045eb8 |
| 14 Oct 2026 | Payment address changed from 0x4f8fa86fb567d1e7dd0f472fc5975aa6a7af762b to 0xa7ceb58c7532756ac2946c706f07bbcf3ec79008 |
| 13 Oct 2026 | Payment address changed from 0x95ab27a6d82c396000e6218cd5c3462c20ccb025 to 0x4f8fa86fb567d1e7dd0f472fc5975aa6a7af762b |
| 13 Oct 2026 | Payment address changed from 0x6476bc62c84a8842ae76f9145802bbdba7bf2487 to 0x95ab27a6d82c396000e6218cd5c3462c20ccb025 |
| 13 Oct 2026 | Payment address changed from 0x6e1d0e82d533955f73bb8ee72a9eaa0cfcbf2b8c to 0x6476bc62c84a8842ae76f9145802bbdba7bf2487 |
| 13 Oct 2026 | Payment address changed from 0x3686853fe74f5687c7a144f67363bc24b947c079 to 0x6e1d0e82d533955f73bb8ee72a9eaa0cfcbf2b8c |
| 13 Oct 2026 | Payment address changed from 0xc6c526c3862f8aa53426d247b975872ea9e4018e to 0x3686853fe74f5687c7a144f67363bc24b947c079 |
| 13 Oct 2026 | Payment address changed from 0x18bd47843b8fc45b4689bd6f0d71be3a59d5341f to 0xc6c526c3862f8aa53426d247b975872ea9e4018e |
| 12 Oct 2026 | Payment address changed from 0xf654b18557759f5121eb5d576ff6820422b2743f to 0x18bd47843b8fc45b4689bd6f0d71be3a59d5341f |
| 12 Oct 2026 | Payment address changed from 0xe0a8bbb5e5b3a86cd5600fbf3d44c2cae06084d1 to 0xf654b18557759f5121eb5d576ff6820422b2743f |
| 12 Oct 2026 | Payment address changed from 0x57cf19d8a27956c2e0cb4ff2b05390e8aed93aa4 to 0xe0a8bbb5e5b3a86cd5600fbf3d44c2cae06084d1 |
| 12 Oct 2026 | Payment address changed from 0x6df799c7afe2b6e9373ffd1de6b91fa24b054052 to 0x57cf19d8a27956c2e0cb4ff2b05390e8aed93aa4 |
| 12 Oct 2026 | Payment address changed from 0xca71f61c957a5bcb44f18640cf85e0d566878fef to 0x6df799c7afe2b6e9373ffd1de6b91fa24b054052 |
| 12 Oct 2026 | Payment address changed from 0xabadc9c8bcee7780f12e6b9f51c8ea70b08ac6c8 to 0xca71f61c957a5bcb44f18640cf85e0d566878fef |
| 12 Oct 2026 | Payment address changed from 0x655c80b4c0559dc5b13c58da2b5de2109e78d8d1 to 0xabadc9c8bcee7780f12e6b9f51c8ea70b08ac6c8 |