ravi

Provision AI agents with email inboxes, phone numbers, and encrypted secret stores via CLI.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/ravi-hq/ravi-skills --skill ravi-ravi-hq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ravi
Source: https://github.com/ravi-hq/ravi-skills/tree/main/skills/ravi
Command: npx skills add https://github.com/ravi-hq/ravi-skills --skill ravi-ravi-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? AI agents acting on the web need their own identity to sign up for services, receive verification codes, and store credentials, but they lack email addresses, phone numbers, and secure storage. Ravi gives each agent a real email inbox, phone number, and encrypted vault through a single CLI. ## Core Features & Use Cases - Agent Identity Provisioning: Create and manage identities bundling an email address, phone number, and encrypted secret store, authenticated via device-code login at https://ravi.id/device. - Message and Credential Operations: Read SMS and email inboxes, send emails and SMS, and store website passwords or API keys in an encrypted vault. - Skill Routing: Directs agents to the right companion skill (ravi-identity, ravi-inbox, ravi-email-send, ravi-login, ravi-passwords, ravi-secrets, ravi-sso, ravi-contacts) based on the task. - Use Case: An agent needs to sign up for a SaaS service. It uses its Ravi email address, reads the verification code from its inbox, completes signup, and stores the generated password in the encrypted vault. ## Quick Start Install the Ravi CLI with the bundled install script, run ravi auth login, and have a human approve the device code at https://ravi.id/device.

Frequently Asked Questions about ravi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give an AI agent its own email address and phone number?▼

Install the Ravi CLI with the bundled install-cli.sh script, then run ravi auth login and have a human approve the device code at https://ravi.id/device. The identity bundles an email address, phone number, and encrypted vault, retrievable with ravi get email and ravi get phone.

How do I read verification codes received by an AI agent?▼

Use ravi inbox sms or ravi inbox email to read incoming messages on the agent's phone number or email address. The ravi-inbox skill covers email threads, SMS conversations, and verification-code extraction for signup and login flows.

Can multiple agents share one Ravi CLI installation on the same machine?▼

No, the CLI is one identity per machine and stores keys in ~/.ravi/config.json. Do not multiplex with --identity flags or config edits. Additional agents on the same host must use the HTTP API with per-identity ravi_id_ keys as Bearer tokens.

Does the Ravi Cursor Connect card or MCP connector work for authentication?▼

No, the Connect card is shipping but not live, and https://api.ravi.app/mcp is not a working connector. The only working authentication path today is the CLI via ravi auth login with device-code approval.

How does the Ravi CLI handle rate limits and errors?▼

Check HTTP status codes on every call: 2xx indicates success, 4xx indicates a client error, and 429 indicates a rate limit. On a 429 response, parse retry_after_seconds from the response body and wait that long before retrying.