Let an AI assistant fill your sales pipeline
A Prospects API with an OpenAPI description, so an AI assistant can find shops nobody has called yet and add them to your pipeline without duplicating any.
What you do today
You ask a chatbot for the cafés in the next town, get a tidy list back, and then type every one of them into your system by hand — checking each against the shops you already have.
One concrete detail
A shop that is already on your books comes back as duplicate rather than being added twice, and one bad row in a batch of a hundred is reported on its own while the other ninety-nine still land. Nothing sent in can mark a shop as agreed or assign it to a Seller.
This page targets no search term; nobody searches for it yet. It is here because the slowest part of finding new shops is no longer finding them — an AI assistant will list every bakery in a town in a minute — it is getting that list into the place where you actually work.
What it is for
The case it is built for: you ask an assistant for the shops in a town you have never called, and instead of handing you a list to copy, it adds them to your pipeline. They appear as cold leads, on the map, with whatever it found — a note, a phone number, the Google place, the chain it belongs to.
Safe to run twice
An assistant asked the same question next week will find the same shops. So it can read your pipeline first, and anything it sends that you already have comes back marked as a duplicate rather than as a second copy of the same corner shop. A row it gets wrong — a town that is not one of your regions, a shop with no name — is reported back on its own, and the rest of the batch still lands.
What it cannot do
It cannot say a shop has agreed to stock you, and it cannot hand a shop to a Seller. Everything that arrives is a lead, and nobody’s: a person on your team claims it. Nor does it reach your stockists, your prices or your money — a prospects key opens the pipeline and nothing else.
For whoever sets it up
The API uses a bearer key and is described in OpenAPI, with an integration guide written to be read by an assistant as much as by a developer. It sits alongside the stockists API, which publishes your shop list to a website; the two use separate keys on purpose.
Common questions
- What can the API do?
- Read the prospects already in your pipeline and the names of your regions, and add new prospects — up to a hundred per request, with a note, a contact, a Google place and the chain each belongs to.
- Can I use it with Claude or another AI assistant?
- Yes. The API is described in OpenAPI and documented for an assistant to read, so an assistant that can call a web API can search your pipeline and add shops for you.
- How is it secured?
- With a key an administrator creates under Settings, shown once. A key carries exactly one scope, so a prospects key cannot read your stockist list and the stockists key behind a website cannot add to your pipeline.
- Does a prospect added this way belong to anybody?
- No. It arrives as a lead with no owner. Somebody on your team takes it from the pipeline, and that is the moment it becomes theirs.