For ai agent builders
Agents need domain access, not your account.
Turn domain operations into tools an agent can safely call.
What breaks today
An agent can write and deploy an application, then stalls at the registrar login, DNS dashboard, or founder inbox. Sharing a root API key removes the human bottleneck by creating a security problem.
What changes with Domani
Domani gives the agent a narrow operating surface: approved operations, a spending budget, and an expiration window. The human keeps account ownership and a reviewable activity trail.
The workflow, end to end
Provision
Create an agent identity with a free inbox, or attach a custom domain when the project needs a public name.
Delegate
Issue a token for specific domain and email operation types, with spending limits and an expiry date.
Operate
Let the agent search, register, configure DNS, receive email, and connect hosting through structured tools.
Review
Inspect sensitive actions, approvals, costs, and state changes from one activity trail.
What Domani provides
MCP and agent skill
Expose domain workflows in the interfaces coding agents already understand.
Scoped credentials
Limit a token to a precise set of operation types and give it an independent expiration.
Safe financial actions
Apply per-purchase and monthly limits to paid domain operations.
Signed inbound events
Deliver email replies to an agent webhook without polling a human inbox.
The boundary that stays explicit
The agent never needs the owner account password or an unrestricted registrar key. Current token scopes limit operation types, not individual domains, so separate accounts are still the stronger boundary when an agent must only see one client's assets.
Questions teams ask
Concrete answers before you change a production workflow.
Does each agent need to buy a domain?+
No. Start with a free @domani.run inbox. Add a custom domain only when the agent or project needs a public name, website, or branded email address.
Can I revoke an agent without changing my own credentials?+
Yes. Agent tokens are separate from the account credential and can be limited by operation type, expired, or revoked independently.
Can the agent make purchases?+
Only if you grant a paid scope and configure the relevant limits. Purchase actions remain subject to the policies on that token and account.