# Momence API and MCP server

> Momence has a Developer API with OAuth 2.0 that reads members, classes and bookings, books free spots, checks in, cancels bookings and freezes memberships, but it has no endpoint to create or cancel classes, message customers, cancel renewals or refund payments (checked 11 Oct 2026). Its tokens expire a few hours after they are issued.

Booking, payments and marketing software for fitness, yoga and wellness studios: classes, appointments, memberships and a customer inbox.

## What is the Momence API?

Cotlet's Momence API exposes 14 endpoints for your own Momence account: list classes, get class roster, search customers, get customer, list customer payments, create class, cancel class, book customer, cancel booking, check in customer, freeze membership, cancel membership renewal, send message and refund payment. The list_classes endpoint returns scheduled classes in a date range, with teacher, location, bookings and status. Each endpoint takes simple JSON inputs like class_id, customer_id or teacher and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas)
- **Endpoints:** 14 (5 read, 9 write)
- **Updated:** 2026-10-11

Momence has a Developer API with OAuth 2.0 that reads members, classes and bookings, books free spots, checks in, cancels bookings and freezes memberships, but it has no endpoint to create or cancel classes, message customers, cancel renewals or refund payments (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Momence with 14 endpoints (5 read, 9 write): your AI agent signs in as you and does the work.

## Does Momence have an official API?

Momence has a Developer API with OAuth 2.0 that reads members, classes and bookings, books free spots, checks in, cancels bookings and freezes memberships, but it has no endpoint to create or cancel classes, message customers, cancel renewals or refund payments (checked 11 Oct 2026). Its tokens expire a few hours after they are issued.

| Task | Momence official | Cotlet |
|---|---|---|
| List classes and who is booked | Yes: List sessions and List session bookings | Yes |
| Create classes and recurring series | No | Yes |
| Cancel a class | No: Only single bookings can be cancelled | Yes |
| Book a customer into a class | Partly: Add to a session for free, or to its waitlist | Yes |
| Check customers in | Yes: Mark a booking checked in or not | Yes |
| Freeze or unfreeze a membership | Yes: Immediately or scheduled | Yes |
| Message customers by email, SMS or in-app | No | Yes |
| Refund a payment | No | Yes |

Sources: [Momence API reference](https://api.docs.momence.com/reference), [Momence API: authentication](https://api.docs.momence.com/docs/getting-started), [Momence Help: Editing, cancelling, deleting classes](https://help.momence.com/en/articles/12027563-editing-cancelling-deleting-faq-s-classes), [Momence Help: Renewal, freeze and failure (subscriptions)](https://help.momence.com/en/articles/12030267-renewal-freeze-failure-faq-s-subscriptions)

## For AI agents

```text
Momence has a Developer API with OAuth 2.0 that reads members, classes and bookings, books free spots, checks in, cancels bookings and freezes memberships, but it has no endpoint to create or cancel classes, message customers, cancel renewals or refund payments (checked 11 Oct 2026). Its tokens expire a few hours after they are issued.
Cotlet provides a hosted MCP server and REST API for Momence: 14 tools (5 read, 9 write).
Access       Request access at https://cotlet.dev/app/signup?app=momence; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/momence
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_classes, get_class_roster, search_customers, get_customer, list_customer_payments, create_class, cancel_class, book_customer, cancel_booking, check_in_customer, freeze_membership, cancel_membership_renewal, send_message, refund_payment
Confirm      cancel_class, book_customer, cancel_booking, freeze_membership, cancel_membership_renewal, send_message, refund_payment (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/momence-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=momence (Momence is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Momence once in a browser. 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 Momence 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.
Session: the user signs in to Momence in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Momence's terms; Cotlet is not affiliated with Momence.
```

## What can an AI agent do in Momence?

Cotlet is best for studio owners and managers who run classes and memberships in Momence and want an AI agent to handle schedules, check-ins, freezes, messages and refunds without running or fixing a server.

- **Check in everyone who showed up** (runs: daily): "Who is booked into tonight's 6pm class? Check in everyone on the list who is here." → `list_classes`, `get_class_roster`, `check_in_customer`
- **[Cancel a class and notify students](https://cotlet.dev/integrations/momence-api-mcp-server/cancel-class-notify-students)**: "Maya is sick. Cancel Saturday's 7am Sunrise Flow, refund anyone who paid a drop-in by card, and text everyone who was booked or waitlisted that the 9am still has spots. Show me the list before you refund or send anything." → `list_classes`, `get_class_roster`, `cancel_class`, `list_customer_payments`, `refund_payment`, `send_message`
- **[Create recurring classes for a new term](https://cotlet.dev/integrations/momence-api-mcp-server/create-recurring-classes)**: "Here is our winter timetable. Create each class as a weekly series in Momence from 5 January to 29 March, as drafts, and tell me about any line you could not match to a template or teacher." → `list_classes`, `create_class`
- **[Freeze a membership while a member travels](https://cotlet.dev/integrations/momence-api-mcp-server/freeze-membership)**: "Jordan Pike emailed that they are traveling from 1 to 30 November. Freeze their membership for those dates and tell me which of their booked classes it cancels." → `search_customers`, `get_customer`, `freeze_membership`, `cancel_membership_renewal`
- **Refund a drop-in as credits**: "Refund last week's drop-in for client@example.com as Momence credits." → `search_customers`, `list_customer_payments`, `refund_payment`

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

Yes. Cotlet does not replace your automation platform: it gives it a Momence 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 check in everyone who showed up, 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 to https://cotlet.dev/api/v1/momence/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/momence/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/momence/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/momence/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Momence.

### list_classes

Scheduled classes in a date range, with teacher, location, bookings and status. Access: read. REST: `POST /api/v1/momence/list_classes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | no | First day. Default: today. |
| `to` | date | no | Last day. Default: 7 days from today. |
| `teacher` | string | no | Only classes taught by this teacher. |
| `include_cancelled` | boolean | no | Also return cancelled classes. Default: false. |

Returns classes between two dates in start order, with teacher, location, booked count and whether the class is cancelled. Cancelled classes are hidden unless include_cancelled is true. Use class_id from each item in get_class_roster and the write tools.

Example response:

```json
{
  "classes": [
    {
      "class_id": "9182736",
      "name": "Vinyasa Flow 60",
      "starts_at": "2026-10-15T19:00:00-07:00",
      "teacher": "Maya Lee",
      "location": "Studio A",
      "booked": 14,
      "capacity": 18,
      "status": "scheduled"
    }
  ]
}
```

### get_class_roster

Customers booked into a class and on its waitlist, with check-in status. Access: read. REST: `POST /api/v1/momence/get_class_roster`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `class_id` | string | yes | Class (session) ID from list_classes. |

Returns booked customers and the waitlist for one class. Each booking has a booking_id for check_in_customer and cancel_booking, and its check-in status. Waitlisted customers have no booking_id.

Example response:

```json
{
  "class_id": "9182736",
  "bookings": [
    {
      "booking_id": "bk_204118",
      "customer_id": "cu_5521",
      "name": "Sam Rivera",
      "checked_in": false
    },
    {
      "booking_id": "bk_204119",
      "customer_id": "cu_5530",
      "name": "Jordan Pike",
      "checked_in": true
    }
  ],
  "waitlist": [
    {
      "customer_id": "cu_5544",
      "name": "Alex Moreau"
    }
  ]
}
```

### search_customers

Find customers by name, email or phone, optionally by tag. Access: read. REST: `POST /api/v1/momence/search_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name, email or phone. |
| `tag` | string | no | Only customers with this tag. |
| `limit` | integer | no | 1 to 100. Default: 25. |

Returns matching customers with ID, name, email and tags. Use customer_id in get_customer, book_customer and list_customer_payments. Tags are the ones you set in Momence.

Example response:

```json
{
  "customers": [
    {
      "customer_id": "cu_5530",
      "name": "Jordan Pike",
      "email": "jordan@example.com",
      "tags": [
        "teacher-training"
      ]
    }
  ]
}
```

### get_customer

Profile, tags, notes, active subscriptions and packs, and upcoming bookings. Access: read. REST: `POST /api/v1/momence/get_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | yes | Customer ID from search_customers. |

Returns one customer profile with notes, active subscriptions and packs, and upcoming bookings. Subscription IDs from here go into freeze_membership and cancel_membership_renewal.

Example response:

```json
{
  "customer_id": "cu_5530",
  "name": "Jordan Pike",
  "email": "jordan@example.com",
  "tags": [
    "teacher-training"
  ],
  "notes": [
    "Prefers the back row."
  ],
  "memberships": [
    {
      "membership_id": "sub_77120",
      "name": "Unlimited Monthly",
      "status": "active",
      "renews_on": "2026-11-05"
    }
  ],
  "upcoming_bookings": [
    {
      "booking_id": "bk_204119",
      "class_id": "9182736",
      "starts_at": "2026-10-15T19:00:00-07:00"
    }
  ]
}
```

### list_customer_payments

Payments from the customer profile (Activity > Payments), newest first. Access: read. REST: `POST /api/v1/momence/list_customer_payments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | yes | Customer ID from search_customers. |
| `since` | date | no | Only payments on or after this date. |

Returns the payments listed under Activity > Payments on the customer profile, newest first. Use payment_id in refund_payment.

Example response:

```json
{
  "payments": [
    {
      "payment_id": "pay_330917",
      "date": "2026-10-04",
      "description": "Drop-in: Vinyasa Flow 60",
      "amount": 25,
      "currency": "USD",
      "refunded": false
    }
  ]
}
```

### create_class

One-off class or recurring series from a class template, like Classes > Schedule > New Class. Access: write. REST: `POST /api/v1/momence/create_class`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `template` | string | yes | Class template name; holds the class name and description. |
| `teacher` | string | yes | Teacher name. |
| `location` | string | yes | Location name, in person or online. |
| `starts_at` | datetime | yes | First class, ISO 8601 with time zone. |
| `duration_minutes` | integer | yes | Length of each class. |
| `repeat_every_days` | integer | no | Days between classes for a recurring series, e.g. 7. Omit for a one-off class. |
| `end_date` | date | no | Last date of the series. Without it the series keeps scheduling itself. |
| `as_draft` | boolean | no | Save unpublished, hidden from customers. Default: false. |

Creates one class, or a series when repeat_every_days is set, from an existing class template. Returns the new class IDs and the first dates. With as_draft the classes stay hidden from customers. It reaches no one until published and is undone with cancel_class, so it runs without asking.

Example response:

```json
{
  "series_id": "ser_48213",
  "classes_created": 12,
  "first_class_id": "9182736",
  "status": "published",
  "next_classes": [
    "2026-10-15T19:00:00-07:00",
    "2026-10-22T19:00:00-07:00"
  ]
}
```

### cancel_class

Cancel one class. It stays on the customer schedule marked as cancelled. Access: write, asks the user first. REST: `POST /api/v1/momence/cancel_class`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `class_id` | string | yes | Class (session) ID from list_classes. |
| `note` | string | no | Optional note added to the cancellation email. |

Cancels one class. It stays on the schedule marked as cancelled, and Momence emails every registered customer its cancellation template, with your optional note in it. Returns how many customers were notified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "class_id": "9182736",
  "status": "cancelled",
  "customers_notified": 14
}
```

### book_customer

Book a customer into a class, or add them to its waitlist. Access: write, asks the user first. REST: `POST /api/v1/momence/book_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `class_id` | string | yes | Class (session) ID from list_classes. |
| `customer_id` | string | yes | Customer ID from search_customers. |
| `waitlist` | boolean | no | Add to the waitlist instead of booking. Default: false. |

Adds a customer to a class, or to its waitlist when waitlist is true. Returns the booking_id, or the waitlist position. The customer gets Momence's usual booking notice. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "class_id": "9182736",
  "customer_id": "cu_5544",
  "status": "booked",
  "booking_id": "bk_204130"
}
```

### cancel_booking

Cancel a customer's booking in a class, with credit and notification choices. Access: write, asks the user first. REST: `POST /api/v1/momence/cancel_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | string | yes | Booking ID from get_class_roster. |
| `credit_customer` | boolean | no | Return the class credit to the customer. |
| `notify_customer` | boolean | no | Send the customer a cancellation notice. |
| `late_cancel` | boolean | no | Mark it as a late cancellation. |

Cancels one customer's booking, the same as Cancel booking next to the customer in the class. You choose whether to credit the customer, whether to notify them and whether it counts as a late cancellation. Late-cancellation charges follow your Cancellation Policy setting. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_id": "bk_204118",
  "status": "cancelled",
  "credited": true,
  "notified": true,
  "late_cancel": false
}
```

### check_in_customer

Mark a booking as checked in, or undo the check-in. Access: write. REST: `POST /api/v1/momence/check_in_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | string | yes | Booking ID from get_class_roster. |
| `checked_in` | boolean | no | false undoes the check-in. Default: true. |

Marks one booking as checked in, or not checked in when checked_in is false. It reaches no one and is undone in one call, so it runs without asking.

Example response:

```json
{
  "booking_id": "bk_204118",
  "checked_in": true
}
```

### freeze_membership

Freeze a customer's subscription now or on a date, with an optional unfreeze date. Access: write, asks the user first. REST: `POST /api/v1/momence/freeze_membership`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `membership_id` | string | yes | Membership (subscription) ID from get_customer. |
| `freeze_from` | date | no | Start of the freeze. Default: now. |
| `unfreeze_on` | date | no | Scheduled unfreeze date. |

Freezes a subscription now or from a date, and unfreezes it on unfreeze_on if set. Momence cancels all the customer's future bookings made with that subscription. The renewal date moves forward by the frozen days unless Preserve Payment Schedule is on. Needs a staff account allowed to freeze. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "membership_id": "sub_77120",
  "status": "freeze_scheduled",
  "freeze_from": "2026-11-01",
  "unfreeze_on": "2026-11-30",
  "future_bookings_cancelled": 2
}
```

### cancel_membership_renewal

Cancel Renewal on a subscription now or at a scheduled date, so it expires instead of charging again. Access: write, asks the user first. REST: `POST /api/v1/momence/cancel_membership_renewal`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `membership_id` | string | yes | Membership (subscription) ID from get_customer. |
| `cancel_at` | datetime | no | Scheduled cancellation. Default: now. |

Stops a subscription from renewing now or at cancel_at. Some memberships need a minimum number of renewals first, and cancelling a main membership also cancels the renewals of its linked membership. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "membership_id": "sub_77120",
  "status": "renewal_cancelled",
  "cancels_at": "2026-11-05T00:00:00-08:00"
}
```

### send_message

Message customers from the Momence Inbox by email, SMS or in-app message. Access: write, asks the user first. REST: `POST /api/v1/momence/send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_ids` | string[] | yes | Customer IDs from search_customers or get_class_roster. |
| `channel` | enum | yes | email, sms or in_app. |
| `body` | string | yes | Message text. |
| `subject` | string | no | Email subject. Email only. |

Sends one message from Home > Inbox to one or more customers by email, SMS or in-app. A message to several customers does not reach those who unsubscribed; a one-to-one message does. Sending to 75 or more email recipients needs the Marketing Suite, and SMS is billed in segments. In-app messages show only if the customer enabled notifications. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "channel": "sms",
  "recipients": 14,
  "delivered_to_provider": 14,
  "skipped_unsubscribed": 0
}
```

### refund_payment

Refund a payment as money or as Momence credits; the original purchase stays on record. Access: write, asks the user first. REST: `POST /api/v1/momence/refund_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `payment_id` | string | yes | Payment ID from list_customer_payments. |
| `refund_to` | enum | yes | money or credits. |

