Ravi

Real-World Scenarios

Software evaluation

An agent evaluating project management tools for your team:

  1. Signs up for Asana trial (email verification)
  2. Signs up for Monday.com trial (email verification)
  3. Signs up for ClickUp trial (phone verification)
  4. Signs up for Notion trial (email verification)
  5. Receives all onboarding emails
  6. Accesses each platform, compares features
  7. Reports findings

Without Ravi: 4 separate verification interruptions, marketing emails flooding your personal inbox.

With Ravi: Fully autonomous. All verifications handled. All marketing emails stay in the agent’s inbox.

# For each service
EMAIL=$(ravi get email --json | jq -r '.email')
CREDS=$(ravi passwords create asana.com --username "$EMAIL" --json)
PASSWORD=$(echo "$CREDS" | jq -r '.password')
# Sign up with $EMAIL and $PASSWORD...
sleep 5
ravi inbox email --unread --json  # Get verification

Price monitoring

An agent tracking prices across e-commerce sites:

  1. Creates accounts on 15 retailers
  2. Adds items to wishlists
  3. Subscribes to price drop alerts
  4. Receives notifications when prices change
  5. Aggregates data and reports to you

Without Ravi: Your personal email exposed to 15 retailers, endless marketing emails.

With Ravi: Agent has its own inbox. Your personal info stays private. Agent monitors alerts independently.

Travel booking

An agent booking a trip:

  1. Creates airline account (email verification)
  2. Books flight (confirmation to email)
  3. Creates hotel account (phone verification)
  4. Books hotel (confirmation to email)
  5. Receives all confirmations
  6. Compiles itinerary

Without Ravi: Multiple verification interruptions, your phone number and email shared with travel companies.

With Ravi: Continuous autonomous operation. All confirmations in one place. Your personal info stays private.

Research assistant

An agent conducting market research:

  1. Signs up for industry publications (email gate)
  2. Registers for analyst reports (email gate)
  3. Creates accounts on data platforms (verification required)
  4. Subscribes to competitor newsletters
  5. Registers for industry webinars
  6. Collects and synthesizes information

Without Ravi: Blocked at every email gate. Your inbox polluted with industry spam.

With Ravi: Agent accesses gated content autonomously. Industry emails stay in the agent’s inbox.

Customer service automation

An agent handling support tasks:

  1. Initiates support ticket (email required)
  2. Receives ticket confirmation
  3. Responds to follow-up questions
  4. Receives resolution confirmation
# Send a support email
ravi email compose \
  --to "support@service.com" \
  --subject "Order #12345 — delivery question" \
  --body "<p>Hi, I'd like to check the delivery status for order #12345.</p>" \
  --json

# Wait for response
sleep 30
ravi inbox email --unread --json

The pattern

Every scenario follows the same pattern:

  1. Get Identity details — ravi get email --json, ravi get phone --json
  2. Store credentials — ravi passwords create <domain> --json
  3. Complete verification — ravi inbox sms --unread --json or ravi inbox email --unread --json
  4. Operate independently — the agent works without human intervention

The web assumes every user has an email and phone number. Ravi gives your agent both, so it can operate in a world built for humans.

Next steps