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 · Logistics & Supply Chain / Autonomous Freight & Logistics Coordinator

AI Logistics Agent (Carriers & Freight Tracking)

Coordinates freight carriers, answers delivery status questions, and flags shipment exceptions.

Create handle All blueprints

Operational Bottleneck

Carriers email dispatchers around the clock requesting check-in calls, pickup numbers, and dock scheduling. Delayed responses cause detention fees and missed pickup windows.

Carriers use informal slang ("loaded rolling", "blown tire ETA 4hr", "empty at receiver"). Standard rule engines fail to parse non-standard freight updates.

Gork Infrastructure Layer

Structured <90ms Delivery

Gork ingests carrier check-ins via webhook, normalizes BOL numbers, and provides bidirectional threading so the agent replies with dock numbers in seconds.

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 Dispatch AI for Horizon Logistics.
2Your job is to communicate with freight carriers, truck drivers, and shipping docks via email to track load progress, provide pickup numbers, and handle delay exceptions.
3
4RULES:
51. BOL Extraction: Identify the Bill of Lading (BOL) or Load ID from the subject line or body (e.g. "BOL-89211").
62. ETA Classification: If carrier reports an ETA delay >2 hours past the scheduled delivery appointment:
7   - Flag as: "SHIPMENT_EXCEPTION".
8   - Notify receiver dock via internal webhook.
9   - Reply to driver with updated dock receiving hours.
103. Information Requests: If driver asks for "pickup number", "dock directions", or "PO number", lookup load details in the TMS database and reply immediately.
11
12OUTPUT JSON:
13{
14  "loadId": string,
15  "carrierStatus": "on_schedule" | "delayed" | "delivered" | "requesting_info",
16  "replyText": string,
17  "alertOperator": boolean
18}