Manage herds, paddocks, and livestock movements/exits for a field using the Auravant Livestock API.
domain: developers.auravant.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enable the livestock module in the Auravant extension's claimset before calling any livestock endpoints.
POST to /livestock/paddock with a WKT shape, field_id, date, and name to define a paddock within a field.
POST to /livestock/herd with type_id (see herd categories), animal_count, weight, weight_unit, herd_name, field_id, and paddock_uuid to create a herd.
POST to /livestock/transaction/paddock with origin_herd_uuid, origin_paddock_uuid, destination_paddock_uuid, and transaction_date to move a herd between paddocks.
POST to /livestock/transaction/exit with destination_type (see exit types), animal_count, weight, and origin_herd_uuid to record animals leaving a herd (sale, death, transfer, etc.).
Known gotchas
The livestock module must be explicitly activated in the extension's claimset, or all livestock endpoints will be inaccessible.
Paddock and herd identifiers used for transactions are UUIDs (paddock_uuid/herd_uuid), not the numeric paddock_id/herd_id also present in responses, so mixing them up will fail requests.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?