Ravi

Identity for AI Agents

Ravi gives AI agents their own identity (email inbox, real phone, encrypted vault) so they can sign up for services, receive verification codes, and keep the passwords they create. For teams whose agents have to act on the web, not just talk. Same identity fills the form, waits on signup OTP / magic link, handles returning-login 2FA, and stores the password across worktrees. Free $0 (1 inbox, 1 inbound-only phone). Docs: https://docs.ravi.app

Get Started
The Problem

Agents can't operate on the web without identity.

To sign up for a service, an agent needs an email. To verify an account, it needs a phone number. To log back in, it needs stored credentials. Without their own, agents are stuck.

agent — bash $ agent.signup("shopify.com") Error: no email address provisioned $ agent.verify_otp() Error: no phone number to receive SMS $ agent.login("shopify.com") Error: no stored credentials $ The agent is stuck.
Sound Familiar?

You solved this for employees.

New hire gets a work email, work number, and a password manager. Not your personal Gmail. Your agents deserve the same.

New Employee
jane@company.com
Work phone
Company vault
Own contact list
New AI Agent
Your personal Gmail
Your real number
Plain text on disk
Your contacts
The Solution

A complete persona for every agent.

Each agent gets its own identity — separate, isolated, revocable.

One person provisions multiple agent identities — Research, Finance, Scheduler
Email
Send, receive, and thread conversations from its own address.
Phone
Receive SMS and intercept OTPs on a dedicated number.
Vault
Store credentials and secrets behind scoped agent access.
Contacts
A per-identity directory that builds itself from every message.
Access Control

You decide who talks to whom.

Define communication policies between your agents. The product manager can reach customer support and engineering. The developer can only reach the PM. You set the rules.

PM Agent → CS Agent, Dev Agent
Dev Agent → PM Agent
Dev Agent → CS Agent
PM Agent CS Agent DEV Agent
Architecture

Identity becomes software.

Existing tools were built for humans — desktop apps, biometric prompts, sessions that expire. Ravi treats identity as infrastructure: programmable, autonomous, revocable.

Approve
Mute
Disable
Identity
Separate agent surfaces.
Give agents their own email, phone, contacts, and credentials instead of sharing personal accounts.
API
Scoped for agent runtimes.
Use identity-level keys for agent work and management keys for account operations.
Ready to give your agents their own identity?
Get Started