Check the source harvest's remaining weight before packaging.
Obtain an available package tag from the tag-availability endpoint.
Confirm a valid item and unit of measure exist for the package type via the active items endpoint.
Submit an array of package objects (source harvest, tag, item, quantity, unit of measure, location) to the harvest packages endpoint, keeping each request to 10 or fewer objects.
Use the dedicated testing-package endpoint specifically when creating a lab-sample package, rather than the standard packaging endpoint.
Confirm the new package appears in the active packages listing.
Known gotchas
Requesting more package weight than the harvest has remaining returns an error.
The standard and testing-sample package-creation endpoints are separate; using the wrong one mislabels the package's purpose.
Package tags must come from your state-issued tag pool, not arbitrary values.
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?