MailgentMailgent
Why Identity

Agents are the new users.
They need identity.

Humans need an email address, a password manager, and a phone for 2FA to operate on the internet. AI agents need the same primitives — purpose-built for autonomous, always-on operation. Mailgent is that infrastructure.

Agents operate with borrowed identities
and hardcoded secrets.

01

No accountability

When an agent sends an email or calls an API — who authorized it? Without identity, there's no delegation chain, no audit trail, no accountability.

02

No trust boundaries

In multi-agent systems, agents can't verify each other. Without identity, any process can impersonate any agent. Inter-agent trust is impossible.

03

No credentials management

API keys in .env files. 2FA disabled. One leaked credential compromises every service the agent touches. No rotation, no scoping, no encryption.

04

No communication channel

Agents use your personal Gmail or dump to a queue. No dedicated address, no DKIM signing, no threading. Emails land in spam.

05

No compliance path

FINRA, HIPAA, SOX, CMMC — regulators ask: 'Can you trace this AI action back to a human?' Without identity infrastructure, the answer is no.

06

No revocation

When an employee leaves, their agents keep running. When a credential leaks, there's no kill switch. No way to revoke access across all services at once.

The agent identity stack.

Humans have email, a password manager, and a phone for 2FA. Remove any one and most of the internet is inaccessible. Agents need the same stack — plus delegation chains and audit trails that trace every action back to the human who authorized it.

Human

Email address
Password manager
Phone for 2FA

Agent (Mailgent)

Inbox — DKIM-signed email
Vault — AES-256-GCM encrypted
TOTP — 2FA code generation
Delegation chain
Audit trail on every action

The delegation chain.
The feature regulators want.

Every regulation governing AI agents asks the same question: “Can you trace this action back to the human who authorized it?” Mailgent's delegation chain answers it for every email, credential access, and TOTP code. Cryptographically verifiable. Instantly revocable.

delegation-chain.ts
// The delegation chain on every action:
//
// Human (ops@novaworks.io)
//   └─ Org (novaworks)
//       └─ Identity (sales-agent-x8k2m)
//           └─ Action (email sent)
//
// Revoke the human?  → Org loses authorization.
// Revoke the org?    → All identities shut off.
// Revoke the identity? → All capabilities stop.
//
// One revocation. Complete shutdown. Zero orphaned access.
Compliance

Regulators are already asking.

Financial Services

FINRA 3110, SEC 17a-4, MiFID II, SOX 404

Every client communication must be attributable. FINRA fined 16 firms $1.1B (2021-2023) for attribution failures.

Mailgent

DKIM-signed emails with delegation chain: Registered Rep > Firm > Agent.

Healthcare

HIPAA 164.312, 21 CFR Part 11, HITECH Act

Unique user identification for every system accessing PHI. Average breach cost: $10.9M.

Mailgent

Per-agent identity satisfies unique user identification. Audit trails provide ALCOA-compliant attribution.

Legal

FRCP 37(e), FRE 502, Circular 230

Litigation holds must be provably delivered. Privileged communications must trace to attorney supervision or privilege is waived.

Mailgent

Delegation chain proves Attorney > Firm > Agent. Delivery audit trails satisfy FRCP.

Defense

CMMC 2.0, NIST 800-171, FedRAMP

Unique identification for all processes handling CUI. Shared service accounts = examination finding. Failure = loss of DoD contracts.

Mailgent

Per-agent identity satisfies NIST 800-171 3.5.1/3.5.2.

Insurance & Real Estate

UCSPA, RESPA/TRID, Fair Housing Act

Claims comms must be from authorized adjusters. Mortgage disclosures must identify the creditor.

Mailgent

Agent identity tied to licensed entity. Delegation chain proves authorization.

Governance is not identity.

IAM platforms monitor and govern agents. Mailgent makes agents functional. You need both — they're complementary layers.

Governance plane

“Who can do what?”

  • Policy enforcement
  • Behavioral monitoring
  • Anomaly detection
  • Access revocation

Your IAM platform

Capability plane

“What can agents actually do?”

  • Send and receive email
  • Store and retrieve credentials
  • Generate 2FA codes
  • Delegation chains + audit trails

Mailgent

Give your agent an identity.

Create an identity, attach capabilities, and start building.