For agent builders

Give your AI agents authority with boundaries, and a record.

An agent that sends email acts on your firm's behalf, so five things should be distinct: who the agent is, what it was permitted to do, what each message was checked against, who approved the consequential ones, and the evidence of what actually went out.  Wingmarked is that layer for agent email.  Each message is checked against the thread, the attachments and what your firm already promised; it then goes out from the sender's own Microsoft 365 mailbox, or waits for a named person.  Nothing is delivered until the check passes, and the wrong email is stopped before it is sent.

What it does for agent mail

  • The gateEvery message your agent sends through Wingmarked is checked before delivery: rules, your firm's policy, and an AI review that reads up to three earlier messages on the thread and the text of PDF and Word attachments.  The message then goes as written, gets a minimal exact fix, is held for a person, or is blocked.
  • No new commitmentAgent mail sends on its own only when the check passes it, it makes no new commitment to the recipient, and its category is switched on.  A new commitment is a date, an amount, an approval, a waiver, a denial or a term the firm has not already given that person.  Anything else holds for the person who owns that kind of decision.
  • Never delegableSome mail always waits for a person: fair housing, accommodation and assistance-animal requests, deposit deductions and itemizations, eviction, move-out and non-renewal notices, legal notices, and anything with legal exposure of medium or higher.  It is judged by the message's own words as well as the category your agent sends, so a wrong label never lets one through.  The list is code, not a setting.
  • Fail closedIf the automatic checks cannot run (a timeout, an AI outage, or only the rules ran), agent mail holds for a person with the sentence "Automatic checks could not run, so this waits for a person." Mail a person wrote follows the firm's own setting.  Agent mail never goes out unchecked.
  • CapsEach agent key has a daily send cap (200 by default) and a cap per recipient (5 a day by default).  Mail over a cap is held, not refused, so nothing is lost and nothing loops.  The key's owner hears about it once that day.
  • The pause buttonOne tap on the agent page pauses a key.  A paused key's mail holds for a person, and resuming the key does not release that mail on its own.  Pause and resume are on the audit log.
  • The ledgerThe agent page keeps a ledger of what went out for each person and what waits on them, by category.  Each decision owner gets one email a day listing both, skipped when both are empty.  Every message is marked as agent-sent in the record and in the audit log, which the database will not let anyone change.
  • Shadow firstBefore your agent sends anything, check_draft in shadow mode records what Wingmarked would have done with each draft and later matches it to what a person actually sent on the same thread.  Nothing is sent, held or announced.  Two weeks of that gives you a measured number in place of a guess.

Quickstart

  1. Sign in as your Microsoft 365 adminOpen /start and continue with Microsoft 365.  That creates your firm's Wingmarked with a 30-day trial of the Wingman plan, which includes the API and MCP, and runs the free 90-day audit, read only.  Nothing about your mail changes.
  2. Make an agent keyMake a key at /admin/api, then mark it as an agent key at /admin/agent so the agent rules above apply to it.  Send it as Authorization: Bearer followed by the key.
  3. Check drafts in shadowCall check_draft with mode shadow on every draft your agent writes.  The sender's address must be in one of your Microsoft 365 domains.  The agent page shows what Wingmarked would have sent and what it would have held, and why.
  4. Send through the gateWhen the shadow numbers say so, send with send_through_wingmarked or POST /v1/messages.  Sending needs the mail flow that /setup creates in your Microsoft 365, because delivery goes back through your own tenant, which signs the message with DKIM.  Poll the status URL to see whether it went or is held.
curl: check a draft in shadow
curl -s https://wingmarked.com/v1/check \
  -H "Authorization: Bearer $WINGMARKED_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "shadow",
    "category": "maintenance",
    "from": "Dana Lee <dana@yourfirm.example>",
    "to": ["marcus@client.example"],
    "subject": "RE: Water heater",
    "text": "Hi Marcus,\n\nThe plumber will be there Tuesday between 10 and 12."
  }'
# {"ok":true,"mode":"shadow","id":"...","recorded":true}
curl: preview the verdict
curl -s https://wingmarked.com/v1/check \
  -H "Authorization: Bearer $WINGMARKED_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "dana@yourfirm.example",
    "to": ["marcus@client.example"],
    "subject": "RE: Deposit",
    "text": "Hi Marcus,\n\nWe will return $2,400 of your deposit by Friday."
  }'
# {"ok":true,"verdict":"...","explanation":"...","findings":[...],"edits":[...],"timedOut":false,"wouldSend":...}
curl: send through the gate
curl -s https://wingmarked.com/v1/messages \
  -H "Authorization: Bearer $WINGMARKED_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "category": "maintenance",
    "from": "dana@yourfirm.example",
    "to": ["marcus@client.example"],
    "subject": "RE: Water heater",
    "text": "Hi Marcus,\n\nThe plumber will be there Tuesday between 10 and 12."
  }'
# 202 {"ok":true,"id":"...","status":"received","statusUrl":"https://wingmarked.com/v1/messages/..."}

curl -s "https://wingmarked.com/v1/messages/$ID" -H "Authorization: Bearer $WINGMARKED_KEY"
# {"status":"released",...} once it went, or {"status":"held_sender","explanation":"...",...} while it waits
TypeScript
const WM = "https://wingmarked.com";
const headers = {
  Authorization: `Bearer ${process.env.WINGMARKED_KEY}`,
  "Content-Type": "application/json",
};

const draft = {
  category: "maintenance",
  from: "Dana Lee <dana@yourfirm.example>",
  to: ["marcus@client.example"],
  subject: "RE: Water heater",
  text: "Hi Marcus,\n\nThe plumber will be there Tuesday between 10 and 12.",
};

