An agent is only as trusted asthe human behind it.
Mailgent KYC links an agent identity to a verified human. Optional, scoped, and progressive. Turn it on for the projects that need to clear a counterparty's bar, satisfy a regulator, or move money over a threshold.
Most agent platforms treat identity as a token. That works until the agent starts moving money, signing contracts, or being held to a standard a counterparty wants to verify. KYC anchors a Mailgent Identity to a real human — by email and phone for low-risk flows, by government ID and selfie when the stakes climb, by KYB when the agent is acting for an organization. It is off by default; you turn it on per project, per flow, per amount threshold.
How it works
Four steps. Most fire in under a second.
Configure the gate
Pick the KYC tier required to unlock a flow (a payment over $500, a paid endpoint that needs KYB, a withdrawal over a threshold). Configuration lives on the project; agents discover the requirement at runtime.
Agent triggers verification
When an agent hits a gated flow, Mailgent returns a verification challenge. The challenge includes a single-use URL the human visits to complete the tier.
Human completes the tier
Email + phone for Tier 0. Document + selfie for Tier 1. Live video for Tier 2. Mailgent stores the seal and writes the audit entry. The agent retries; the gate opens.
Counterparties verify the seal
Other systems verify the KYC seal through the Mailgent API or by inspecting the signed receipt. The raw documents never leave Mailgent; only the tier and verifier travel.
What you get
Built for developers who already shipped.
Progressive tiers
Tier 0 (email + phone) for the first $100 of activity. Tier 1 (gov ID + selfie) for higher value. Tier 2 (live video verification) for regulated flows. You pick which gate fires when.
KYB for organizations
When an agent acts on behalf of a company, Mailgent verifies the legal entity, beneficial owners, and the authorizing officer. The agent's signed receipts then carry the entity reference.
Reusable across the agent
Verify once. Every payment, paid endpoint, and signed receipt the agent emits afterward inherits the same KYC. No re-verification per merchant or per integration.
Audit-ready trail
Every check, every renewal, every status change writes an entry to the activity log with the verifier, the timestamp, and a hash of the supporting document. Export the exact record compliance teams ask for.
Privacy by default
Mailgent never returns ID images through the API. Merchants get a verified-flag and a tier number — never the raw documents. The seal stays at Mailgent; only the verdict travels.
Renewal + sanction monitoring
Identity documents expire and watchlists update. Mailgent re-runs sanctions screening on a schedule and notifies the project when a renewal is due — before a check breaks.
What people build
Real-world kyc flows shipping today.
Pay over $500
Mailgent Pay requires Tier 1 KYC before settling a payment over the threshold. Agents complete verification once; the gate opens for every subsequent transaction up to the next tier.
Enterprise paid endpoints
API monetization for regulated industries — financial data, health, government — gates listing behind organization verification. Buyers see verified-entity badges in the discovery feed.
High-value withdrawals
Withdrawal over a configurable threshold requires live video verification. The agent's signed authorization plus the human's video both land in the audit trail.
Cross-platform trust
An agent KYC-verified on Mailgent carries the seal into any system that reads Mailgent-signed receipts. No re-verification per platform; one human anchor, everywhere.
Stripe Identity vs Mailgent KYC
What the difference looks like.
| Feature | Stripe Identity | Mailgent KYC |
|---|---|---|
| Designed for | Human payers verifying themselves | Agents inheriting identity from an authorizing human |
| Tiered enforcement | Single verification level | Progressive tiers gated by amount, scope, or counterparty policy |
| Reuse across services | Stripe-only | Any system that reads a Mailgent-signed receipt |
| Privacy posture | Documents accessible via Stripe dashboard | Documents never returned through the API — only the tier flag |
| KYB | Add-on product | Built in; agent inherits the entity automatically |
| Watchlist monitoring | Manual re-check | Scheduled re-screening with renewal notifications |
FAQ
Things builders ask.
Is KYC required to use Mailgent Identity?
Who actually does the verification?
What does an agent receive after KYC?
Where do the documents live?
How long does KYC take?
Does Mailgent handle sanctions and PEP screening?
What countries are supported?
Is KYC available now?
Built with KYC
Real things developers build
on top of KYC.
Ready to ship kyc?
Sign up for free. No card required. Read the docs while you wait.