What Your AI Assistant Can and Can't Do With Herd Records

Connecting an AI assistant to farm records raises the right kind of suspicion. Records are the operation's memory — lambing history, treatments, withdrawal dates — and nobody should hand that to software without knowing exactly what it can touch. Here are the straight answers, as they work in Ranch.Bot.

Can an assistant read my records?

Yes, once you grant it. Ranch.Bot runs an MCP server (MCP is the open standard assistants use to work with outside tools). You connect your assistant, sign in to Ranch.Bot once in your browser, and from then on it can look up your animals, groups, and records — by ear tag, EID, name, or plain question.

Practical version: a 200-ewe flock mid-lambing. "Which ewes from the first cycle haven't lambed?" is answered from your actual lambing records, not from whatever the assistant half-remembers of an old conversation.

Can it add or change records?

Yes — that is half the point. Describe the work and it lands as structured data: "Ewe 415 lambed twins this morning, one assist" becomes a lambing record with a date, a count, and a note, on the right ewe. Treatments, movements, group changes work the same way.

Two guardrails apply to every write:

  1. Scope. The assistant can only touch farms you granted when you signed in.
  2. Change History. Every change, human or AI, is logged. You can always see what was added, when, and through what access.

Can it do things without me knowing?

Nothing connects itself. Assistant access exists only because you signed in to grant it, and it lasts only until you revoke it. There is no background access, no standing permission you didn't create, and the Change History shows everything that used the access you granted.

Where does "review before saving" happen?

This distinction matters, so here it is precisely:

  • Inside the Ranch.Bot app, the built-in assistant shows you every record it understood from your words, and you confirm before it saves. That review gate is an app feature.
  • Through your own assistant (Claude and other MCP clients), writes go through your scoped access and are logged in Change History — but the conversation happens in the assistant's app, so the confirmation step is the one your assistant provides. Ranch.Bot's guarantees there are scope, logging, and revocation, not a second review screen.

If you want the tightest loop on every save, use the in-app assistant. If you want the convenience of the assistant you already use, the access is scoped and the trail is complete. Many producers will use both in the same week.

Can it make decisions about my herd?

No, and it shouldn't. Records inform decisions — they don't make them. An assistant with access can pull a ewe's full history at culling time: three lambings, one assist, two singles, a mastitis treatment. Whether she stays is your call, made with better information. Nothing in Ranch.Bot offers veterinary diagnosis or makes culling, breeding, or financial decisions, and an assistant connected to it gets data, not authority.

What happens when I revoke access?

Access ends immediately. Open Settings → Connected Apps, revoke the connection, and the assistant's sign-in stops working. Your records are untouched by revocation — they are yours, exportable in full anytime, whether or not any assistant is connected.

What's the honest summary?

It canIt can't
Read the records on farms you grantedReach anything you didn't grant
Add and update records from plain languageAct outside the logged, scoped access
Pull full histories for your decisionsMake the decisions or give vet advice
Save you the data-entry slogReplace your judgment at the chute

Ranch.Bot was built on a working sheep operation, where suspicion of software that overpromises runs appropriately deep. The design assumes the producer stays in charge: your sign-in grants access, your settings revoke it, your Change History sees all of it.

Ready to see it with your own herd? Start the 14-day free trial and connect your assistant from the setup guide once your first animals are in.