A verdict per option
Fits, fails or cannot tell, for every requirement, with the value and where it came from.
Product
Personalise the Storefront
For AI Agents
Industries
By Goal
Resources
For AI agents
Your assistant knows what the shopper asked for. Pulse tells it which products the listings prove fit, which fail, and which say nothing, so it recommends from evidence and says plainly what it cannot tell.
Where you are
Ask a language model which laptop has 16GB of RAM and it will pick one, even when the listing never stated the memory. The shopper buys on that answer, and the return reason says "not as described".
"The listing does not say" is a better answer than a confident guess.
What happens
One call, from MCP or HTTP. Nothing to train, nothing stored.
As requirements such as "voltage = 24V", or in plain words; a budget in the words becomes a price requirement.
Up to 50 at a time, with whatever fields and text you have. A stated field always wins over text read off a page.
Each option comes back fits, fails or cannot tell, with the attributes that are missing. The agent says what the evidence shows, and only that.
What you get
Fits, fails or cannot tell, for every requirement, with the value and where it came from.
A first-class answer instead of a guess, with the missing attributes named.
Every unknown is exactly what the option's owner should publish next.
The open-source MCP server for agents, or one HTTP call from your own code.
"Laptop under $1,500 with 16GB RAM": one fits, one fails on price, one cannot tell because its listing never states the RAM.
What you get
Without Pulse
With Pulse
Before you commit
Questions
Install the MCP server with one line, or call the API from your code. The open-source repository has runnable examples.
An API key comes from the Pulse dashboard.