Is it legit? Reviews trust checker

Reserves a submission and returns an upload_url. POST the complete JSON payload (format from describe_review_source) to it from your own environment or the user's browser; the HTTP response is the trust report. The URL is a secret that completes the submission under YOUR identity whoever posts to it, so the POST needs no key. Alternatively feed the same submission_id to submit_reviews in inline chunks. Pending submissions expire after 2 hours (or are closed as superseded when you one-shot the same place instead).

Call first. Resolves a Google Maps link or place_id and reports whether a trust result is cached, how fresh it is, and a recommendation: use the cached result, or collect and submit the reviews (also when a cached single-source result would benefit from your corroboration). Never contacts Google.

Read this BEFORE scraping. Returns, per platform, the exact submission format: identity fields for the listing, the per-review fields (required vs optional; everything required is visible on the review card), where each lives on the platform's pages, the sort-by-newest and 500-most-recent rules, an example payload, and how to deliver it. Without a platform it lists the supported platforms. Only Google Maps exists today.

Fallback for when you cannot reach a browser tab signed in to Google. Queues a server-side pull of the listing's newest reviews (the same worker as the site's form) and scores it. Ask the user first: it spends one of their server-side fetches for the month (check_place's serverFetch block says how many are left). Returns the job's progress; call again with job_id every 10-15 seconds until status is done (the result is then in the response) or failed (nothing is spent). Takes a Maps link, including share short-links, or a place_id. A place that is already scored returns its result without a fetch.

For a submission fed by inline chunks: validates, scores, stores and returns the report. For one already uploaded to its upload_url: returns the stored report. Pending with nothing uploaded yet: says so.

The cached fraud analysis for a place: verdict (looks_legit / not_sure / past_manipulation / inflated / manipulated) with its label and a one-sentence summary, letter grade, 0-100 trust score, the adjusted rating credible reviewers actually give (vs the headline average), reviewer-mix tiers, review-injection statistics, cross-business duplicate-review evidence, red flags, and provenance. Cache only: on a miss, collect and submit the reviews (see check_place).

The ranked directory of places already analyzed for review fraud, best adjusted rating first (what the site's home and city pages show). 25 per page. Optional city or curated-list filter; the response lists the available cities/lists and their counts.

Submit the review feed inside the tool call. Without submission_id this is a one-shot submission of the whole payload (fine up to about 150 reviews). For more, call begin_submission, then send chunks of up to 150 reviews each with the same submission_id and final=false; send final=true with the last chunk (the identity fields may arrive with any chunk). Use this only when you cannot POST to the upload_url yourself (no page fetch, no curl): retyping reviews you already hold in a page or script is slow and error-prone. Returns the trust report when finalized.

After a submission is finalized: send the summary you give the user of what recent reviewers praise (pros), complain about (cons) and advise (tips), up to 6 short plain-English sentences per list, drawn from reviews by established accounts rather than one-off ones. It is shown on the place's page next to the trust result and never affects the score. The same lists can travel inside the submission payload as `takeaways` instead. Only an accepted or kept submission can carry one; calling again replaces yours.