Legacy API Keys

Verified: August 24, 2026

API keys are an advanced compatibility surface. They are not part of Ranch.Bot onboarding, and most customers do not need one.

What does not require an API key

You do not need an API key to:

  • sign in with your phone;
  • create a farm;
  • enable Text-in;
  • review or confirm proposed records in the web dashboard;
  • manage animals, groups, and records in the app; or
  • export farm data.

The Getting Started guide owns that workflow.

Current integration boundary

The public Ranch.Bot MCP package uses browser OAuth login. Creating an API key does not make Claude, ChatGPT, Gemini, or another assistant connect to Ranch.Bot.

The local stdio MCP source uses OAuth device flow rather than an API key. API keys remain for directed developer and legacy self-hosted HTTP use while Ranch.Bot works toward retiring them. See MCP Setup.

Create a key only when directed

If Ranch.Bot support or a development runbook specifically requires a key:

  1. Open Settings → API Keys.
  2. Choose Create API Key.
  3. Give the key a name and, if needed, a default farm.
  4. Copy the key when it is shown. The full value is not shown again.

A Ranch.Bot key starts with rb_sk_. Treat the full value like a password.

Keep a key safe

  • Do not paste it into chat, email, screenshots, or a public repository.
  • Use a separate key for each directed integration.
  • Revoke a key immediately if it may have leaked.
  • Remove unused keys.

To revoke one, open Settings → API Keys, choose the key, and confirm Revoke. A revoked key no longer authenticates requests.

Lost or exposed key

The full key cannot be recovered from Ranch.Bot. Revoke the old key and create a replacement only if the integration still needs one.

For help, email support@ranch.bot. Never send the key value.

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.