Refunds one payment from the customer profile, as money back to the card or as Momence credits. The original purchase stays on record with a separate refund entry. Needs a staff account allowed to refund. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "payment_id": "pay_330917",
  "refunded_to": "credits",
  "amount": 25,
  "currency": "USD",
  "status": "refunded"
}
```

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

Connecting Momence takes three steps: request access, sign in to Momence once, then add one MCP server or call the REST API with the same key.

### Connect Momence to your agent.

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

2. **Sign in to Momence once** Open the connect page from the console and sign in to Momence the way you always do. We keep the session, never your password, and you can revoke it anytime.

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 Momence 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.

```
Who is booked into tonight's 6pm class? Check in everyone on the list who is here.
```

### Call Momence 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 a POST endpoint at /api/v1/momence/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/momence/create_class \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"template":"Vinyasa Flow 60","teacher":"Maya Lee","location":"Studio A","starts_at":"2026-10-15T19:00:00-07:00","duration_minutes":60,"repeat_every_days":7,"end_date":"2026-12-31"}'
```

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

```
{
  "series_id": "ser_48213",
  "classes_created": 12,
  "first_class_id": "9182736",
  "status": "published",
  "next_classes": [
    "2026-10-15T19:00:00-07:00",
    "2026-10-22T19:00:00-07:00"
  ]
}
```

