You are putting together a shortlist for a farm-data project. You have a simple plan: start with the big names. John Deere, Bayer, Syngenta. Surely the companies that own the field have the best APIs for it.
So you open the Agriculture industry page on apis.io. It holds 320 providers and 1,186 APIs, and membership is computed from tags rather than a fixed list. Before you read a single name, the bands tell you what to expect. 199 providers are minimal, 70 are emerging, 33 are thin and 18 are developing. Not one is listed as strong or exemplar.
Now you look for the names you came for. John Deere scores 10.8, minimal, with 8 APIs counted and no published count. Bayer is at 11.3 and Syngenta at 17.4, both with zero APIs listed. If you were hoping to find a published contract to build against, the catalog has none to give you yet for anything branded Deere.
So who leads? You scan the table by function. For local food discovery, Rett fra Bonden scores 53.1 with 7 APIs, 4 published. For greenhouse sensing, 30MHz scores 52.6 with 127 APIs, 4 published. For weather and ag data, DTN scores 50.9 with 99 APIs, 37 published. Climate FieldView, the farm data platform, scores 44.5 with 5 APIs, 1 published. In equipment, AGCO scores 43.8 with 58 APIs, 3 published. Trimble, for positioning, scores 41.1 with 20 APIs, 2 published. CNH scores 37.4 with 8 APIs, 1 published.
Three patterns stand out as you read. First, the leader is a non-profit. Rett fra Bonden is a Norwegian discovery layer for local food, a registry of 1,900+ farms, farm shops and markets that its own description says is built to be read by AI agents first. It outranks every equipment maker and agrochemical company in the vertical, and its provider page puts it at 43.9 on Agent Readiness, agent-ready.
Second, and this is the part that matters if you are about to quote a number, the industry page lags the provider pages. 30MHz's own page now reads 55.2, strong, and Rett fra Bonden's reads 50.0. So the vertical does have a strong provider. The rollup just has not caught up. That is the catalog's own record contradicting its own headline, and the post says so plainly: if you rank from the industry page, check the provider page before you quote a band. You would have told your team there was no strong provider in agriculture, and the provider pages say otherwise.
Third, data vendors outscore machinery. DTN publishes 37 APIs, the deepest published surface in the top tier, covering weather, agronomy and commodity data. AGCO lists 58 APIs but only 3 published. In agriculture, the companies selling information have done more of the contract work than the companies selling tractors.
That gives you a place to start. For field and parcel data, the post points you to DTN's Farm Intelligence entries, such as the Land Crop API, which meters by record and says so in its headers. For farm-operations data, Climate FieldView and AGCO are the two equipment-adjacent records with published contracts.
You close the tab with a cleaner picture than the one you opened it with. Agriculture is a big vertical with a thin top. The 320-provider count is real, but 269 of them sit in the bottom two bands, and the strongest records belong to data companies and a food directory, not the brands that own the field. You drop the Deere-first plan, build your shortlist around DTN, Climate FieldView and AGCO, and make a note to verify any band against the provider page before it goes in a slide.
Read the original: https://apis.io/2026/11/11/agriculture-has-320-providers-and-john-deere-scores-10-8/