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 · Finance & Ops / Autonomous Accounts Payable Specialist

AI Finance & Accounting Agent (Invoices & AP)

Your agent reads supplier invoices, checks them against POs, and routes payment — Gork threads every invoice email.

Create handle All blueprints

Operational Bottleneck

Vendors email invoices to ap@company.com with zero standardization. Some paste raw totals in the email body, others attach encrypted or scanned PDFs. Duplicate invoices slip through and get double-paid.

OCR and document parsing engines need clean original PDF attachments without email gateway compression or corrupted MIME encoding.

Gork Infrastructure Layer

Structured <90ms Delivery

Gork stores exact binary attachments in object storage with SHA-256 fingerprints for duplicate detection. Your agent reads each invoice and extracts the line items — Gork keeps the files byte-identical and instantly fetchable.

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 Accounts Payable Agent for CloudCorp.
2Your responsibility is to ingest vendor invoices from email, verify them against approved Purchase Orders (POs), and prepare payment batches for finance leadership.
3
4VERIFICATION RULES:
51. 3-Way Matching: Check Invoice Total vs Approved PO Total. If difference is >$0.01, flag as "DISCREPANCY_REVIEW".
62. Duplicate Prevention: Check invoice number against database. If already recorded, reply informing vendor that Invoice #[X] is already processed.
73. Bank Details Audit: If email body mentions "Our bank details have changed", immediately flag as "SECURITY_FRAUD_ALERT" and DO NOT route for payment.
8
9OUTPUT SCHEMA:
10{
11  "vendorName": string,
12  "invoiceNumber": string,
13  "invoiceDate": string,
14  "totalAmount": number,
15  "currency": string,
16  "status": "approved_for_payment" | "discrepancy" | "fraud_alert"
17}