What is Gork mail (also searched as Grokmail or gork.email)?

Gork mail (gork.email, often spelled Grokmail or Grok mail) is programmable email infrastructure designed specifically for AI agents, LLMs, and autonomous workflows. It provides real email addresses, API & MCP access, signed webhooks, and deliverability guardrails.

How does Gork mail work for AI agents?

Gork mail gives each AI agent its own isolated email address via one API call or MCP tool. Agents can send emails, receive inbound messages via signed webhooks, search conversation history, and manage threads.

Can I use Gork mail with Claude Code, Cursor, or LangChain?

Yes. Gork mail ships a native Model Context Protocol (MCP) server. Running npx -y -p @gork/sdk gork-mcp gives Claude, Cursor, Goose, or Windsurf 13 native email tools.

Back to all blueprints

Templates · Agentic Commerce / Autonomous Purchasing & Order Tracker

Agentic Commerce Agent (Purchasing & Receipts)

Completes online purchases, receives merchant order confirmations, and extracts digital receipts.

Create handle All blueprints

Operational Bottleneck

When an AI agent buys items online (AWS credits, office hardware, travel bookings), the merchant sends confirmation emails, 3D Secure verification codes, and tracking numbers. Without an inbox, the transaction is flying blind.

E-commerce transactional receipts use complex nested HTML tables, dynamic tracking widgets, and embedded images that break standard text scrapers.

Gork Infrastructure Layer

Structured <90ms Delivery

Gork threads every order email and stores every PDF invoice in object storage. Your agent parses receipts and tracking numbers from the bodies — Gork keeps the conversation and the files together.

Execution Artifacts

System prompt, SDK code & webhooks

Copy the system prompt directly into your model context (Claude, ChatGPT, or custom orchestrator).

system-prompt.txt

1You are an Autonomous Agentic Commerce Assistant.
2Your mission is to monitor merchant receipts and order confirmations for purchases executed by our internal automation agents.
3
4TASKS:
51. Receipt Extraction: Extract Merchant Name, Order Number, Total Charged, Currency, and Estimated Delivery Date.
62. Tracking Code Ingestion: Detect carrier tracking links (UPS, FedEx, DHL, USPS) and dispatch a tracking webhook to the logistics monitor.
73. Anomaly Flagging: If an order receipt arrives for an unrecognized charge (> $250 without a corresponding internal purchase intent ID), alert the security team immediately.
8
9OUTPUT JSON:
10{
11  "merchant": string,
12  "orderNumber": string,
13  "totalAmount": number,
14  "currency": string,
15  "trackingNumber": string | null,
16  "carrier": string | null,
17  "verified": boolean
18}