[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # REVIEWS.io API and MCP server > REVIEWS.io has a REST API, but only on the Plus plan, and no official MCP server (checked 23 Oct 2026). The API index lists reads of reviews, invitations and the unsubscribe list, queuing and editing invitations, and tagging reviews. It lists no endpoint to reply to a review, moderate one or pause an invitation. Review collection platform for online stores: invitations by email and SMS, company and product reviews, a Timeline to reply to and moderate them, and widgets that show them on your site. ## What is the REVIEWS.io API? Cotlet's REVIEWS.io API exposes 13 endpoints for your own REVIEWS.io account: list reviews, get a review, draft a reply with REVIEWS.io AI, list invitations, list the unsubscribe list, reply to a review, send a review to moderation, tag reviews, pause invitations, resume invitations, add to the unsubscribe list, remove from the unsubscribe list and export reviews by email. The list_reviews endpoint returns company or product reviews from the Timeline with rating, text, reviewer, source, tags and replies. Each endpoint takes simple JSON inputs like review_id, date_from or date_to and works both as an operation of the reviews_io_read or reviews_io_write MCP tool for agents and as a REST call for scripts. - **Category:** [Marketing & SEO](https://cotlet.dev/integrations/category/marketing-seo.md) - **Endpoints:** 13 (5 read, 8 write) - **Updated:** 2026-10-21 REVIEWS.io has a REST API, but only on the Plus plan, and no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for REVIEWS.io with 13 endpoints (5 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does REVIEWS.io have an official API? REVIEWS.io has a REST API, but only on the Plus plan, and no official MCP server (checked 23 Oct 2026). The API index lists reads of reviews, invitations and the unsubscribe list, queuing and editing invitations, and tagging reviews. It lists no endpoint to reply to a review, moderate one or pause an invitation. | Task | REVIEWS.io official | Cotlet | |---|---|---| | Read company and product reviews | Yes: API on the Plus plan only | Yes | | Tag reviews | Yes: API on the Plus plan only | Yes | | List review invitations | Yes: API on the Plus plan only | Yes | | Reply to a review, publicly or privately | No | Yes | | Draft an AI reply | No: Auto Generate Reply is a dashboard button on the Plus plan | Yes | | Moderate a review | No | Yes | | Pause and resume invitations | Partly: The index lists edit endpoints for invitations, but no pause or resume | Yes | | Read and change the unsubscribe list | Partly: The index lists reading it and adding a user, not removing one | Yes | Sources: [REVIEWS.io developer docs: API index](https://developer.reviews.io/), [REVIEWS.io Help: REVIEWS.io API](https://support.reviews.io/en/articles/9185068-reviews-io-api), [REVIEWS.io Plans & Pricing](https://www.reviews.io/front/pricingplans), [REVIEWS.io Help: Managing and moderating reviews](https://support.reviews.io/en/articles/16530455-managing-and-moderating-reviews-on-reviews-io) ## Quick reference ```text REVIEWS.io has a REST API, but only on the Plus plan, and no official MCP server (checked 23 Oct 2026). The API index lists reads of reviews, invitations and the unsubscribe list, queuing and editing invitations, and tagging reviews. It lists no endpoint to reply to a review, moderate one or pause an invitation. Cotlet provides a hosted MCP server and REST API for REVIEWS.io: 13 tools (5 read, 8 write). Access Sign up at https://cotlet.dev/app/signup?app=reviews-io, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools reviews_io_read, reviews_io_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/reviews-io, each operation at its own route, e.g. POST /api/v1/reviews-io/reviews/{review_id}/replies Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_reviews, get_review, generate_reply_draft, list_invitations, list_unsubscribed, reply_to_review, moderate_review, tag_reviews, pause_invitations, resume_invitations, add_to_unsubscribe_list, remove_from_unsubscribe_list, export_reviews Confirm reply_to_review, moderate_review, tag_reviews, resume_invitations, remove_from_unsubscribe_list, export_reviews (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/reviews-io-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=reviews-io, requests REVIEWS.io in the Cotlet console and creates an API key there. 2. The user signs in to REVIEWS.io once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables REVIEWS.io for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted REVIEWS.io server that someone else maintains, including non-developers. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to REVIEWS.io in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get REVIEWS.io only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no REVIEWS.io login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following REVIEWS.io's terms; Cotlet is not affiliated with REVIEWS.io. ``` ## What can an AI agent do in REVIEWS.io? Cotlet is best for REVIEWS.io store owners and marketers who are not developers and want their AI agent to reply to reviews, moderate spam and pause invitations without running or fixing a server. - **[Reply to new reviews](https://cotlet.dev/integrations/reviews-io-api-mcp-server/reply-to-reviews.md)** (runs: daily): "Find reviews from the last 2 days in my REVIEWS.io Timeline that have no reply. Write a short reply for each in the tone of my earlier replies. Leave refunds and complaints for me." → `list_reviews`, `get_review`, `generate_reply_draft`, `reply_to_review` - **[Remove fake or spam reviews](https://cotlet.dev/integrations/reviews-io-api-mcp-server/moderate-fake-reviews.md)** (runs: weekly): "Look at 1 and 2 star reviews from the last week. Check whether the reviewer was ever invited. Send obvious spam to moderation with a reason and list the doubtful ones for me." → `list_reviews`, `get_review`, `list_invitations`, `moderate_review` - **[Pause review invitations during a delay](https://cotlet.dev/integrations/reviews-io-api-mcp-server/pause-review-invitations.md)**: "Pause the in-progress review invitations for orders 77410 to 77412 because their parcels are delayed. Resume them when I say the parcels arrived." → `list_invitations`, `pause_invitations`, `resume_invitations` - **Tag reviews for your widgets** (runs: weekly): "Tag this week's 5-star product reviews that mention "kettle" with the tag kettle-love." → `list_reviews`, `get_review`, `tag_reviews` - **Keep wholesale customers off review invitations**: "Add these wholesale customer emails to the unsubscribe list so they never get a review request, and show me the list afterwards." → `list_unsubscribed`, `add_to_unsubscribe_list` ## Can REVIEWS.io automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a REVIEWS.io connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to reply to new reviews, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/reviews-io/reviews. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/reviews-io/reviews with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to REVIEWS.io. ### list_reviews Company or product reviews from the Timeline with rating, text, reviewer, source, tags and replies. Access: read. REST: `GET /api/v1/reviews-io/reviews`. MCP: `reviews_io_read → list_reviews`. | Parameter | Type | Required | Description | |---|---|---|---| | `type` | enum | no | company or product. Default: company. | | `search` | string | no | Reviewer name or email address. | | `rating_min` | integer | no | Lowest star rating, 1 to 5. | | `rating_max` | integer | no | Highest star rating, 1 to 5. | | `date_from` | date | no | Only reviews on or after this date. | | `date_to` | date | no | Only reviews on or before this date. | | `cursor` | string | no | Next page cursor from the previous call. | Returns reviews as the Timeline shows them; type picks company or product reviews. Each review carries its replies, so an empty replies list means nobody answered. source says where the review came from, for example reviews_io, google or trustpilot. search matches the reviewer name or email address. Pass next_cursor back as cursor for the next page. Example response: ```json { "reviews": [ { "review_id": "4831902", "type": "company", "rating": 5, "reviewer": "Hannah Weiss", "source": "reviews_io", "created_at": "2026-10-21", "text": "Kettle arrived on time and boils fast.", "tags": [ "kettle" ], "replies": [] }, { "review_id": "4829417", "type": "company", "rating": 1, "reviewer": "Sam Cole", "source": "reviews_io", "created_at": "2026-10-20", "text": "Visit my-shop-deals.example for coupons.", "tags": [], "replies": [] } ], "next_cursor": "c2" } ``` ### get_review One review in full, with the reviewer email, product, tags and every reply. Access: read. REST: `GET /api/v1/reviews-io/reviews/{review_id}`. MCP: `reviews_io_read → get_review`. | Parameter | Type | Required | Description | |---|---|---|---| | `review_id` | string | yes | Review ID from list_reviews. | Returns the whole review text, not a preview, with the reviewer email, the product for a product review and the replies with their visibility, public or private. Use it before replying or moderating, and again right before posting to see whether someone answered in the meantime. Example response: ```json { "review_id": "4831902", "type": "company", "rating": 5, "reviewer": "Hannah Weiss", "reviewer_email": "hannah@example.com", "source": "reviews_io", "created_at": "2026-10-21", "text": "Kettle arrived on time and boils fast. The lid is a little stiff.", "product": null, "tags": [ "kettle" ], "replies": [] } ``` ### generate_reply_draft REVIEWS.io's own AI draft for a review, written in the review's language. Plus plan. Access: read. REST: `GET /api/v1/reviews-io/reviews/{review_id}/reply-drafts/generate`. MCP: `reviews_io_read → generate_reply_draft`. | Parameter | Type | Required | Description | |---|---|---|---| | `review_id` | string | yes | Review ID from list_reviews. | Presses Auto Generate Reply on one review and returns the draft text. Nothing is posted: the draft is yours to edit and send with reply_to_review. REVIEWS.io makes one draft per review and models it on the replies you have already posted. Accounts without the Plus plan get APP_PERMISSION_DENIED. Example response: ```json { "review_id": "4831902", "language": "en", "draft": "Thank you, Hannah. We are glad the kettle arrived on time." } ``` ### list_invitations Review invitations from Invitation History with status, type, email, order ID and send date. Access: read. REST: `GET /api/v1/reviews-io/invitations`. MCP: `reviews_io_read → list_invitations`. | Parameter | Type | Required | Description | |---|---|---|---| | `status` | enum | no | in_progress, paused, sent or responded. | | `invite_type` | enum | no | email or sms. | | `email` | string | no | Customer email address. | | `order_id` | string | no | Order ID the invitation was queued for. | | `date_from` | date | no | Start of the date range. | | `date_to` | date | no | End of the date range. | | `cursor` | string | no | Next page cursor from the previous call. | Returns invitations as Invitation History lists them, for email or SMS. status is in_progress, paused, sent or responded. A paused invitation carries the reason REVIEWS.io shows when you hover over Paused. Pass next_cursor back as cursor for the next page. Example response: ```json { "invitations": [ { "invitation_id": "9120456", "type": "email", "status": "in_progress", "email": "a.novak@example.com", "order_id": "77410", "send_date": "2026-10-24" }, { "invitation_id": "9120457", "type": "email", "status": "in_progress", "email": "l.mora@example.com", "order_id": "77411", "send_date": "2026-10-24" }, { "invitation_id": "9120460", "type": "sms", "status": "in_progress", "email": "j.tran@example.com", "order_id": "77412", "send_date": "2026-10-25" } ], "next_cursor": null } ``` ### list_unsubscribed Email addresses on your unsubscribe list, which stops review invitations to them. Access: read. REST: `GET /api/v1/reviews-io/unsubscribeds`. MCP: `reviews_io_read → list_unsubscribed`. No parameters. Returns the addresses shown under Settings > Unsubscribe List. Invitations are not sent to these addresses. Use it before add_to_unsubscribe_list to avoid duplicates. Example response: ```json { "emails": [ "wholesale@example.com", "buyer@example.org" ] } ``` ### reply_to_review Posts a public reply under a review, or a private reply to the reviewer. Access: write, asks the user first. REST: `POST /api/v1/reviews-io/reviews/{review_id}/replies`. MCP: `reviews_io_write → reply_to_review`. | Parameter | Type | Required | Description | |---|---|---|---| | `review_id` | string | yes | Review ID from list_reviews. | | `body` | string | yes | Reply text. | | `visibility` | enum | no | public or private. Default: public. | Presses Post Public Reply, or Private Reply when visibility is private. A public reply shows with the review; a private reply goes to the reviewer. Trustpilot reviews cannot be answered in REVIEWS.io and fail with an error. The help center does not describe editing a reply after it is posted, so check the text first. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "review_id": "4831902", "visibility": "public", "status": "posted", "body": "Thank you, Hannah. Glad the kettle arrived on time. If the lid ever sticks, write to support@northwindkitchen.example and we will send a new one." } ``` ### moderate_review Files a moderation request for a review with a reason, as the Moderate button does. Access: write, asks the user first. REST: `POST /api/v1/reviews-io/reviews/{review_id}/moderate`. MCP: `reviews_io_write → moderate_review`. | Parameter | Type | Required | Description | |---|---|---|---| | `review_id` | string | yes | Review ID from list_reviews. | | `reason` | string | yes | Why the review should go, in your words, for example "not a real customer", "offensive content" or "incorrect company". | Clicks Moderate on the review and submits the reason. REVIEWS.io decides, usually within about an hour, and the change shows within an hour after that, so the status is submitted at first. Google-sourced reviews have no Moderate button and fail. Cotlet has no tool to undo a moderation. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "review_id": "4829417", "status": "submitted", "reason": "not a real customer" } ``` ### tag_reviews Adds one tag to the reviews you select, creating the tag if it does not exist. Access: write, asks the user first. REST: `POST /api/v1/reviews-io/reviews/tag`. MCP: `reviews_io_write → tag_reviews`. | Parameter | Type | Required | Description | |---|---|---|---| | `review_ids` | array | yes | Review IDs from list_reviews. | | `tag` | string | yes | Tag name. | Uses Bulk Tag Reviews in the Timeline: selects the reviews, searches for the tag and creates it when it is missing. Tags reach no customer, but widgets can show reviews by tag, so a tag can change what visitors see. A tag disappears from REVIEWS.io once no review carries it. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "tag": "kettle-love", "tagged": 2, "review_ids": [ "4831902", "4831977" ] } ``` ### pause_invitations Pauses invitations that are in progress, keeping them and their place in the queue. Access: write. REST: `POST /api/v1/reviews-io/invitations/pause`. MCP: `reviews_io_write → pause_invitations`. | Parameter | Type | Required | Description | |---|---|---|---| | `invitation_ids` | array | yes | Invitation IDs from list_invitations, up to 100. | Pauses up to 100 invitations per call, the same as the dashboard. Only in_progress invitations can be paused. A paused invitation is not deleted and is undone with resume_invitations, so this tool does not ask for your OK. Customers get nothing while it is paused. Example response: ```json { "paused": 3, "invitations": [ { "invitation_id": "9120456", "status": "paused" }, { "invitation_id": "9120457", "status": "paused" }, { "invitation_id": "9120460", "status": "paused" } ], "skipped": [] } ``` ### resume_invitations Restarts paused invitations in their old queue position, so customers receive them. Access: write, asks the user first. REST: `POST /api/v1/reviews-io/invitations/resume`. MCP: `reviews_io_write → resume_invitations`. | Parameter | Type | Required | Description | |---|---|---|---| | `invitation_ids` | array | yes | Invitation IDs from list_invitations with status paused. | Clicks Resume on the paused invitations. Invitations to unsubscribed addresses, invitations overdue by more than 4 weeks and those blocked by a marketing-consent gate cannot be resumed and come back in skipped with the reason. Resumed invitations are sent to customers. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "resumed": 2, "invitations": [ { "invitation_id": "9120456", "status": "in_progress" }, { "invitation_id": "9120457", "status": "in_progress" } ], "skipped": [ { "invitation_id": "9120460", "reason": "overdue by more than 4 weeks" } ] } ``` ### add_to_unsubscribe_list Adds email addresses to your unsubscribe list so they get no review invitations. Access: write. REST: `POST /api/v1/reviews-io/unsubscribe-lists`. MCP: `reviews_io_write → add_to_unsubscribe_list`. | Parameter | Type | Required | Description | |---|---|---|---| | `emails` | array | yes | Email addresses to add. | Types the addresses into Settings > Unsubscribe List and clicks Add Emails. It reaches no one and is undone with remove_from_unsubscribe_list, so it does not ask for your OK. Invitations already queued for these addresses are not part of this tool; check them with list_invitations. Example response: ```json { "added": 2, "emails": [ "wholesale@example.com", "buyer@example.org" ] } ``` ### remove_from_unsubscribe_list Deletes an address from your unsubscribe list, so it can get review invitations again. Access: write, asks the user first. REST: `DELETE /api/v1/reviews-io/unsubscribe-lists`. MCP: `reviews_io_write → remove_from_unsubscribe_list`. | Parameter | Type | Required | Description | |---|---|---|---| | `email` | string | yes | Address from list_unsubscribed. | Clicks Delete next to the address in Settings > Unsubscribe List. That customer can receive review invitations again. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "removed": "buyer@example.org" } ``` ### export_reviews Emails a CSV or JSON export of reviews to an address you name. Start Up plan and above. Access: write, asks the user first. REST: `POST /api/v1/reviews-io/reviews/export`. MCP: `reviews_io_write → export_reviews`. | Parameter | Type | Required | Description | |---|---|---|---| | `type` | enum | yes | company, product or questions_and_answers. | | `send_to` | string | yes | Email address that receives the file. | | `format` | enum | no | csv or json. Default: csv. | | `date_from` | date | no | Date From. | | `date_to` | date | no | Date To. | | `rating_min` | integer | no | Minimum rating, 1 to 5. | | `rating_max` | integer | no | Maximum rating, 1 to 5. | Fills in Settings > Export Reviews: type is company, product or questions_and_answers, with an optional date range and rating range. REVIEWS.io emails the file; it is not returned here. The file includes reviewer names and emails, so it goes only where you send it. Accounts below the Start Up plan get APP_PERMISSION_DENIED. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "type": "company", "format": "csv", "status": "requested", "send_to": "reports@northwindkitchen.example" } ``` ## How do I connect REVIEWS.io to Claude Code, Codex or Cursor? Connecting REVIEWS.io takes three steps: sign up, sign in to REVIEWS.io once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect REVIEWS.io to your agent. 1. **Create an account** Sign up and add REVIEWS.io in the console. Your API key is there too. 2. **Sign in to REVIEWS.io in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to REVIEWS.io there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. Claude Code: ``` claude mcp add --transport http cotlet \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` Cursor: ``` { "mcpServers": { "cotlet": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the REVIEWS.io tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` Find reviews from the last 2 days in my REVIEWS.io Timeline that have no reply. Write a short reply for each in the tone of my earlier replies. Leave refunds and complaints for me. ``` ### Call REVIEWS.io from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/reviews-io with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` curl -X POST https://cotlet.dev/api/v1/reviews-io/reviews/4831902/replies \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"body":"Thank you, Hannah. Glad the kettle arrived on time. If the lid ever sticks, write to support@northwindkitchen.example and we will send a new one.","visibility":"public"}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "review_id": "4831902", "visibility": "public", "status": "posted", "body": "Thank you, Hannah. Glad the kettle arrived on time. If the lid ever sticks, write to support@northwindkitchen.example and we will send a new one." } ``` ## Why use Cotlet for REVIEWS.io? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to REVIEWS.io yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When REVIEWS.io changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect REVIEWS.io to Cotlet? Yes. You sign in to REVIEWS.io yourself, in your own Cloud Browser, and we never save your password. Your agents only get REVIEWS.io once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **Who runs Cotlet?** Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet. **Is this an official REVIEWS.io integration?** No, Cotlet is independent of REVIEWS.io. REVIEWS.io's own API is too limited for this work. Cotlet works through your own REVIEWS.io account, the way you use REVIEWS.io in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to REVIEWS.io in your console: your agents lose access at once and you stay signed in. Signing out of REVIEWS.io in the browser works too, and Reset browser deletes the whole profile. ## Is there a REVIEWS.io MCP server on GitHub? No community MCP server for REVIEWS.io showed up in our check. The usual route is Zapier, where REVIEWS.io sends review data to a webhook from an invitation Flow, and the Zap does the rest. REVIEWS.io's own help center lists no Zapier actions, so a Zap cannot reply to a review or moderate one. Cotlet works in your dashboard instead, so it can do what you do there. | | Zapier | Cotlet | |---|---|---| | Setup | Add a Webhook by Zapier step to an invitation Flow, then build the Zap | Sign up, sign in to REVIEWS.io once, add one MCP server or API key | | When REVIEWS.io changes | The webhook keeps working; anything built on pages you click by hand is up to you | Our team tests it daily and fixes it for you; failed calls are free | | Your REVIEWS.io session | No session: the webhook is a one-way push from a Flow | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | When the session expires | Not applicable to a webhook | Your Cloud Browser keeps you signed in; if REVIEWS.io logs you out, your agent gets a link to sign in again | | Upkeep | You maintain each Zap | Nothing to host or update | | Where it runs | Zapier, triggered by a Flow's webhook | Hosted: Claude Code, Codex, Cursor, n8n, Make, Zapier and scripts, also on a schedule | | Price | Zapier plan on top of REVIEWS.io | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when REVIEWS.io changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the REVIEWS.io API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the REVIEWS.io API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | Credits | Price, one time | Calls at 10 credits | Per 1,000 credits | |---|---|---|---| | 5,000 | $29 | 500 | $5.80 | | 15,000 | $79 | 1,500 | $5.27 | | 32,000 | $149 | 3,200 | $4.66 | | 60,000 | $249 | 6,000 | $4.15 | Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own REVIEWS.io account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to REVIEWS.io yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get REVIEWS.io only after you enable it. When REVIEWS.io signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to REVIEWS.io, sign out of REVIEWS.io in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **REVIEWS.io's terms:** You use your own REVIEWS.io account and stay responsible for following REVIEWS.io's terms. Cotlet is independent and not affiliated with REVIEWS.io. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open REVIEWS.io in the console and press Request access. Then you create your API key and connect REVIEWS.io there. **Do I need to be technical?** No. You sign in to REVIEWS.io once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect REVIEWS.io to Cotlet?** Yes. You sign in to REVIEWS.io yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get REVIEWS.io once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My REVIEWS.io sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your REVIEWS.io cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through REVIEWS.io's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. REVIEWS.io sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no REVIEWS.io login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** REVIEWS.io offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **Do I need REVIEWS.io's Plus plan?** No. Cotlet works in your own dashboard, so it does not use the API, which REVIEWS.io limits to the Plus plan. Some dashboard features still follow your plan: Auto Generate Reply needs Plus, and export by email needs Start Up or above (REVIEWS.io pricing page and help center, checked 23 Oct 2026). A call to a tool your plan lacks fails with APP_PERMISSION_DENIED. **Can it answer Trustpilot or Google reviews?** Not Trustpilot: REVIEWS.io cannot reply to Trustpilot reviews, so they are answered on Trustpilot. Google-sourced reviews have no Moderate button and are reported on Google. Both are skipped and listed for you (REVIEWS.io Help: Managing and moderating reviews). **How long does a moderation request take?** REVIEWS.io says a decision usually takes about an hour, and the change shows within an hour after that. moderate_review returns status submitted at once, and the review changes after REVIEWS.io decides. **Can my agent post or send messages in REVIEWS.io without asking me?** No. Every call to reply_to_review, moderate_review, tag_reviews, resume_invitations, remove_from_unsubscribe_list or export_reviews waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. pause_invitations and add_to_unsubscribe_list run without asking, because they send nothing to anyone and one call undoes it. **Can I use the REVIEWS.io API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/reviews-io from the HTTP Request node. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.