#livestock

Hay and forage bale maths as an API, computed locally and deterministically — the weight, dry-matter and feed-supply numbers a rancher, hay producer or livestock manager plans winter feed with. The round-bale endpoint gives the weight from the cylinder volume (π·r²·width) × the dry-matter density (typically ~9–12 lb/ft³ for cured hay), so a 5×5 ft bale runs about 1,000 lb, and reports the dry-matter weight (≈88 % of as-fed) that actually feeds the animals — buy and ration on dry matter, not gate weight. The square-bale endpoint gives the weight of a rectangular bale from its length, width and height (÷ 1,728 for cubic feet from inches) × the density — a typical 14×18×36-inch small square is about 50 lb, big 3×3 or 4×4 ft bales hundreds — with a reminder that high moisture both adds weight and risks mould and barn-fire heating. The feed-supply endpoint sizes the stack: feed needed = head × daily intake × days (cattle eat ~2–2.5 % of bodyweight, about 25–30 lb of dry matter for a beef cow), and bales = that ÷ the bale weight, so 30 cows for 120 days at 30 lb is about 108 thousand-pound bales — add 10–20 % for feeding waste. Everything is computed locally and deterministically, so it is instant and private. Ideal for ranch- and farm-management tools, hay-trading and livestock apps, and ag calculators. Pure local computation — no key, no third-party service, instant. US units; densities are estimates. 3 compute endpoints. For grain storage use a grain-bin API; for rotational grazing a grazing API.

api.oanor.com/baleweight-api

Horse-care maths as an API, computed locally and deterministically — the everyday numbers a horse owner, barn manager or vet tech runs without reaching for a chart. The weight endpoint estimates body weight from a weight-tape measurement using the classic formula weight ≈ heart girth² × body length ÷ a type divisor (adult 330, yearling 301, weanling 280, pony 299) with measurements in inches — a horse with a 72-inch girth and 66-inch length comes out at about 1,037 lb (470 kg), the number you actually dose wormer and feed against. The feed endpoint turns body weight and a goal into daily forage: horses eat roughly 1.5–2.5 % of body weight in dry-matter forage a day, so a 1,000 lb horse on maintenance wants about 15–20 lb of hay, more to gain and less to slim. The gestation endpoint gives the foaling due date and the normal 320–362 day window from a breeding date — a mare bred on 1 April is due around 7 March the next year, give or take three weeks. Everything is computed locally and deterministically, so it is instant and private. Ideal for barn-management and horse-care apps, breeding and foaling trackers, feed-calculator and tack-shop sites, and equine-vet tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational estimates — not veterinary advice.

api.oanor.com/equine-api

Rotational-grazing maths as an API, computed locally and deterministically — the animal-unit, grazing-day and acreage numbers a rancher or homesteader moves a herd by. It all hangs on the animal unit: a 1000-pound cow eating about 26 pounds of dry matter a day. The animalunits endpoint converts a mixed herd to that common basis — a cow is 1.0 AU, a cow-calf pair 1.3, a horse 1.25, a sheep 0.2, a goat 0.17 — so ten cows and fifty sheep are 20 AU demanding 520 pounds of forage a day; pass a weight instead and it scales by weight ÷ 1000. The days endpoint works out how long a paddock lasts: grazing days = (acres × forage per acre × utilization) ÷ (animal units × 26), where the classic “take half, leave half” puts utilization near 50 %, so five acres yielding 3,000 lb at 50 % feeds 10 AU for about 29 days. The acres endpoint sizes the paddock the other way — acres = (AU × 26 × days) ÷ (forage × utilization) — so 20 AU for a 30-day move needs about 10.4 acres. Everything is computed locally and deterministically, so it is instant and private. Ideal for ranching, regenerative-agriculture, homesteading and farm-management app developers, paddock-planner and stocking-rate tools, and grazing-chart software. Pure local computation — no key, no third-party service, instant. US units; forage yield varies with season — measure it. Live, nothing stored. 3 compute endpoints.

api.oanor.com/grazing-api

Animal gestation and egg-incubation date maths as an API, computed locally and deterministically — the breeding and hatch calendar a farmer, breeder or vet works to. The gestation endpoint takes a species and a breeding date and returns the expected due date with the normal early-to-late window: due date = breeding date + the species' average gestation, so a cow bred on the 1st of January (283 days) calves around the 11th of October, a dog (63 days) whelps nine weeks later, a goat 150 days, a horse 340, a pig 114 — dozens of species from rabbit to camel to elephant, with an override for your own herd average. Give a target birth date instead and it works backwards to the date to breed. The incubation endpoint does the same for poultry and birds — chicken 21 days, duck 28, goose 30, quail 18, ostrich 42 and more — returning the hatch date, the lockdown date (stop turning and raise humidity ~3 days before hatch) and the day-7 and day-14 candling dates. Date arithmetic is exact, including leap years. Everything is computed locally and deterministically, so it is instant and private. Ideal for livestock, breeding, veterinary, farm-management and hatchery app developers, gestation-calculator and breeding-calendar tools, and agricultural education. Pure local computation — no key, no third-party service, instant. Dates as YYYY-MM-DD. Live, nothing stored. 2 compute endpoints. Averages, not a veterinary prediction.

api.oanor.com/gestation-api