// Shadow: Wingmarked records what it would have done.  Nothing is sent.
await fetch(`${WM}/v1/check`, {
  method: "POST",
  headers,
  body: JSON.stringify({ ...draft, mode: "shadow" }),
});

// Send: checked, then delivered from the sender's mailbox or held for a person.
const res = await fetch(`${WM}/v1/messages`, { method: "POST", headers, body: JSON.stringify(draft) });
const { id, statusUrl } = await res.json();
const status = await (await fetch(statusUrl, { headers })).json();
console.log(id, status.status, status.explanation);
Python
import os
import requests

WM = "https://wingmarked.com"
headers = {"Authorization": f"Bearer {os.environ['WINGMARKED_KEY']}"}

draft = {
    "category": "maintenance",
    "from": "Dana Lee <dana@yourfirm.example>",
    "to": ["marcus@client.example"],
    "subject": "RE: Water heater",
    "text": "Hi Marcus,\n\nThe plumber will be there Tuesday between 10 and 12.",
}

# shadow: Wingmarked records what it would have done.  nothing is sent.
requests.post(f"{WM}/v1/check", json={**draft, "mode": "shadow"}, headers=headers, timeout=30)

# send: checked, then delivered from the sender's mailbox or held for a person.
sent = requests.post(f"{WM}/v1/messages", json=draft, headers=headers, timeout=30).json()
status = requests.get(sent["statusUrl"], headers=headers, timeout=30).json()
print(sent["id"], status["status"], status.get("explanation"))

The MCP endpoint

POST /v1/mcp is an MCP server over Streamable HTTP: JSON-RPC 2.0, one request per POST, JSON responses, protocol version 2025-06-18.  It takes the same bearer key as the REST endpoints and offers the three tools below.  A tool's own refusal, such as a sender outside your domains, comes back as a tool result the model can read and act on.

https://wingmarked.com/v1/mcp
  • check_draftThe verdict Wingmarked would reach on a draft (pass, autofix, hold_sender, hold_reviewer or block), the findings with one plain sentence each, and the exact find-and-replace edits it would make.  Nothing is stored.  With mode shadow it records what it would have done and answers with the record's id only.
  • send_through_wingmarkedSends a message through the gate.  Returns an id and a status URL to poll.  Nothing is delivered until the check passes.
  • recallWhat the firm has already told a person, from its own sent mail: dates, amounts, terms and deadlines, each with the sentence it came from and the date.  Read it before writing to someone.
Claude Code
claude mcp add --transport http wingmarked https://wingmarked.com/v1/mcp --header "Authorization: Bearer wm_live_..."
  • ReviewersA reviewer tool's integration key gets one tool on the same endpoint, act_on_hold.  A reviewer who wants to work their own queue from Claude connects a separate server, /mcp/reviewer, which signs them in with OAuth instead of a key.

With any sending provider

  • Check, then send with what you havecheck_draft sends nothing, so it can sit in front of whatever sends your agent's mail today: Microsoft Graph, an SMTP server or a transactional email API.  Call it with the draft.  Send when the verdict is pass, or autofix after you apply the returned edits.  Otherwise give the draft to a person.  Treat timedOut as a reason to wait for a person, the way the gate does.
  • Who stops the mailWith your own provider, Wingmarked answers and your code decides.  The no-new-commitment rule, the never-delegable list, the caps, the pause button, fail closed and the ledger are enforced only on mail sent through Wingmarked.  A preview answers with the gate's verdict alone; shadow mode is where the agent rules are measured.
  • The sender's domainThe sender's address must be in one of the domains of the Microsoft 365 tenant your Wingmarked is connected to, for a check as for a send.  A draft from any other domain is refused.

Works with

  • Microsoft 365The hairpin: your tenant's transport rule sends outgoing mail to the Wingmarked relay, and the checked message goes back to your tenant, which signs it with DKIM and delivers it from the sender's own mailbox.
  • The API and MCP gatePOST /v1/check, POST /v1/messages and POST /v1/mcp, from any language or agent framework that can make an HTTPS request with a bearer key.
  • ClaudeAdd the MCP server to Claude Code with one command.  A reviewer can work their own queue from claude.ai, the desktop app or Claude Code.

Pricing

The 90-day audit is free: your Microsoft 365 admin signs in, and Wingmarked reads the last 90 days of sent mail, read only, and shows every email it would have stopped.  A new firm gets a 30-day trial of Wingman, which includes the API and MCP.  After the trial, Shadow is free forever and holds nothing, and the API is not part of it.  Gate is $12 per seat per month.  Wingman, with the API and MCP, is $29 per seat per month.  Senders are seats, with a minimum of 5; reviewers are free.  Mail never stops for non-payment.

Not built yet

  • Microsoft 365 firstSign-up without us is for Microsoft 365.  A firm on Google Workspace starts by writing to us.
  • A person grants access onceAn agent cannot sign up on its own.  A Microsoft 365 admin consents once, and an admin makes the key.
  • Categories are yoursWingmarked does not sort mail into categories on its own.  A message without one is general, and agent mail sends on its own only in a category an admin has switched on.
  • No request rate limit yetBeyond the send caps on agent keys, the API has no rate limit yet.  Use one key per agent so the record says which one sent what.

Security

How Wingmarked handles your mail: what is stored and for how long, the Microsoft permissions, who processes your data, and the audit log. Read the security page.

Read against the code on October 21, 2026.  Plain text for tools: /llms.txt and /llms-full.txt.