Open source review monitoring: looot-reviews
Read public reviews of your company and your competitors and group them into themes.
The code is MIT open source. The data is not free and not self-hosted: every real run calls looot and pays per call at the catalog price shown before the run.
Short answer
What is looot-reviews?
looot-reviews is an MIT-licensed web app and CLI. Name your company or place and its competitors. It pulls public reviews, groups them into themes with counts and example quotes, tracks the average rating by month and lists themes where a competitor's customers are unhappy and yours are not. The code is open source. The data is paid per looot call.
What it does
What looot-reviews does and how to run it
Name a target and its competitors on the command line or in a YAML file. Google Maps needs only a name. App Store, Google Play and Tripadvisor need an id for each place or app.
It groups reviews into themes by counting words, with no LLM needed, and shows counts and example quotes. It tracks the average rating by month and lists themes where a competitor is weak and you are not. An optional LLM step can merge themes if you set your own key.
The CLI prints the plan and a maximum cost before it runs, and the maximum counts every page it may fetch. Results go to JSON, CSV and a markdown brief.
This is the job that products such as ReviewTrackers do.
git clone https://github.com/loootai/looot-reviews && cd looot-reviews
npm install --ignore-scripts
npm run demo
npm run reviews -- --demo --out out
npm run reviews -- --config reviews.example.yaml --dry-run
export LOOOT_TOKEN=...
npm run reviews -- --target "Blue Door Cafe @ Austin TX" --competitors "Copper Pot @ Austin TX; Tin Roof @ Austin TX" --max-spend 0.10 --out outFacts
Facts from the repository
Read from GitHub on 2026-10-11.
| Job | Read public reviews of your company and your competitors and group them into themes. |
|---|---|
| License | MIT |
| Language | TypeScript |
| A real run needs |
|
| Demo mode | Yes. npm run demo shows invented shops with generated reviews, and --demo writes the same data as files. Both need no token and make no looot call. |
| Repository | github.com/loootai/looot-reviews |
| Facts read on | 2026-10-11 |
Data and price
Endpoints it calls, with the live price
Every real run calls these looot endpoints. The price column is read live from the catalog, never typed into this page.
| Endpoint | Used for | Live price |
|---|---|---|
| serper-placesserper | Google Maps place lookup | reading live price |
| serper-reviewsserper | Google Maps reviews, per page | reading live price |
| searchapi-io-apple-product-reviewssearchapi-io | App Store reviews, per page | reading live price |
| anysite-api-google-play-apps-reviewsanysite | Google Play reviews | reading live price |
| searchapi-io-tripadvisor-reviewssearchapi-io | Tripadvisor reviews, per page | reading live price |
Prices are read from the looot public catalog when the page loads. Some endpoints are priced per result, so a run that returns many rows costs more than one call. The CLI dry run prints the exact quote for your input before anything is charged.
Limits
What looot-reviews does not do
- It reads public reviews as providers return them. It does not reply, post or monitor continuously. Run the CLI on a schedule if you want that.
- It keeps rating, text, title and date, and does not keep reviewer names.
- It fetches the first pages the provider gives, up to 5 pages per source, not every review of a large place.
- Trustpilot, G2 and Yelp are missing because the catalog has no endpoint for them.
- Sentiment is the star rating, not text analysis. Themes count words, work on English text only, and a set under about 30 reviews gets a warning.
- The web form reads Google Maps only. Use the CLI with a YAML file to add the other sources.
- Response parsing was written from provider documentation and fixtures. The README says it was not checked against a recorded paid response.
With an agent
Run it with your agent
Copy the prompt, give it to the agent you already use, and it dry-runs first.
FAQ
Questions about looot-reviews
Keep going
Related on looot.ai
- Google Maps scraper
A free tool you can run in the page
- Free tools
Jobs you can run in the page
- All open source repos on looot
The hub with every repo
- repo
- https://github.com/loootai/looot-reviews
- job
- Read public reviews of your company and your competitors and group them into themes.
- license
- MIT
- language
- TypeScript
- endpoint
- serper: serper-places (maps_local_search)
- endpoint
- serper: serper-reviews (maps_place_reviews)
- endpoint
- searchapi-io: searchapi-io-apple-product-reviews (reviews_appstore_reviews)
- endpoint
- anysite: anysite-api-google-play-apps-reviews (api_google_play_apps_reviews)
- endpoint
- searchapi-io: searchapi-io-tripadvisor-reviews (search_tripadvisor-reviews)
- price
- per call, read live from the catalog on the web page
- framing
- MIT code, paid data, every real run calls looot
- setup
- https://looot.ai/skill.md
- llms.txt
- https://looot.ai/llms.txt
- read
- 2026-10-11
Run looot-reviews on your own looot account.
Try the demo first, no account needed. For a real run, start your workspace, top up, and use the quote the repo prints before it spends anything.