primitive-inbox

Give your agent a real inbox: a managed *.primitive.email address that receives mail, plus the verbs to read it (primitive emails latest), wait for it (primitive emails wait), answer it (primitive reply), and run a handler on every message (primitive functions deploy). No SMTP, no DNS, no mail server to host.

When to reach for this

Use freely (no user confirmation needed):

• The user needs an address to receive replies, verification codes, alerts, or signups.
• You sent a message and need to watch for the response.
• You are building a workflow that reacts to inbound mail (parse it, trigger on it, route it).
• You need a managed/throwaway address for a signup or an email verification.
• Someone emailed your address and answering it is part of the task the user gave you (see Replying for when not to).

Ask the user first:

• Replying to a person when the user has not asked you to handle that mail, or when the reply could create a ticket, lead, or commitment.
• Signing the address up for a third-party service, newsletter, or anything with side effects on a human.
• Deploying a Function that auto-replies or takes action on inbound mail: confirm the behavior, and that it follows the rules in Replying, before it runs on real messages.