# Open source review monitoring: looot-reviews 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. Read public reviews of your company and your competitors and group them into themes. ## Short answer 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 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. ## Commands 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 out ## Facts - Job: Read public reviews of your company and your competitors and group them into themes. - License: MIT - Language: TypeScript - Needs: Node.js 22.12 or newer - Needs: A looot token with the scopes runs.execute, catalog.read, runs.read and usage.read, for real pulls only - Needs: A funded looot balance, for real pulls only - Needs: An admin password of 12 characters or more for the web app outside the demo - 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: https://github.com/loootai/looot-reviews ## Endpoints it calls - serper: serper-places (maps_local_search), Google Maps place lookup - serper: serper-reviews (maps_place_reviews), Google Maps reviews, per page - searchapi-io: searchapi-io-apple-product-reviews (reviews_appstore_reviews), App Store reviews, per page - anysite: anysite-api-google-play-apps-reviews (api_google_play_apps_reviews), Google Play reviews - searchapi-io: searchapi-io-tripadvisor-reviews (search_tripadvisor-reviews), Tripadvisor reviews, per page ## What it 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. ## Run it with an agent Use looot to find what customers complain about at my competitors. Read https://looot.ai/skill.md first. Then clone https://github.com/loootai/looot-reviews, write my company and my competitors into a YAML file, run its dry run and show me the quote and the cap. Run the real pull only after I say yes, and list the themes where competitors are weak and I am not. ## What does looot-reviews do? It pulls public reviews of your company and your competitors through looot, groups them into themes with counts and example quotes, tracks the average rating by month and shows where a competitor's customers are unhappy. ## Is looot-reviews free? The code is free under the MIT license. The data is not. Every real pull is a set of paid looot calls at the catalog price, quoted before the run. Demo mode and the dry run cost nothing. ## Which review sources does it read? Google Maps, the App Store, Google Play and Tripadvisor. Trustpilot, G2 and Yelp are not included, because the catalog has no endpoint for them. ## Does it need an LLM key? No. Themes come from counting words. An optional LLM step can merge themes if you set your own key and model, and it is off by default. ## What does a pull cost? One place lookup and a number of pages per source. The table on this page shows the live catalog price of each endpoint, and the dry run prints the plan with a maximum, because later pages are fetched only when the provider says there are more. ## What does it not do? It does not reply to reviews, post, or monitor on its own. Sentiment is the star rating, themes work on English text, and it keeps no reviewer names. ## Can I try it without a looot account? Yes. npm run demo and the CLI --demo flag use invented shops and need no token. A real pull needs a token and a funded balance. ## How do I run it from an agent? Give your agent the prompt on this page and the setup link https://looot.ai/skill.md. The repo ships a skill that dry-runs first, shows the total and runs only after you agree. ## Related - /open-source-alternatives - /free-tools/google-maps-scraper - /free-tools ## Last read 2026-10-11. Facts come from the repository on GitHub. The price per call is read live from the catalog on the web page.