Compare products across retailers
Ask for a product, pack size or category and return matched product groups with shelf prices, member prices and unit prices across the four major retailers.
MCP-compatible access · self-serve or managed
BasketWatch Agent Access exposes the live grocery dataset through a managed private layer for analyst copilots, internal chat tools and automated reporting workflows. It is designed for commercial teams that want answers with prices, promotions, unit prices and evidence attached.
Two ways in
Most teams do not need anything bespoke. The MCP server runs locally against your own API key, so your assistant queries the live dataset directly and your credits meter exactly as they do on a direct HTTP request. Nothing proxies through us.
{
"mcpServers": {
"basketwatch": {
"command": "python",
"args": ["-m", "basketwatch_mcp"],
"env": {
"BASKETWATCH_API_BASE": "https://basketwatchireland.com",
"BASKETWATCH_API_KEY": "YOUR_KEY",
"BASKETWATCH_MCP_MAX_ROWS": "200"
}
}
}
}
Seven tools: search, cross-retailer comparison, promotions, price changes, new lines, removed lines and catalogue listing. Each call returns up to 200 rows by default, and without a key you still get a live 50-row sample, so you can try it before buying. Full setup is in the API reference.
Your credit pack covers this. No separate MCP plan and no second balance: a pack bought on the pricing page is the same credits whether the records are pulled by your own code or by your assistant. One record returned, one credit.
An autonomous agent can purchase its own credits and start querying, with no browser and no card entry, by paying over MPP with a Stripe shared payment token.
/api/credits/mpp402 payment challengePayment terms are HMAC-bound, so an edited challenge is refused, and the charge is idempotent, so a retry cannot bill the card twice. Documented in the API reference and described for machines at /llms.txt.
Managed access still exists for teams who want scoped workflows, dedicated capacity or an SLA. That is a conversation, not a signup.
Live agent session
A real workflow: a question goes in, the agent calls structured BasketWatch tools over MCP, and the answer comes back with retailers, prices and unit prices attached, never a guess.
What it can do
The agent layer is not a general chatbot. It is a focused interface over structured Irish grocery data across Aldi, Tesco, SuperValu and Dunnes Stores.
Ask for a product, pack size or category and return matched product groups with shelf prices, member prices and unit prices across the four major retailers.
Surface current Clubcard, Real Rewards, multibuy, was-price and member-only offers with the underlying offer text preserved.
Turn daily changes into readable summaries: what rose, what fell, by how much, and where the evidence came from.
Identify newly listed products, removed products and range churn by retailer, category or search term.
Build daily category notes, promotion roundups, competitor snapshots and customer-ready summaries from the latest snapshot.
Responses can include scrape dates, retailer names, product URLs, IDs and row-level context so an analyst can verify the conclusion.
Private tool layer
The agent uses controlled BasketWatch data tools, then writes the answer from returned rows. That keeps the LLM away from guessing prices or inventing promotional context.
Retailer, product name, product ID and product URL where available.
Shelf price, member/effective price and unit price basis.
Promotion label, was-price, loyalty pricing and validity text where captured.
Scrape date and freshness context for the data used.
Clear “not enough data” responses when a match is weak or unavailable.
How access works
The public site shows what the layer can do; the implementation stays private so access is controlled, metered and supported. Four steps from scope to live.
Agree the use case: analyst chat, daily brief, watchlist, comparison or internal copilot.
Usage caps, data access, cadence and support level matched to the team and subscription.
Approved customers get private setup details and keys. Connector internals stay unpublished.
Answers check against row-level evidence so teams trust the data behind the summary.
Pricing model
Separate from the public API marketplace. Best for teams that already know they want BasketWatch data inside an AI workflow and need controlled access, support and usage boundaries.