Farmbrite API
✓ Official Vendor SpecProductivityTask Managementbearer24 EndpointsREST
For Agents
Record and retrieve animal records, feedings, grazings, measurements, livestock groups, and climate-gauge readings on a Farmbrite farm.
Use for: I want to record a new animal on the farm, Log a feeding for a specific cow, Retrieve the weight history for an animal, List all climate gauges and their latest readings
Not supported: Does not handle crop records, field mapping, or accounting — use for animal, grazing, and climate-gauge tracking only.
The Farmbrite API exposes the farm-management platform's records for animals, livestock groups, feedings, grazings, measurements, and climate gauges. It lets agents and integrations log day-to-day farm activity, retrieve animal histories, and pull environmental readings for reporting or analytics. The 24-endpoint surface is structured around a small number of primary resources with nested activity logs.
Install Jentic One Beta
Connect the Farmbrite API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Farmbrite API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Farmbrite API.
Track individual animals with creation, update, and deletion of animal records via /animals
Log feedings against a specific animal and pull historical feeding records via /animals/{animal_id}/feedings
Record physical measurements (weight, body condition) for any animal via /animals/{animal_id}/measurements
Retrieve grazing and livestock-group rosters to plan rotational grazing schedules
Capture climate-gauge readings such as rainfall and temperature to feed weather-aware farm dashboards
Pull animal set-log history to audit treatments, moves, and group assignments
Use Cases
Patterns agents use Farmbrite API for, with concrete tasks.
★ Daily Farm Activity Logging
Smallholder and ranch operations use Farmbrite to log feedings, measurements, and treatments against individual animals each day. The nested /animals/{animal_id}/feedings and /animals/{animal_id}/measurements endpoints make it straightforward to attribute every activity to the correct animal. Replaces paper logs and spreadsheets with a queryable record set in a few hours of integration work.
Create a feeding record for animal_id 4521 with feed type, quantity, and timestamp via POST /animals/{animal_id}/feedings
Livestock Weight and Health Tracking
Producers tracking animal performance pull measurement histories from /animals/{animal_id}/measurements to chart weight gain, body condition, and health markers over time. The data feeds breeding decisions, sale-weight forecasts, and veterinary reviews. Pairs well with reporting tools that want a structured feed instead of CSV exports.
Pull every measurement for animal_id 4521 via GET /animals/{animal_id}/measurements and chart weight against date
Climate-Aware Grazing Planning
Rotational grazing operations combine /climate_gauges readings with /grazings and /livestock_groups data to plan paddock moves around rainfall and temperature. The API gives planners a programmatic feed instead of polling the Farmbrite UI. Useful for regenerative agriculture dashboards and farm advisory services.
Fetch the latest reading from each /climate_gauges entry and cross-reference it with active /grazings to recommend the next paddock move
AI Farm Assistant via Jentic
Conversational farm assistants use Jentic to call Farmbrite operations from natural-language prompts like 'log today's feeding for cow 12'. Jentic resolves the intent to the right /animals/{animal_id}/feedings call and supplies the bearer token from its vault. The agent never handles raw credentials and the operator does not have to integrate the spec directly.
Through Jentic, search 'log a feeding for a farm animal', load the operation, and execute with animal_id, feed type, and quantity from the user's voice input
Key Endpoints
24 endpoints — the farmbrite api exposes the farm-management platform's records for animals, livestock groups, feedings, grazings, measurements, and climate gauges.
METHOD
PATH
DESCRIPTION
POST
/animals
Create a new animal record
GET
/animals/{animal_id}
Retrieve a single animal
POST
/animals/{animal_id}/feedings
Log a feeding for an animal
POST
/animals/{animal_id}/measurements
Record a measurement for an animal
GET
/grazings
List grazing records
GET
/livestock_groups
List livestock groups
POST
/climate_gauges
Create a climate gauge
POST
/animals
Create a new animal record
GET
/animals/{animal_id}
Retrieve a single animal
POST
/animals/{animal_id}/feedings
Log a feeding for an animal
POST
/animals/{animal_id}/measurements
Record a measurement for an animal
GET
/grazings
List grazing records
GET
/livestock_groups
List livestock groups
POST
/climate_gauges
Create a climate gauge
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Farmbrite bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw bearer token never enters prompt context or logs.
Intent-based discovery
Agents search by intent (e.g. 'log a feeding for an animal') and Jentic returns the matching nested /animals/{animal_id}/feedings operation with its input schema.
Time to first call
Direct integration: 1-2 days for bearer auth, animal-id resolution, and nested-resource handling. Through Jentic: under an hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Farmbrite API through Jentic.
What authentication does the Farmbrite API use?
Farmbrite uses HTTP Bearer token authentication — supply your API token in the Authorization header. Through Jentic, the bearer token lives in the vault and is injected at execution time, so the agent never sees the raw token.
Can I log feedings and measurements for individual animals with the Farmbrite API?
Yes. POST to /animals/{animal_id}/feedings to log a feeding event and POST to /animals/{animal_id}/measurements to record weight or body condition. Both endpoints attribute the entry to a specific animal_id.
What are the rate limits for the Farmbrite API?
Farmbrite does not publish explicit rate limits in the OpenAPI spec. Treat it as a low-frequency operational API, batch reads where possible, and respect any 429 responses by backing off.
How do I retrieve climate gauge readings through Jentic?
Install with pip install jentic, search 'list climate gauges on a farm', load the GET /climate_gauges operation, and execute with your Farmbrite bearer token. Sign up at https://app.jentic.com/sign-up.
Does the Farmbrite API support crop and field records?
The current OpenAPI surface covers animals, feedings, grazings, measurements, livestock groups, and climate gauges. Crop, field, and accounting endpoints are not exposed in this spec — use the Farmbrite UI for those workflows.
GET STARTED