Ranch.Bot Documentation

Ranch.Bot turns livestock notes into structured records. The current daily workflow starts with a short web setup, then uses Text-in from the registered phone and the web dashboard for review.

Start here

Getting Started is the authoritative setup guide. It covers account creation, the 30-day trial, farm setup, Text-in, review, and export.

Current product path

Complete the account and farm setup in the web app. Enable Text-in under Settings → Account, text a note from the registered phone, then review the proposed record in the dashboard before it saves.

Daily records

  • Conversations - Review plain-language notes and proposed writes.
  • Animals - Find animals by name, management tag, EID, brand, or tattoo.
  • Records - View health, movement, genetic, feed, and other records.
  • Groups - Organize animals and apply work to a group.
  • Fast Entry - Choose between Text-in, web capture, and preview workflows.

Farm and data

Preview workflows

These pages document code that exists but is not enabled for standard customer accounts today:

  • Chute Mode - Preview status and current boundary.
  • Feed Mode - Preview status and current boundary.

Advanced integrations

External-assistant access is separate from the SMS and web product. It is not part of onboarding.

  • CLI Setup - Install, sign in through your browser, select a farm, and read records.
  • MCP Integration Status - Public package, registry, and hosted-connection status.

Plans and support

Current plan amounts and billing intervals live on the pricing page. The trial is 30 days, requires a card, and charges nothing until day 31.

For help, visit Support or email support@ranch.bot.

Terminal access

The public CLI setup guide covers installation, browser OAuth login, farm selection, and a first read. CLI login needs no API key. CLI writes run directly under your permissions, without the app confirmation screen or its Action-backed Change History.

HTTP developer reference

Browse the developer reference, current access guidance, and integration walkthroughs. API access remains directed developer use; these documents do not change public CLI or MCP installation availability.