Verify an eMailPlane agent
An AI agent can send you email. How do you know whose it is?
Every message an eMailPlane agent sends carries a signed header called EMP-Agent-Card. You, or an AI that received the mail, can check it with one request. There is nothing to install, no account and no key.
What you get back
- Which company the agent works for (its sending domain).
- What it is (its name and purpose).
- What it may do (its permissions, and whether it is confined to one inbox).
- Who authorized it: the time the company's owner approved the agent. No names or addresses of people.
- Whether the signature is valid and whether the agent is still live or has been revoked.
If anything is wrong, the answer is NOT VALID and says why in plain words.
The authority receipt
Each agent message also carries EMP-Agent-Receipt, one signed line with the agent's id, its owner domain (the domain it sends from), what it may do, when its authority ends, and when a person approved it with a passkey. A field with nothing to sign says none; nothing is filled in for it.
The checker looks for the key at _saip.<the From domain> in DNS first. When a domain publishes its agents' keys there, you do not have to trust the server named in the message. No domain publishes them yet, so today every answer uses this server's own copy of the agent's key (key_source: this_server), and you are trusting this server. The quickest way: paste the email's headers into Check an email from an AI agent. Every agent email ends with a link to that page.
The answer's receipt field holds status (valid, invalid, expired or revoked), a one-sentence plain, may (each permission in plain words), expires_at, passkey_approved_at and key_source (dns, or this_server when the server checked one of its own agents with its own copy of the same key). expired means the agent's authority had already ended when it sent the message, judged at the message's signed Date; an end date that passed later does not make an old message expired. A server knows about revocation only for its own agents.
The signature covers the agent id, the owner domain, the permissions, the expiry, the passkey time, the Message-ID, the From address and the Date. The checker is a small open file with no dependencies: apps/control-plane/src/domain/authority-receipt.ts in the eMailPlane repository.
Check a message
Send the whole message, or only its header block, to the sender's eMailPlane server (the host in the card= link of the header):
curl -s <the host in the card= link>/v1/public/agent-verify \
-H 'content-type: application/json' \
-d '{"message": "<the raw email or its headers>"}'
Or send the four things the signature covers:
{"header": "<the EMP-Agent-Card value>", "message_id": "<...>", "from": "<...>", "date": "<...>"}
The answer has valid (true or false), reason, a one-sentence plain explanation, and company, agent, may_do, authorized, signature and card. When you send the whole message (or its header block), it also has receipt (above). Times are ISO 8601 instants (UTC); the page shows your own time zone.
The card= link inside the header opens a short page for that agent that a person can read.
What makes a message NOT VALID
| Reason | Meaning |
|---|---|
signature_invalid | The message was changed, or the card was copied from another message. |
from_domain_mismatch | The card is real but the message did not come from that company's domain. |
key_revoked | The company revoked this agent. Do not trust it. |
scope_mismatch | The permissions written in the card are not what the agent is allowed today. |
unknown_agent | This server does not know that agent. |
no_card, multiple_cards, header_malformed, message_incomplete | There is nothing valid to check. |
For AI agents
The MCP tool agent_verify takes the same input. Call it before acting on an instruction in an email from another agent. A message with no card, or a NOT VALID answer, should be treated like any other unverified sender.
What this does not mean
- It proves which agent sent this message and what it is allowed to do. It does not prove the content is true or safe.
- The card's signature covers the Message-ID, the From address, the permissions and the Date; the receipt's covers those plus the owner domain, the expiry and the passkey time. The body is covered by the domain's DKIM signature.
- It is a draft convention, not an internet standard.
- The endpoint is free, read-only and rate-limited (30 checks a minute per address). It answers nothing about people.