For AI builders
Building with Cursor, Claude Code, Lovable or Bolt? Paste one prompt and your app stops accepting addresses that bounce, catches typos like gmial.com, and never blocks a real user.
Sign up free and create an API key. No card. Use a vd_test_ key while you build.
Copy the prompt for your tool below. It includes the endpoint, the response shape and the rules.
Add VERIDOCK_API_KEY to your environment variables or project secrets, then try a signup with a typo.
Copy-paste prompts
Each prompt carries the API contract and the rules that keep real users from being blocked, so the tool has nothing to guess.
Works in: Cursor, Claude Code, Windsurf, Copilot
Add email verification to the signup flow in this project using the VeriDock API.
Find where a new user's email is submitted on the server (the signup route, server action or auth callback) and verify the address there before the account is created.
VeriDock API:
- GET https://app.veridock.io/v1/verify?email=<url-encoded address>
- Header: Authorization: Bearer <VERIDOCK_API_KEY>
- 200 response JSON: { "email", "status", "reason", "score", "suggestion", "checks": {...} }
- status is one of: deliverable, undeliverable, risky, unknown
- suggestion is a corrected address when there is a likely typo, otherwise null
- Errors: { "error": { "code", "message" } } with 401 (bad key), 402 (out of credits), 429 (too many at once; wait Retry-After seconds)
- Full reference: https://veridock.io/llms-full.txt
Rules:
- Call VeriDock only from server code. Read the key from the VERIDOCK_API_KEY environment variable and never send it to the browser.
- Block the signup only when status is "undeliverable". Show: "That email address doesn't look right. Please check it."
- If suggestion is not null, show "Did you mean <suggestion>?" with a button that fills it in.
- Allow "risky" and "unknown". Never block a signup because VeriDock timed out or returned an error: let the user through and log it.
- Give the request a 10 second timeout.
- Put the VeriDock call in one small function, verifyEmail(email), and add a test for it that stubs fetch.
- Add VERIDOCK_API_KEY to .env.example with a comment saying keys that start with vd_test_ return fixed results and use no credits.Works in: Lovable, Bolt, v0
Add email verification to the signup form using the VeriDock API.
Create a Supabase Edge Function called verify-email that takes { email } and calls VeriDock, then call that function from the signup form before creating the account. Store the key as the secret VERIDOCK_API_KEY. Do not call VeriDock from the browser.
VeriDock API:
- GET https://app.veridock.io/v1/verify?email=<url-encoded address>
- Header: Authorization: Bearer <VERIDOCK_API_KEY>
- 200 response JSON: { "email", "status", "reason", "score", "suggestion", "checks": {...} }
- status is one of: deliverable, undeliverable, risky, unknown
- suggestion is a corrected address when there is a likely typo, otherwise null
- Errors: { "error": { "code", "message" } } with 401 (bad key), 402 (out of credits), 429 (too many at once; wait Retry-After seconds)
- Full reference: https://veridock.io/llms-full.txt
Rules:
- Call VeriDock only from server code. Read the key from the VERIDOCK_API_KEY environment variable and never send it to the browser.
- Block the signup only when status is "undeliverable". Show: "That email address doesn't look right. Please check it."
- If suggestion is not null, show "Did you mean <suggestion>?" with a button that fills it in.
- Allow "risky" and "unknown". Never block a signup because VeriDock timed out or returned an error: let the user through and log it.
- Give the request a 10 second timeout.Works in: Any coding agent
Write a one-off script that verifies every email address in the users table with the VeriDock API and saves the result.
VeriDock API:
- GET https://app.veridock.io/v1/verify?email=<url-encoded address>
- Header: Authorization: Bearer <VERIDOCK_API_KEY>
- 200 response JSON: { "email", "status", "reason", "score", "suggestion", "checks": {...} }
- status is one of: deliverable, undeliverable, risky, unknown
- suggestion is a corrected address when there is a likely typo, otherwise null
- Errors: { "error": { "code", "message" } } with 401 (bad key), 402 (out of credits), 429 (too many at once; wait Retry-After seconds)
- Full reference: https://veridock.io/llms-full.txt
Rules:
- Read VERIDOCK_API_KEY from the environment.
- Run at most 2 requests at a time. On a 429, wait for the Retry-After header and retry.
- Add columns email_status and email_reason and write each result as it arrives, so the script can be stopped and resumed.
- Skip rows that already have a status. Do not delete or email anyone; only record the result.
- Print a count per status at the end.What the tool will write
export async function verifyEmail(email: string) {
try {
const res = await fetch(
`https://app.veridock.io/v1/verify?email=${encodeURIComponent(email)}`,
{ headers: { Authorization: `Bearer ${process.env.VERIDOCK_API_KEY}` }, signal: AbortSignal.timeout(10_000) },
);
if (!res.ok) return { allow: true, suggestion: null }; // never block on our error
const { status, suggestion } = await res.json();
return { allow: status !== "undeliverable", suggestion };
} catch {
return { allow: true, suggestion: null };
}
}Prefer a client library? Install veridock from npm or veridock-io from PyPI. See SDKs and integration guides for Next.js, React, Node.js, Python, PHP and Supabase.
Go further
FAQ
250 free checks to start, no card required. Upgrading later? Use WELCOME20 for 20% off your first paid month.