The IamMe Platform
How it works, who it protects, and how to integrate — everything you need to evaluate IamMe for your organisation.
Trust delivered in milliseconds
Before the phone rings, the recipient already knows who you are. No apps to open. No steps to take.
Caller signals intent
Before dialing, the caller — an enterprise system or enrolled individual — sends a cryptographically signed token to the IamMe network.
Network signs and delivers
IamMe validates the caller's identity, signs the token with ES256, and pushes a notification to the recipient via APNs or FCM — ahead of the call.
Recipient sees the truth
A native notification appears on the locked screen before the call arrives. The phone rings normally — with verifiable context already visible.
The phone has become the attack surface
Caller ID is trivially spoofed. AI can clone a voice in seconds. IamMe makes identity unforgeable — regardless of the threat vector.
Generative AI clones a voice from seconds of audio. Attackers impersonate executives, family members, and officials in real time.
Attackers call posing as banks, the IRS, Medicare, or tech support — convincing victims to transfer funds or share credentials before the call is answered.
Fraudsters spoof the SSA, IRS, FBI, and local police — creating fear that bypasses rational thinking. Victims are conditioned not to hang up.
"Your grandchild needs bail money." Emergency framing disables skepticism. AI voice cloning makes it indistinguishable from a real family member.
Legitimate businesses pay for fraud they didn't commit. Customers ignore calls from banks and health providers because they can't distinguish real from fake.
Attackers call employees posing as executives or IT, instructing wire transfers or credential resets. High success rate. Low detection. Growing fast.
Traditional fraud defenses are reactive — they analyze patterns after the fact or flag numbers after victims have already been harmed. IamMe runs in parallel with every call, delivering cryptographic proof of identity before the phone rings. Every threat above requires faking an identity that cannot be faked. The token is unforgeable, hardware-bound, and verified in milliseconds.
Your calls get answered.
Your brand gets trusted.
When customers see your name before you call, answer rates rise and fraud exposure falls. One API call before you dial — no telephony changes required.
Account alerts, fraud warnings, loan officer calls. Every outbound call from your institution arrives verified. Customers answer. Trust is restored.
Benefits agencies, revenue services, public health — citizens are conditioned to distrust government calls. Verified identity restores credibility at scale.
Appointment reminders, care team follow-ups, prescription notifications. Patients answer verified providers. Missed appointments fall. Outcomes improve.
Your calls stand out.
For the right reasons.
Enroll once. Every call you make shows your verified identity to the recipient — before their phone rings. You get answered. They feel safe answering.
The same identity.
End-to-end encrypted.
Device keys established at enrollment unlock more than verified calls. IamMe's secure messaging uses the same hardware-protected keypairs to establish end-to-end encrypted channels — without a separate key exchange.
Trust is earned, not assumed
Verification levels reflect real-world trust. Enrollment is the start — confirmed history and institutional auditing earn higher standing.
Phone ownership verified. Biometric device key generated. Trust is building through call history.
A history of confirmed calls — real interactions with real people. The network has seen this identity behave consistently.
Reserved for enterprises, government entities, and institutions. Identity verified through audit — the highest level of trust in the network.
One API call.
Before you dial.
Enterprise integration is a single POST request before every outbound call. Your telephony stack doesn't change.
Get API credentials# Before every outbound call
curl -X POST https://api.iamme.ai/v1/attest \
-H "Authorization: Bearer <your_api_key>" \
-d '{
"from_number": "+18005551000",
"to_number": "+15551234567",
"comm_type": "call",
"purpose": "account_verification"
}'
# Then dial normally
{
"status": "delivered",
"expires_in": 60,
"delivery_id": "del_a1b2c3d4"
}Ready to be trusted?
Whether you're evaluating enterprise integration or exploring the API — we'd like to hear from you.
Or reach us at hello@iamme.ai