Complete the OAuth 2.0 authorization code flow with the cart.basic:write and profile.compact scopes to obtain a user-scoped access token
Locate the target store using the Locations API and confirm the user's preferred locationId
Build the cart request payload containing an array of items, each with a upc and quantity; validate that UPCs correspond to items available at the selected location
PUT or POST the cart payload to the Cart API endpoint; on success the items will appear in the user's Kroger.com cart
Handle partial success responses: the API may succeed overall but flag individual items that could not be added (e.g., unavailable at location); surface those to the user
Do not attempt to complete checkout programmatically — the Cart API adds items only; the customer must complete checkout on Kroger's owned surfaces
Known gotchas
The Cart API is limited to adding items; reading the current cart contents or removing items may require separate scope or may not be supported in the public tier — check your approved scopes
User tokens expire; implement proactive refresh so a long shopping session does not produce a mid-flow 401 when the customer tries to add a final item
Kroger's cart is a single shared cart per user account — adding items via the API will merge with whatever the user already has in their cart on Kroger.com, which may surprise users
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp