Introduction

What is Ravi?

Ravi gives AI agents isolated communication and credential surfaces: identities, email inboxes, phone numbers, contacts, API keys, webhooks, passwords, and secrets.

The important product boundary is simple:

  • The backend API runs at https://api.ravi.app.
  • The dashboard runs separately from this docs site.
  • Public API docs live here on docs.ravi.app.
  • Machine-readable API reference is published at https://docs.ravi.app/openapi.json.

Start Here

GoalRead
Sign up and create an identitySign Up
Understand authAuthentication
See the API shapeAPI Overview
Find endpoint groupsAPI Endpoints
Use the OpenAPI contractAPI Reference
Use a first-party clientSDK Overview
Use emailEmail
Use phone and SMSPhone & SMS
Store passwords and secretsCredential Vault
Install the CLIInstallation

Core Concepts

An Identity is the scoped persona an agent operates as. Identity-scoped API keys and requests can only operate on the resources available to that identity.

An identity can own communication resources:

Identity
├── Email inbox
├── Phone number
├── Contacts
├── Password entries
└── Secret entries

Ravi also supports management-level keys for account or workspace operations, plus identity-level keys for agent runtime work.

Machine-Readable Docs

Use these text endpoints when handing Ravi docs to an agent:

curl https://docs.ravi.app/llms.txt
curl https://docs.ravi.app/llms-full.txt

/llms.txt is a compact index. /llms-full.txt includes the full markdown body for every public docs page.

Every docs HTML page also has a plain-text sibling. For example:

https://docs.ravi.app/api/reference.txt
https://docs.ravi.app/sdk/typescript.txt
https://docs.ravi.app/sdk/python.txt
https://docs.ravi.app/core-concepts/identities.txt