#agriculture

Live commodity futures prices as an API — the energy, grain, soft and livestock commodity complex, served from Yahoo Finance. For any commodity it returns the front-month futures price, the previous close, the absolute and percentage change on the day, the day's high and low and the 52-week high and low, with the price's currency and quoting unit (e.g. USD per barrel, US cents per bushel). Look a commodity up by name or alias (crude oil, Brent, natural gas, gasoline, corn, wheat, soybeans, coffee, sugar, cocoa, cotton, orange juice, live cattle, lean hogs and more), pull a category board (energy, grains, softs, livestock) ranked by the day's move, or get the whole board in one call. The commodity-quote layer for trading, markets and dashboard apps. Live, no key. Distinct from the precious-metals API — this is the energy, agricultural and soft-commodity complex.

api.oanor.com/commodities-api

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

Planting seed-rate maths as an API, computed locally and deterministically — the plant-population, seed-spacing and seeding-rate numbers a farmer, agronomist or precision-ag tool sets a planter or drill to. The population endpoint gives the plants per acre = 6,272,640 ÷ (row spacing × in-row seed spacing) in inches (the 6,272,640 is the square inches in an acre), so 30-inch rows with seeds 6 inches apart give about 34,800 plants per acre — closer spacing raises the population and the competition. The seed-spacing endpoint runs it the other way: the in-row spacing for a target population = 6,272,640 ÷ (target plants × row spacing), so 35,000 plants per acre in 30-inch rows means a seed about every 6 inches, the value to set on a singulating meter or seed-rate drive. The seeding-rate endpoint gives the pounds of seed per acre = the target population ÷ the germination rate ÷ the seeds per pound, over-seeding for the seeds that never come up — 35,000 plants of a 1,500-seeds-per-lb crop at 95 % germination needs about 24.6 lb/acre, working from the seed lot's own tag. Everything is computed locally and deterministically, so it is instant and private. Ideal for precision-ag and farm-management tools, planter-calibration and agronomy apps, and seed-retail utilities. Pure local computation — no key, no third-party service, instant. US units. 3 compute endpoints. For sprayer rates use a spray API; for fertiliser a fertilizer API.

api.oanor.com/seedrate-api

Agricultural sprayer maths as an API, computed locally and deterministically — the calibration, coverage and tank-mix numbers a farmer, agronomist or custom applicator dials a boom sprayer in with. The calibration endpoint gives the broadcast application rate GPA = 5940 × the per-nozzle flow (GPM) ÷ (ground speed in mph × nozzle spacing in inches), the 5940 converting the units for a full-coverage boom — so a 0.4 GPM nozzle at 5 mph on 20-inch spacing lays down about 24 gallons per acre, and driving faster or spacing nozzles wider drops the rate. The coverage endpoint gives the acres a tank covers (tank ÷ GPA) and, for a field size, the total spray volume and the number of tank-loads, with the partial last fill called out so it can be mixed to the leftover acres. The product endpoint gives the pesticide or nutrient to add per tank = the acres a tank covers × the label rate per acre (in whatever unit the rate uses — ounces, pints, pounds), plus the total product for the field. Everything is computed locally and deterministically, so it is instant and private. Ideal for precision-ag and farm-management tools, sprayer-calibration and tank-mix apps, and ag-retail utilities. Pure local computation — no key, no third-party service, instant. Always follow the product label and calibrate with a real catch test. 3 compute endpoints. For fertiliser rates use a fertilizer API; for sprinkler/irrigation design an irrigation API.

api.oanor.com/spray-api

Screw-conveyor and grain-auger maths as an API, computed locally and deterministically — the capacity, speed and throughput numbers a farmer, millwright or material-handling engineer sizes an auger with. The capacity endpoint gives the volumetric throughput from the screw geometry: the annular flight volume per turn ((π/4)(diameter² − shaft²) × pitch) × rpm × 60 × the trough loading, so a 9-inch full-pitch screw on a 2.5-inch shaft at 40 rpm and 45 % loading moves about 330 cubic feet — 265 bushels — an hour. The speed endpoint inverts it, the rpm needed for a target capacity, so you don't overspeed a small auger and grind the grain. The bushels endpoint converts a volumetric rate to bushels and tons per hour (1 bushel = 1.2445 ft³, tons = bushels × test weight ÷ 2000), so 330 ft³/hr of 56-lb corn is 265 bushels or 7.4 tons an hour — the number you match to the dryer or the truck. Everything is computed locally and deterministically, so it is instant and private. Ideal for grain-handling and ag-equipment apps, material-handling and conveyor-design tools, farm-build calculators, and engineering aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — incline and material change real throughput. For belt conveyors use a conveyor API.

api.oanor.com/auger-api

Fish-farming (aquaculture) maths as an API, computed locally and deterministically — the stocking, feed and oxygen numbers a fish farmer or RAS designer runs a system on. The stocking endpoint turns a tank or pond volume and a target biomass density into a fish count: biomass = density × volume, count = biomass ÷ average fish weight — a 10 m³ tank at 30 kg/m³ holds 300 kg, about 1,200 fish at 250 g each, and you stock to the harvest weight, not the fingerling weight, so the tank does not overload as they grow. The feed endpoint gives the daily ration as a percentage of body weight, and the feed to reach a target weight gain through the feed conversion ratio — 300 kg fed at 2 % is 6 kg a day, and growing 100 kg of fish at an FCR of 1.2 takes 120 kg of feed. The oxygen endpoint gives the dissolved-oxygen demand of a stock — biomass × the per-kg consumption rate — so 300 kg at 300 mg O₂/kg/hr needs 90 g of oxygen an hour, the number your aeration must beat. Everything is computed locally and deterministically, so it is instant and private. Ideal for aquaculture and RAS-design apps, fish-farm management tools, hatchery and feed calculators, and ag-tech sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Commercial-planning estimates — species and system vary. For a home aquarium use an aquarium API.

