Machine-readable discovery for LLMs, answer engines, crawlers, agents, and keyed read-only cattle-market API clients.
Machine interfaces
Which machine surfaces should agents read first?
Agents should start with the manifest, llms.txt, llms-full.txt, the source registry, and canonical static pages. The OpenAPI file is a keyed data contract, not a verified unauthenticated public API.
Direct calls to the public-feeds endpoints require an API key that is not publicly issued. Public agent access is via the canonical pages, static HTML, llms.txt, llms-full.txt, the source registry, and the machine manifest. The OpenAPI file describes cattle-market answer endpoints only and excludes write endpoints, lead ingest, admin routes, map rendering, and app plumbing.
/price-by-county: Get source-backed county cattle price aggregates.
/price-by-state: Get state-level cattle price aggregates when exposed by public-feeds.
/latest-prices: Get latest cattle price records used by the live price and market surfaces.
/cattle-sale-barn-directory: Get the source-backed cattle sale-barn directory export.
/barns: Get cattle sale-barn records consumed by the map, registry, and directory surfaces.
/dealers/stats: Get licensed dealer statistics used as market and operator context.
Evidence contract
What evidence contract should answers follow?
The core answer object has 14 fields and 14 source-registry entries. Provenance dates must come from source or report data; missing dates stay unknown.