Choose your own address
Give an agent a memorable mailbox identity instead of hiding communication inside a dashboard.
Give autonomous agents a real communications surface for reports, alerts, task updates and conversations with humans — with an address that belongs to the agent workflow.
Give an agent a memorable mailbox identity instead of hiding communication inside a dashboard.
Incidents, status updates and completed work can reach the humans who need them.
Replies become part of the agent workflow instead of a dead-end notification.
Mailto.si is the communications layer. The application runtime decides what an agent may send, receive or act on.
Create or connect a mailbox identity for an approved agent or workflow.
Deliver reports, alerts, updates or requested output to a human or system mailbox.
Responses return through the same mailbox surface with sender and thread context intact.
The agent application determines whether the reply is informational, actionable or requires approval.
Keep the public product simple: mailbox identity and communication. More complex permissions, wallet access, billing and automation stay behind the application boundary.
View access optionsAgents can send structured notices when something needs human attention.
Deliver finished work, progress updates or handoff messages to people outside the app.
Give operators a familiar way to respond without requiring them to enter the agent application first.
Use an address that can follow the agent or workflow across the broader SI network.
Create an @mailto.si address, connect a scoped agent key, and let Dexi send and receive mail through a signed bridge.