api.oanor.com/aquaculture-api

Grain-bin storage maths as an API, computed locally and deterministically — the bushel and weight numbers a farmer or elevator sizes storage by. The bushels endpoint measures a round bin: floor area × grain depth gives the cubic feet, and a cubic foot holds about 0.8036 bushels, so an 18-foot bin filled 20 feet level holds roughly 4,090 bushels — and grain heaped to a peak adds a cone of (1/3) × floor area × peak height, so a 4-foot peak adds about 270 more. The weight endpoint converts bushels to weight by the crop’s standard test weight — corn and sorghum at 56 pounds a bushel, wheat and soybeans 60, oats 32, barley 48 — so those 4,090 bushels of corn weigh 229,040 pounds, about 114.5 US tons or 104 tonnes; pass a measured test weight for light or heavy grain. Everything is computed locally and deterministically, so it is instant and private. Ideal for agriculture, grain-elevator, farm-management and ag-tech app developers, storage-capacity and inventory tools, and harvest software. Pure local computation — no key, no third-party service, instant. US units (feet, bushels, pounds). Live, nothing stored. 2 compute endpoints.

api.oanor.com/grainbin-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

Plant-spacing and planting-density maths as an API, computed locally and deterministically. The grid endpoint works out how many plants fill an area in a square (rectangular) layout: from a spacing (one value, or separate row and in-row spacings) and either an area or a length and width, it returns the planting density per square metre, square foot, 1,000 ft², acre and hectare, an area-based plant estimate, and — when you give length and width — an exact edge-inclusive grid count with the number of rows and plants per row. The triangular endpoint does the same for an offset (hexagonal) layout, where rows sit spacing × √3/2 apart and fit about 15.47 % more plants than a square grid at the same spacing, and it reports the gain. The density endpoint converts a spacing into a planting density in several units, or works in reverse: give a number of plants and an area and it recommends the spacing that fills it. Lengths accept millimetres, centimetres, metres, inches or feet; area accepts m², ft², acres or hectares. Everything is computed locally and deterministically, so it is instant and private. Ideal for gardening and landscaping apps, agriculture and horticulture tools, nursery and farm planners, and reforestation calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is planting layout and density; for fertilizer application rates use a fertilizer API and for mulch, soil and gravel quantities use a landscaping API.

api.oanor.com/plantspacing-api

Fertilizer maths as an API, computed locally and deterministically. The rate endpoint works out how much fertilizer product to apply to hit a target nitrogen rate over an area: from the N-P-K analysis (such as 10-10-10 or 20-5-10), a target pounds of nitrogen per 1000 ft² (or per 100 m²) and the area, it returns the product weight and the pounds of nitrogen, phosphate and potash applied. The nutrients endpoint reports the pounds of nitrogen, P₂O₅ and K₂O — and the elemental phosphorus and potassium — in a bag of a given weight and analysis. The coverage endpoint works out how much area a bag covers at a target nitrogen rate. N-P-K are percent by weight; phosphorus is reported as P₂O₅ and potassium as K₂O following the label convention, with the elemental amounts alongside (P₂O₅ × 0.4364, K₂O × 0.8301). Everything is computed locally and deterministically, so it is instant and private. Ideal for lawn-care and gardening apps, agriculture and turf tools, and landscaping and quoting software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fertilizer rate maths; for mulch, gravel and topsoil quantities use a landscaping API.

api.oanor.com/fertilizer-api

Solar irradiance and agroclimatology for any location on Earth — as an API over NASA POWER (Prediction Of Worldwide Energy Resources), derived from NASA satellite and reanalysis data. Get the solar resource needed to size and assess PV and CSP systems: global (GHI), direct-normal (DNI) and diffuse horizontal irradiance, clear-sky irradiance and the clearness index — either as long-term monthly climatology normals for quick site assessment, or as a daily time series for a date range (1981-present). The same call also serves meteorology — temperature, wind speed, relative humidity and precipitation — making it ideal for solar energy, agriculture, building-energy modelling and climate work. From cloudy Berlin to the Sahara, it turns a coordinate into bankable solar and climate data. A solar-resource / agroclimatology data source — distinct from PV-system energy simulation (PVGIS) and historical-weather records. Open data from NASA POWER.

api.oanor.com/solar-api

Work with USDA Plant Hardiness Zones: determine the hardiness zone for any location from its average annual extreme minimum temperature in Celsius or Fahrenheit (returning the zone code such as 6b, the zone number, subzone and the temperature range in both units), browse the complete reference of all 26 subzones from 1a to 13b with their temperature ranges and example regions worldwide, look up a single subzone by code, and find which common garden plants — fruits, vegetables, herbs, shrubs, trees, perennials, vines, bulbs, succulents and grasses — tolerate a given zone. Every endpoint accepts input via the query string or the request body and returns lean JSON. Pure server-side computation (no third-party upstream), so responses are instant and always available. Ideal for gardening and plant-finder apps, AgTech and landscaping tools, nurseries and education.

api.oanor.com/hardiness-api