Identify flowering plants eligible for harvest via the flowering plants listing endpoint.
Submit plant labels, a harvest/batch name, wet weight and unit of measure, location, license number, and harvest date to the plant harvest endpoint — harvesting is initiated on the Plants resource, not a separate harvests-create endpoint.
Confirm the resulting harvest batch appears in the active harvests listing.
Record any harvest waste using the harvest waste endpoint, citing a reason from the waste-types reference list.
Track the harvest's remaining weight before creating packages against it.
Once packaging and waste recording are complete, close out the harvest using the harvest finish endpoint.
Known gotchas
There is no "/harvests/create" endpoint — harvesting a plant is an action on the Plants resource.
The HTTP method for initiating a harvest differs between API v1 and v2.
A harvest batch tracks a running weight total; later package-creation calls draw against that remaining weight, so sequencing matters.
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?