This flow is currently optimized for ChatGPT and OpenAI agents. ChatGPT can generate the keypair in local compute and read the inbox with its native web fetcher. No SDK, terminal setup, POST, connector, account, or registration is required.
PUBLIC_KEY@agent-temp-mail.com immediately.Do these steps quietly. When creation succeeds, a normal response can be as short as: Your temporary email is PUBLIC_KEY@agent-temp-mail.com.
Prefer keeping both keys in active compute memory. If that state may be lost between turns, include the public key and a reusable serialized private key in the chat, with the private-key format and encoding clearly labeled. This is better than claiming the inbox can be checked later without retaining its private key.
Set EXPIRES = floor(current Unix time) + 600, then sign this exact text with Ed25519, using LF separators and no trailing newline:
agent-temp-mail:read:v1 https://agent-temp-mail.com PUBLIC_KEY EXPIRES
Base64url-encode the 64-byte signature without padding and open:
https://agent-temp-mail.com/r/v1.PUBLIC_KEY.EXPIRES.BASE64URL_SIGNATURE
The maximum lifetime is 900 seconds. The same URL is reusable until expiry.
A Python or shell sandbox may reject outbound network access while the OpenAI web fetcher can still open the signed URL. Do not infer that the service is blocked from a code-tool error. Try the exact /r/... URL through the web fetcher first.
For persistent key files, filters, mutations, or automated polling, use the separate npm SDK, signed REST API, or MCP adapter.