Skip to main content

Give your AI agent an address of its own

An agent that has to borrow a human mailbox is an agent with a person in the loop. Gork gives each agent its own address under @try.gork.email or your verified custom domain, and keeps that address stable across jobs, model changes, and redeploys.

Real Address

Every agent gets an address under @try.gork.email (or your verified custom domain) that can send, receive, and hold a conversation.

Thread Memory

GET /v1/threads/{id} returns the conversation in order, so your agent answers with the history behind it instead of guessing from one message.

Signed Webhooks

email.received fires as soon as mail lands — HMAC-SHA256 signed, retried with exponential backoff, with a delivery log.

Inbox-Scoped Keys

Issue a key that can only read, send, and thread mail for one address. Rotate or revoke it from the dashboard.

Step 1: Provision the agent identity

TypeScript

Step 2: Receive mail

Subscribe a webhook to email.received:
cURL
The payload carries the message, its thread, and a classification of who sent it:
sender.kind is human, agent, or automated, derived from automation headers and subject patterns. An automated sender is usually an out-of-office reply — branch on it before your agent answers.

Step 3: Reply in-thread

Verify the X-Gork-Signature header first (see Verify webhook requests), then pull the thread and answer it:
TypeScript
A reply sent without inReplyTo arrives as a brand-new email in the recipient’s client.

Search across inboxes

GET /v1/messages?q= runs a case-insensitive search across subject, body, sender, and recipients, scoped to the inboxes your key can access (see Search Messages). Use it to give an agent recall over everything it has ever received without keeping its own index.

MCP: identity as native agent tools

Agents running through Claude Code or Cursor get the same surface as MCP tools:
Then prompt your agent:
“Create an inbox for sdr-alex, then watch it, summarize anything that arrives, and reply in-thread to anyone asking for a demo.”

What agents should not use email for

Email delivery is best-effort. Gork does not offer a latency guarantee, so do not route login-critical one-time passcodes or 2FA codes through an agent inbox. See Terms.
Inbound messages are stripped of executable markup (<script>, <iframe>, inline event handlers, javascript: URLs) before storage, while the raw MIME is archived to object storage.