## Why use Cotlet for Momence?

**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 Momence yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Momence changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Momence MCP server on GitHub?

No open-source Momence MCP server turned up. The realistic option is the Developer API in your own script, or hosted wrappers around it, which have the same endpoint limits. Cotlet works in the dashboard instead, so it also creates and cancels classes, cancels renewals, sends messages and refunds.

|  | Developer API | Cotlet |
|---|---|---|
| Setup | Create an OAuth client; staff-account automation uses the password flow | Request access, sign in to Momence once, add one MCP server or API key |
| What you can do | Members, bookings, check-ins and freezes; no class creation or cancellation, messages or refunds | Also classes, renewals, messages and refunds, each send or refund confirmed by you |
| When the session expires | Access tokens expire a few hours after creation; your code refreshes them | We keep the session alive; if Momence logs you out, your agent gets a link to sign in again |
| When Momence changes | You update your own code | Our team tests it daily and fixes it for you; failed calls are free |
| Your Momence session | Client secret and tokens kept in your own code and config | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| Where it runs | Your server or scripts | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free with your Momence account, paid for with your time | Free 7-day trial with 5,000 credits, then credits per call |

### 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 Momence 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 the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Momence API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Momence API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Momence account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Momence yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Momence tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Momence in your dashboard: the session is deleted and access ends at once. 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.
- **Momence's terms:** You use your own Momence account and stay responsible for following Momence's terms. Cotlet is independent and not affiliated with Momence. [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?**

Request access and pick Momence. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Momence once in your browser 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 a hosted server safe? My Momence session would leave my computer.**

Cotlet keeps your Momence session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Can the agent cancel a class and tell everyone who booked?**

Yes. cancel_class cancels the class, and Momence emails every registered customer its cancellation template with your optional note (Momence Help, checked 11 Oct 2026). send_message adds a personal text or in-app message on top.

**What staff permissions does it need?**

It acts as the staff account you sign in with, so it can only do what that account may do. Freezing needs a staff account with permission to freeze (Momence Help, checked 11 Oct 2026).

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

No. Every call to cancel_class, book_customer, cancel_booking, freeze_membership, cancel_membership_renewal, send_message or refund_payment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_class, check_in_customer runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Momence API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/momence/{tool} from the HTTP Request node.