Give your AI agent an identity on the internet
Autonomous agents hit a wall the moment a website asks for an email address: agents can’t check a human inbox. Gorkmail closes that loop. Your agent gets a real address it controls, and when a service sends a verification email, Gorkmail detects the OTP or magic link and delivers it as structured data — via webhook or a single API call.Real Address
Every agent gets an address under
@try.gork.email (or your verified custom domain) that can send, receive, and maintain conversations.Verification Intelligence
OTP codes and magic links are extracted from inbound mail after Agent Shield sanitization — cloaked or spoofed codes can’t poison the result.
Instant Webhooks
email.verification_detected fires the moment a verification email lands, HMAC-signed, with retries.One API Call
GET /v1/messages/:id/verification returns the code, link, expiry, and provider hint — no email parsing in your agent.Step 1: Provision the agent identity
TypeScript
Step 2: Subscribe to verification events
Register a webhook for theemail.verification_detected event:
cURL
Step 3: Complete the signup
Handle the webhook (verify theX-Gork-Signature HMAC header first — see the HMAC guide), then hand the code to your browser agent:
TypeScript
MCP: verification as a native agent tool
Agents running through Claude Desktop, Claude Code, or Cursor get verification as a first-class tool:“Create an inbox forsignup-bot, register an account on example.com using that address, then usegork_get_verificationto get the code and finish the signup.”
Fallback: poll the API
If webhooks aren’t an option, your agent can poll:TypeScript