Grocey is a supermarket API for AI shopping agents: sign in once to a real grocery account and get back real order history, real delivery addresses and slots, and a cart it can actually fill, not a public catalog to browse.
I want to cook carbonara and tomato soup this week, plus my usual items
Carbonara for four needs spaghetti, guanciale, eggs and pecorino; tomato soup needs canned tomatoes, onion, garlic and stock. Here's what Grocey found and filled at your store, plus your usual repeat items:
This week's meals
Your usual, from repeat orders
Cart filled for the week, delivery slot held. You tap buy at Delio to place it.
Real field names from the groceries contract (GroceryCart, GroceryLine, GroceryFulfilmentSlot, topProducts). Example values, not a captured account.
What did I order last time from Delio? Reorder it
Your last Delio order: 7 items, 69.93 PLN. Grocey re-added every line to a fresh cart:
Delio, Warszawa · 7 items · 69.93 PLN
Reordered from last time
Same order, refilled in your cart, delivery slot held. You tap buy at Delio to place it.
Real field names from the groceries contract (GroceryCart, GroceryLine, GroceryFulfilmentSlot, topProducts). Example values, not a captured account.
Add ingredients for this, for 4 people, to this week's groceries
That's a baked ziti with a side salad, portioned here for four. Grocey matched the ingredients at your store:
For 4: baked ziti and salad
Cart filled for four, delivery slot held. You tap buy at Delio to place it.
Real field names from the groceries contract (GroceryCart, GroceryLine, GroceryFulfilmentSlot, topProducts). Example values, not a captured account.
Why an account, not a catalog
A catalog API can list what a store sells. It was never signed in to your account, so here is what it cannot see, and what Grocey reads instead.
A catalog API has no account to read, so it has no order history either. Grocey signs in to your real account and reads what you actually bought, when, and for how much.
A catalog API can only guess at delivery. Grocey reads your real saved addresses and the delivery slots your account actually sees today, not a generic estimate.
A catalog API hands you a product list and leaves you to rebuild the cart yourself. Grocey fills a real cart on your real account, ready for you to check out with one tap.
A catalog API shows the same product list to everyone. Grocey reads whatever your account actually sees: stock, prices, and slots as they exist for you.
Consumer products
Connect your own assistant today. Grocey Chat, a standing shopping agent of its own, is next.
End users
One URL turns Grocey into a tool your assistant can call: search a store, check your cart, ask what is in your delivery slot today.
Set it up →Meal planning
Plan the week, then fill a real cart at a real store from the plan. The meal plan is AI, the basket is your actual account.
See how it works →A standing shopping agent on iMessage. Not built yet.
For builders
Two APIs, kept separate from the two consumer doors above: the write API that acts on someone's own account, and the catalogue it reads along the way.
Builders
Signed API keys, connect links, and webhooks over MCP or REST. One contract, and every provider implements it the same way.
Read the docs →Builders
Read the crawled catalogue behind a store Grocey supports: product names, prices in minor units, availability, images and categories, from the live site rather than a syndicated feed. Paginated, and bounded to the stores Grocey crawls today.
See the endpoints →Coverage · live data
Generated at build time from the exact same provider declarations the API reads: never fetched live, never a second list to let drift from the truth. Each provider links to its own page below.
BE · 1 provider
LU · 1 provider
Poland · 4 providers
Polish grocery delivery. Sign in with your phone number and an SMS code.
Polish online supermarket with van delivery. Sign in with your e-mail and password.
Żabka's express grocery delivery in Poland. Same account and sign-in as Delio.
Groceries and shops on Wolt. Sign in with the link Wolt mails to your address.
Roadmap · not built yet
These are not in the capability cards above because they are not real yet. When they ship, they move up.
Grocey fills the cart. Placing the order is still a human tap today. A checkout method exists in the contract, but it's switched off by default, and nothing has placed a real order through it yet.
Pulling a receipt or an invoice out of a completed order is not built yet.
Putting a delivery slot on a calendar automatically is not built yet.
Per item nutrition data alongside search results is not built yet.
FAQ
Not for self-serve signup. Grocey already runs in production as the connector behind Alfredo, our own concierge agent. The gro_* keys, connect links, and webhooks described on this site are the interface we're building toward. Request access to be part of private beta.
Delio, in Poland, is the only provider that has ever completed a real connect. Collect&Go, Frisco.pl, Żabka Jush and Wolt are built and unit-tested, but none of them has ever connected to a real account, so we label them honestly instead of counting them as coverage.
It takes you to your Grocey dashboard. Sign in with Google or a one time code we email you, then connect your own store and see what Grocey can see: your recent orders, your addresses, your cart. It is a live demonstration of the account level read, not a signup for the developer API.
It drives the real grocery site in an isolated browser session, the same way a person would sign in by hand: no scraping shortcuts, no shared credentials, no partnership required.
Search, store and fulfilment options, and, where the provider supports it, order history and a live, editable cart. Where a provider genuinely can't answer something, the API says so explicitly rather than returning an empty result that looks like a fact about the account.
Sign in with Google or a one time email code, connect your own store, and see what Grocey reads back. Building something on top of it? Request access to the developer API.