[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)

# Okendo API and MCP server

> Okendo has an official API, but with limits (checked 23 Oct 2026). The Merchant REST API reads and updates reviews, replies, loyalty customers and webhooks, and Okendo's spec calls it available to enterprise customers. The official MCP server only reads published reviews and questions.

Reviews, loyalty, referrals, surveys and quizzes for Shopify stores. Reviews are collected after an order, moderated in the Okendo admin and shown on the storefront.

## What is the Okendo API?

Cotlet's Okendo API exposes 11 endpoints for your own Okendo account: list reviews, get a review, suggest a review reply, list questions, get product performance, get sentiment report, get publishing settings, publish a review, reject a review, reply to a review and answer a question. The list_reviews endpoint returns reviews by moderation status, with rating, text, sentiment, verification and any reply. Each endpoint takes simple JSON inputs like review_id, status or limit and works both as an operation of the okendo_read or okendo_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Marketing & SEO](https://cotlet.dev/integrations/category/marketing-seo.md)
- **Endpoints:** 11 (7 read, 4 write)
- **Updated:** 2026-10-23

Okendo has an official API, but with limits (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Okendo with 11 endpoints (7 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Okendo have an official API?

Okendo has an official API, but with limits (checked 23 Oct 2026). The Merchant REST API reads and updates reviews, replies, loyalty customers and webhooks, and Okendo's spec calls it available to enterprise customers. The official MCP server only reads published reviews and questions.

| Task | Okendo official | Cotlet |
|---|---|---|
| List reviews by moderation status | Partly: Merchant API for enterprise customers; the MCP server sees published reviews only | Yes |
| Publish or reject a review | Partly: Merchant API has an Update a Review endpoint for enterprise customers | Yes |
| Reply to a review | Partly: Merchant API has a reply endpoint for enterprise customers | Yes |
| Draft a reply with Okendo AI | No | Yes |
| Read and answer shopper questions | Partly: MCP server lists published questions and answers; nothing answers one | Yes |
| Product performance numbers | Partly: MCP server gives totals and rating distribution for published reviews | Yes |
| Sentiment breakdown | Partly: MCP server returns sentiment for each published review, not a report | Yes |
| Read auto-publish rules | No | Yes |

Sources: [Okendo Help: Connect your Okendo MCP server to ChatGPT and Claude](https://support.okendo.io/en/articles/12672009-connect-your-okendo-mcp-server-to-chatgpt-and-claude), [Okendo Developers: Merchant API usage](https://docs.okendo.io/docs/merchant-rest-api/usage), [Okendo Developers: Merchant API specification](https://docs.okendo.io/docs/open-api/merchant-rest-api/okendo-enterprise-api), [Okendo pricing](https://okendo.io/pricing/)

## Quick reference

```text
Okendo has an official API, but with limits (checked 23 Oct 2026). The Merchant REST API reads and updates reviews, replies, loyalty customers and webhooks, and Okendo's spec calls it available to enterprise customers. The official MCP server only reads published reviews and questions.
Cotlet provides a hosted MCP server and REST API for Okendo: 11 tools (7 read, 4 write).
Access       Sign up at https://cotlet.dev/app/signup?app=okendo, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    okendo_read, okendo_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/okendo, each operation at its own route, e.g. POST /api/v1/okendo/reviews/{review_id}/replies
Auth         Authorization: Bearer <COTLET_API_KEY>. 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, suggest_review_reply, list_questions, get_product_performance, get_sentiment_report, get_publishing_settings, publish_review, reject_review, reply_to_review, answer_question
Confirm      publish_review, reject_review, reply_to_review, answer_question (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/okendo-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=okendo, requests Okendo in the Cotlet console and creates an API key there.
2. The user signs in to Okendo once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Okendo 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 Okendo 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 Okendo 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 Okendo 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 Okendo 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 Okendo's terms; Cotlet is not affiliated with Okendo.
```

## What can an AI agent do in Okendo?

Cotlet is best for Shopify store owners and support teams on Okendo who want their AI agent to moderate reviews, reply and answer questions without running or fixing a server.

- **[Moderate pending reviews](https://cotlet.dev/integrations/okendo-api-mcp-server/moderate-pending-reviews.md)** (runs: daily): "Go through the pending reviews in Okendo. Publish genuine product feedback, reject reviews that name a competitor or contain personal details, and leave the rest pending with a one-line reason." → `list_reviews`, `get_review`, `publish_review`, `reject_review`
- **[Reply to reviews without an answer](https://cotlet.dev/integrations/okendo-api-mcp-server/reply-to-reviews.md)** (runs: daily): "Find published Okendo reviews from the last 3 days with no reply. Draft a reply for each with Okendo AI, reply publicly to 4 and 5 stars, and reply privately by email to anything with an order problem." → `list_reviews`, `suggest_review_reply`, `reply_to_review`
- **[Answer product questions](https://cotlet.dev/integrations/okendo-api-mcp-server/answer-product-questions.md)** (runs: daily): "List the pending questions in Okendo. Answer the ones my product notes cover and publish them, and list the others for me." → `list_questions`, `answer_question`
- **Weekly review performance report** (runs: weekly): "Every Monday, give me last week's reviews received and published, average rating and sentiment split, and name the product with the lowest rating." → `get_product_performance`, `get_sentiment_report`
- **Mark reviews that need support follow-up** (runs: daily): "Find reviews from the last 2 days with 2 stars or fewer and add an internal note, visible to nobody outside the team, that says "Needs support follow-up"." → `list_reviews`, `get_review`, `reply_to_review`

## Can Okendo automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Okendo 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 moderate pending 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/okendo/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/okendo/reviews with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 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 Okendo.

### list_reviews

Reviews by moderation status, with rating, text, sentiment, verification and any reply. Access: read. REST: `GET /api/v1/okendo/reviews`. MCP: `okendo_read → list_reviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | pending, published or rejected. Default: pending. |
| `search` | string | no | A customer email address. |
| `limit` | integer | no | How many reviews to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists reviews as Reviews > Moderation shows them for the status you pick: pending, published or rejected. Each review has its product, the customer name and email, rating, title, text, photos and videos, sentiment (positive, negative, neutral or mixed), a profanity flag, whether the customer is a verified buyer or verified reviewer, and your reply if there is one. Pass next_cursor back as cursor for the next page. search matches a customer email address.

Example response:

```json
{
  "reviews": [
    {
      "review_id": "rev_4a91c7",
      "product": "Canvas Tote",
      "customer": "Lena Fischer",
      "email": "lena@example.com",
      "rating": 5,
      "title": "Love the fit, runs true",
      "sentiment": "positive",
      "profanity": false,
      "verification": "verified_buyer",
      "status": "pending",
      "reply": null
    },
    {
      "review_id": "rev_7d20e3",
      "product": "Canvas Tote",
      "customer": "Sam Okafor",
      "email": "sam@example.com",
      "rating": 2,
      "title": "Strap broke after a week",
      "sentiment": "negative",
      "profanity": false,
      "verification": "unverified",
      "status": "pending",
      "reply": null
    }
  ],
  "next_cursor": null
}
```

### get_review

One review in full, with every photo and its reply. Access: read. REST: `GET /api/v1/okendo/reviews/{review_id}`. MCP: `okendo_read → get_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | review_id from list_reviews. |

Opens the Details page of one review and returns the full text, every photo or video with its hidden or shown state, the product attributes, sentiment, the profanity flag, the verification mark and the reply with its visibility. Use it before publish_review or reject_review when the card preview is not enough.

Example response:

```json
{
  "review_id": "rev_7d20e3",
  "product": "Canvas Tote",
  "customer": "Sam Okafor",
  "rating": 2,
  "title": "Strap broke after a week",
  "text": "The strap tore at the seam after a week of normal use. The bag itself is nice.",
  "media": [
    {
      "type": "photo",
      "hidden": false
    }
  ],
  "sentiment": "negative",
  "profanity": false,
  "verification": "unverified",
  "status": "pending",
  "reply": null
}
```

### suggest_review_reply

A draft reply from Okendo AI for one review. Saves nothing. Access: read. REST: `GET /api/v1/okendo/reviews/{review_id}/reply/suggest`. MCP: `okendo_read → suggest_review_reply`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | review_id from list_reviews. |

Clicks Suggest AI Reply in the reply editor and returns the draft. Okendo writes it from the review, its language and your last 6 human-written replies for that sentiment. Calling it again is Regenerate: the new draft replaces the old one and there is no rollback. Nothing is saved or sent until reply_to_review is called.

Example response:

```json
{
  "review_id": "rev_7d20e3",
  "draft": "Thank you for telling us, Sam. We are sorry the strap broke. Please reply to this email with your order number and we will make it right."
}
```

### list_questions

Shopper questions by status, with product, asker and any answer. Access: read. REST: `GET /api/v1/okendo/questions`. MCP: `okendo_read → list_questions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | pending, published or rejected. Default: pending. |
| `product` | string | no | Only questions about this product. |
| `limit` | integer | no | How many questions to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists questions as Reviews > Questions > Moderation shows them for the status you pick. Each question has its product, who asked with name and email, the question text and your answer if there is one. Pass next_cursor back as cursor for the next page. Needs the Q&A widget on your store, or there are no questions to list.

Example response:

```json
{
  "questions": [
    {
      "question_id": "qst_31b8",
      "product": "Canvas Tote",
      "asked_by": "Priya Nair",
      "email": "priya@example.com",
      "question": "Is the tote machine washable?",
      "status": "pending",
      "answer": null
    }
  ],
  "next_cursor": null
}
```

### get_product_performance

Reviews received and published, average rating, questions and sentiment score, from Reviews > Performance. Access: read. REST: `GET /api/v1/okendo/product-performance`. MCP: `okendo_read → get_product_performance`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `range` | enum | no | Last 4 weeks, Last 30 days, Last 12 weeks, Last 90 days, Past year or All time. |
| `group_by` | enum | no | Day, Week, Month, Quarter or Year. The steps that fit depend on the range. |
| `product` | string | no | A product or product group. Default: all products. |

Reads the Products tab of Reviews > Performance. It returns reviews received (published and unpublished), reviews published with their share of those received, the average rating across both, questions received and the sentiment score, for all products or the ones you name, with a series for the group_by step. The agent can compare two periods by calling it twice.

Example response:

```json
{
  "range": "Last 4 weeks",
  "group_by": "Week",
  "reviews_received": 120,
  "reviews_published": 108,
  "published_share": "90%",
  "average_rating": 4.6,
  "questions_received": 14,
  "sentiment_score": 0.72,
  "series": [
    {
      "week": "Sep 28",
      "reviews_received": 31
    },
    {
      "week": "Oct 5",
      "reviews_received": 29
    },
    {
      "week": "Oct 12",
      "reviews_received": 34
    },
    {
      "week": "Oct 19",
      "reviews_received": 26
    }
  ]
}
```

### get_sentiment_report

How many reviews are positive, negative, mixed or neutral, from Reviews > Performance. Access: read. REST: `GET /api/v1/okendo/sentiment-report`. MCP: `okendo_read → get_sentiment_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `range` | enum | no | Last 4 weeks, Last 30 days, Last 12 weeks, Last 90 days, Past year or All time. |
| `group_by` | enum | no | Day, Week, Month, Quarter or Year. The steps that fit depend on the range. |

Reads the Sentiment tab of Reviews > Performance. It returns the number of reviews in each of positive, negative, mixed and neutral for the range you pick. Okendo takes sentiment from the language of each review, not from its stars.

Example response:

```json
{
  "range": "Last 4 weeks",
  "positive": 84,
  "negative": 12,
  "mixed": 6,
  "neutral": 18,
  "total": 120
}
```

### get_publishing_settings

Your auto-publish rules from Reviews > Settings > Publishing. Access: read. REST: `GET /api/v1/okendo/publishing-settings`. MCP: `okendo_read → get_publishing_settings`.

No parameters.

Returns whether auto-publish is on, the minimum star rating, which blocks are on (unverified reviews, media, profanity, negative sentiment) and the profanity filter options. Use it to tell why a review is still pending. Reads only; the settings are changed in Okendo.

Example response:

```json
{
  "auto_publish": true,
  "minimum_star_rating": 4,
  "block_unverified": true,
  "block_media": false,
  "block_profanity": true,
  "block_negative_sentiment": true,
  "censor_flagged_words": true
}
```

### publish_review

Publish a pending or rejected review so shoppers see it on your storefront. Access: write, asks the user first. REST: `POST /api/v1/okendo/reviews/{review_id}/publish`. MCP: `okendo_write → publish_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | review_id from list_reviews. |

Clicks Publish on the review's toolbar in Reviews > Moderation and returns the new status. The review appears on your storefront, so it reaches shoppers. Okendo does not let you edit review text, so the review goes up as the customer wrote it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "review_id": "rev_4a91c7",
  "status": "published"
}
```

### reject_review

Reject a review so it stays off your storefront. Access: write, asks the user first. REST: `POST /api/v1/okendo/reviews/{review_id}/reject`. MCP: `okendo_write → reject_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | review_id from list_reviews. |

Clicks Reject on the review's toolbar in Reviews > Moderation and returns the new status. Okendo has no delete: a rejected review stays in the Rejected list. The customer is not told, and cannot edit the review, so a customer who wants a change needs a new link to write another review. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "review_id": "rev_7d20e3",
  "status": "rejected"
}
```

### reply_to_review

Reply to a review publicly, by private email, or as an internal note. Access: write, asks the user first. REST: `POST /api/v1/okendo/reviews/{review_id}/replies`. MCP: `okendo_write → reply_to_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | review_id from list_reviews. |
| `body` | string | yes | The reply text. |
| `visible_to_shoppers` | boolean | no | Show the reply on your storefront. Default: false. |
| `email_reviewer` | boolean | no | Email a copy to the reviewer. Default: false. |

Saves a reply in the reply editor with its two checkboxes. visible_to_shoppers puts the reply on your storefront and in the admin. email_reviewer emails a copy to the customer, and alone it makes the reply private. With both off the reply stays in the admin as an internal note, marked with a padlock. The tool cannot edit or delete a reply. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "review_id": "rev_7d20e3",
  "reply_saved": true,
  "visible_to_shoppers": false,
  "email_reviewer": true
}
```

### answer_question

Answer a shopper question, publicly or privately by email. Access: write, asks the user first. REST: `POST /api/v1/okendo/questions/{question_id}/replies`. MCP: `okendo_write → answer_question`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `question_id` | string | yes | question_id from list_questions. |
| `answer` | string | yes | The answer text. |
| `visible_to_shoppers` | boolean | no | Publish the question and answer on your storefront. Default: false. |

Clicks Add Answer on a question in Reviews > Questions > Moderation and saves the answer. With visible_to_shoppers on, the question and answer are published on your storefront and the asker is emailed (Publish Question and Notify). With it off, nothing is public and the asker still gets the answer by email (Save and Notify). By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "question_id": "qst_31b8",
  "status": "published",
  "visible_to_shoppers": true,
  "asker_notified": true
}
```

## How do I connect Okendo to Claude Code, Codex or Cursor?

Connecting Okendo takes three steps: sign up, sign in to Okendo 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 Okendo to your agent.

1. **Create an account** Sign up and add Okendo in the console. Your API key is there too.

2. **Sign in to Okendo in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Okendo 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 Okendo 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.

```
Go through the pending reviews in Okendo. Publish genuine product feedback, reject reviews that name a competitor or contain personal details, and leave the rest pending with a one-line reason.
```

### Call Okendo 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/okendo 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/okendo/reviews/rev_4a91c7/replies \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Thank you, Lena! Glad the tote fits so well. Tip: it runs true to size in the larger bag too.","visible_to_shoppers":true,"email_reviewer":true}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "review_id": "rev_4a91c7",
  "reply_saved": true,
  "visible_to_shoppers": true,
  "email_reviewer": true
}
```

## Why use Cotlet for Okendo?

**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 Okendo 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 Okendo changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Okendo to Cotlet?

Yes. You sign in to Okendo yourself, in your own Cloud Browser, and we never save your password. Your agents only get Okendo 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 Okendo integration?**

No, Cotlet is independent of Okendo. Okendo's own API is too limited for this work. Cotlet works through your own Okendo account, the way you use Okendo 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 Okendo in your console: your agents lose access at once and you stay signed in. Signing out of Okendo in the browser works too, and Reset browser deletes the whole profile.

## Is there a Okendo MCP server on GitHub?

Yes, for enterprise customers. The Merchant API is a REST API with an API key. You write and host the code that calls it, keep it on Okendo's dated API version, and it lists no endpoints for questions, reports or publishing settings. Cotlet hosts the tools for you and works in the admin screens.

|  | Merchant API | Cotlet |
|---|---|---|
| Setup | Copy your User ID and API key from the integration settings, then write and host the calls | Sign up, sign in to Okendo once, add one MCP server or API key |
| Plan | Okendo calls it available to enterprise customers; its pricing lists API access as an add-on at some tiers | Your own Okendo admin, on the plan you have |
| Coverage | Reviews, replies, loyalty customers and webhooks; no questions, reports or publishing settings in the docs | Reviews, replies, questions, Performance reports and publishing settings, as the admin shows them |
| When Okendo changes | You move your code to each new okendo-api-version | Our team tests the tools daily and fixes them for you; failed calls are free |
| Your credentials | An API key in your code, used as an HTTP Basic Auth password | Your session in your own Cloud Browser in the EU, profile encrypted, only for the apps you enable |
| Where it runs | Your server; the API allows 2 requests per second with a small burst | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Set by your Okendo plan, plus your time to build and run it | 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 Okendo 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 Okendo API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Okendo 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 Okendo 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 Okendo 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 Okendo only after you enable it. When Okendo 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 Okendo, sign out of Okendo 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.
- **Okendo's terms:** You use your own Okendo account and stay responsible for following Okendo's terms. Cotlet is independent and not affiliated with Okendo. [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 Okendo in the console and press Request access. Then you create your API key and connect Okendo there.

**Do I need to be technical?**

No. You sign in to Okendo 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 Okendo to Cotlet?**

Yes. You sign in to Okendo yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Okendo 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 Okendo 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 Okendo 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 Okendo's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Okendo 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 Okendo 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?**

Okendo 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).

**Does Okendo's own MCP server moderate or reply to reviews?**

No. Okendo's MCP server needs the Reviews Growth plan and admin access, and it has three tools: reviews_aggregate, reviews_search and questions_list. It only surfaces published, storefront-visible reviews and questions, so it cannot see pending reviews or approve, reject, reply or answer. Cotlet works in the admin, where pending reviews and the buttons are.

**Which Okendo plan do I need?**

Cotlet works in your own admin, so it can do what your plan shows there. Auto Review Replies need the Growth plan and above, Q&A needs the Q&A widget on your store, and Okendo describes the Merchant API as available to enterprise customers. Cotlet uses none of those, and an agent working in your admin needs the access you have.

**Do I sign in to Okendo or to Shopify?**

Both, once. Okendo's login page sends existing users to the Okendo app on their Shopify store's Apps page, so you sign in to Shopify in your Cloud Browser and open Okendo from there. You complete any Shopify verification yourself; Cotlet keeps only the session.

**Can my agent post or send messages in Okendo without asking me?**

No. Every call to publish_review, reject_review, reply_to_review or answer_question waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Okendo 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/okendo 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.