# Rent Manager API and MCP server

> Rent Manager has an API that reads and writes your database, but it is not self-serve (checked 11 Oct 2026). Its public pages offer no key signup: access goes through the Integrations Partner Program or an API support request, and a developer then builds the connector.

Property management software for residential, commercial and HOA portfolios: tenants, accounting, service issues and tenant texting, in a Windows program and the browser-based Rent Manager Express.

## What is the Rent Manager API?

Cotlet's Rent Manager API exposes 12 endpoints for your own Rent Manager account: list properties, list tenants, get tenant, get tenant ledger, list charge types, list service issues, get history, create service issue, update service issue, add history note, post charge and send text. The list_properties endpoint returns properties in your Rent Manager database, with address and unit count. Each endpoint takes simple JSON inputs like tenant_id, cursor or property_id and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Real estate](https://cotlet.dev/integrations/category/real-estate)
- **Endpoints:** 12 (7 read, 5 write)
- **Updated:** 2026-10-11

Rent Manager has an API that reads and writes your database, but it is not self-serve (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Rent Manager with 12 endpoints (7 read, 5 write): your AI agent signs in as you and does the work.

## Does Rent Manager have an official API?

Rent Manager has an API that reads and writes your database, but it is not self-serve (checked 11 Oct 2026). Its public pages offer no key signup: access goes through the Integrations Partner Program or an API support request, and a developer then builds the connector.

| Task | Rent Manager official | Cotlet |
|---|---|---|
| List tenants and balances | Partly: The API reads your database, after Rent Manager arranges access | Yes |
| Read a tenant ledger | Partly: The API reads your database, after Rent Manager arranges access | Yes |
| Post a one-off charge | Partly: The API can write data, after Rent Manager arranges access | Yes |
| Create and update service issues | Partly: The API can write data, after Rent Manager arranges access | Yes |
| Add a History/Notes entry to a tenant | Partly: The API can write data, after Rent Manager arranges access | Yes |
| Text a tenant | Partly: Texting is a Rent Manager feature; API coverage is not published | Yes |

Sources: [Rent Manager: software customization (API and Open Access)](https://www.rentmanager.com/software-customization/), [Rent Manager: become an integrations partner](https://www.rentmanager.com/become-or-refer-a-partner/), [Rent Manager: maintenance and service issues](https://www.rentmanager.com/maintenance/), [Rent Manager Express: browser-based program](https://www.rentmanager.com/rent-manager-express-delivers-more-accessibility-and-flexibility/), [Rent Manager: automate your operation (Task Automation, AR Automation)](https://www.rentmanager.com/automate-your-operation-with-these-tools/)

## For AI agents

```text
Rent Manager has an API that reads and writes your database, but it is not self-serve (checked 11 Oct 2026). Its public pages offer no key signup: access goes through the Integrations Partner Program or an API support request, and a developer then builds the connector.
Cotlet provides a hosted MCP server and REST API for Rent Manager: 12 tools (7 read, 5 write).
Access       Request access at https://cotlet.dev/app/signup?app=rent-manager; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/rent-manager
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_properties, list_tenants, get_tenant, get_tenant_ledger, list_charge_types, list_service_issues, get_history, create_service_issue, update_service_issue, add_history_note, post_charge, send_text
Confirm      create_service_issue, update_service_issue, post_charge, send_text (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/rent-manager-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=rent-manager (Rent Manager is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Rent Manager 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 Rent Manager server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Rent Manager MCP server instead.

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 Rent Manager 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 Rent Manager's terms; Cotlet is not affiliated with Rent Manager.
```

## What can an AI agent do in Rent Manager?

Cotlet is best for property managers who want their AI agent to post charges, text tenants and track service issues in Rent Manager without running or fixing a server.

- **[Text past-due tenants a personal rent reminder](https://cotlet.dev/integrations/rent-manager-api-mcp-server/text-tenants-rent-reminder)** (runs: weekly): "Find Maple Court tenants who owe more than $500, check their ledger and History/Notes, and text a personal reminder to the ones who have not promised a payment date. Log each text." → `list_tenants`, `get_tenant_ledger`, `get_history`, `send_text`, `add_history_note`
- **Post late fees to tenant ledgers**: "Post a $50 late fee to every tenant who has not paid October rent by the 5th." → `list_tenants`, `list_charge_types`, `post_charge`
- **[Create service issues from tenant texts and emails](https://cotlet.dev/integrations/rent-manager-api-mcp-server/create-service-issues-from-requests)** (runs: daily): "The tenant in 12A at Maple Court texted that the kitchen sink leaks under the cabinet. Check for an open issue on that unit, open a service issue for plumbing and text her that it is logged." → `list_tenants`, `list_service_issues`, `create_service_issue`, `update_service_issue`, `send_text`
- **[Follow up on overdue service issues](https://cotlet.dev/integrations/rent-manager-api-mcp-server/follow-up-overdue-service-issues)** (runs: weekly): "Find service issues at all properties open for more than 7 days. Assign the unassigned ones by trade, ask the technician for an update on the stuck ones and text tenants who have waited over two weeks." → `list_service_issues`, `get_history`, `update_service_issue`, `send_text`
- **Review a tenant ledger and log a payment plan**: "Show me Jordan Lee's ledger for the last 3 months and add a note about the payment plan." → `list_tenants`, `get_tenant_ledger`, `add_history_note`

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

Yes. Cotlet does not replace your automation platform: it gives it a Rent Manager 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 text past-due tenants a personal rent reminder, 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/rent-manager/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/rent-manager/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/rent-manager/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/rent-manager/{tool} with your API key. | cron or GitHub Actions. |

## Tools

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

### list_properties

Properties in your Rent Manager database, with address and unit count. Access: read. REST: `POST /api/v1/rent-manager/list_properties`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Name or address contains. |
| `limit` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the properties your user can see, with address and number of units. Use the property_id of each item in list_tenants, list_service_issues and create_service_issue. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "properties": [
    {
      "property_id": "p_12",
      "name": "Maple Court",
      "address": "12 Maple St, Dayton, OH",
      "units": 24
    },
    {
      "property_id": "p_15",
      "name": "Elm Street Duplexes",
      "address": "8 Elm St, Dayton, OH",
      "units": 2
    }
  ],
  "next_cursor": null
}
```

### list_tenants

Tenants with property, unit, status, contact details and current balance. Access: read. REST: `POST /api/v1/rent-manager/list_tenants`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | no | Only tenants of this property. |
| `status` | enum | no | current, past, future or all. Default: current. |
| `min_balance` | integer | no | Only tenants owing at least this amount, whole dollars. |
| `search` | string | no | Name, unit or email contains. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns tenants with property, unit, status, email, phone and current balance. Current tenants only by default; set status to widen it. min_balance keeps only tenants who owe at least that many whole dollars. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "tenants": [
    {
      "tenant_id": "10482",
      "name": "Jordan Lee",
      "property": "Maple Court",
      "unit": "4B",
      "status": "current",
      "email": "jordan.lee@example.com",
      "phone": "+1 555 010 0142",
      "balance": "1250.00"
    },
    {
      "tenant_id": "10517",
      "name": "Priya Shah",
      "property": "Maple Court",
      "unit": "12A",
      "status": "current",
      "email": "priya.shah@example.com",
      "phone": "+1 555 010 0177",
      "balance": "0.00"
    }
  ],
  "next_cursor": null
}
```

### get_tenant

One tenant: contacts, lease dates, rent and balance. Access: read. REST: `POST /api/v1/rent-manager/get_tenant`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `tenant_id` | string | yes | Tenant ID from list_tenants. |

Returns one tenant with contacts, lease start and end, monthly rent and current balance. Use it before a call or a text to see the whole picture for one unit.

Example response:

```json
{
  "tenant_id": "10482",
  "name": "Jordan Lee",
  "property": "Maple Court",
  "unit": "4B",
  "status": "current",
  "lease_start": "2026-02-01",
  "lease_end": "2027-01-31",
  "monthly_rent": "1200.00",
  "balance": "1250.00"
}
```

### get_tenant_ledger

Charges, payments and credits on a tenant account, with running balance. Access: read. REST: `POST /api/v1/rent-manager/get_tenant_ledger`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `tenant_id` | string | yes | Tenant ID from list_tenants. |
| `from` | date | no | Start date. Default: 90 days ago. |
| `to` | date | no | End date. Default: today. |

Returns the ledger of one tenant account, oldest first, with a running balance after each line. Opening balance is the balance before the first line of the period. The period defaults to the last 90 days.

Example response:

```json
{
  "tenant_id": "10482",
  "from": "2026-08-01",
  "to": "2026-10-11",
  "opening_balance": "0.00",
  "lines": [
    {
      "date": "2026-08-01",
      "type": "Rent",
      "amount": "1200.00",
      "balance": "1200.00"
    },
    {
      "date": "2026-08-03",
      "type": "Payment",
      "amount": "-1200.00",
      "balance": "0.00"
    },
    {
      "date": "2026-09-01",
      "type": "Rent",
      "amount": "1200.00",
      "balance": "1200.00"
    },
    {
      "date": "2026-09-04",
      "type": "Payment",
      "amount": "-1200.00",
      "balance": "0.00"
    },
    {
      "date": "2026-10-01",
      "type": "Rent",
      "amount": "1200.00",
      "balance": "1200.00"
    },
    {
      "date": "2026-10-06",
      "type": "Late Fee",
      "amount": "50.00",
      "balance": "1250.00"
    }
  ],
  "closing_balance": "1250.00"
}
```

### list_charge_types

Charge types set up in your database, such as rent or late fee. Access: read. REST: `POST /api/v1/rent-manager/list_charge_types`.

No parameters.

Returns the charge types defined in your Rent Manager database. The names are yours, so read this list before post_charge and use one of its names in charge_type.

Example response:

```json
{
  "charge_types": [
    {
      "name": "Rent"
    },
    {
      "name": "Late Fee"
    },
    {
      "name": "Lockout Fee"
    }
  ]
}
```

### list_service_issues

Service issues with status, property, unit, assignee and dates. Access: read. REST: `POST /api/v1/rent-manager/list_service_issues`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | Status name as set in your database, e.g. New, Work in Progress or Resolved. Default: all except Resolved. |
| `property_id` | string | no | Only issues at this property. |
| `older_than_days` | integer | no | Only issues created at least this many days ago. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns service issues, oldest first, with status, property, unit, assignee and creation date. Every status except Resolved by default, so a plain call is the open list. Status names are the ones set in your database. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "issues": [
    {
      "issue_id": "si_20744",
      "title": "Water heater not heating",
      "property": "Elm Street Duplexes",
      "unit": "8 Elm St",
      "status": "Work in Progress",
      "assigned_to": "Sam Ortiz",
      "created_at": "2026-09-28T09:12:00-04:00"
    },
    {
      "issue_id": "si_20801",
      "title": "Hallway light out",
      "property": "Maple Court",
      "unit": "Common area",
      "status": "New",
      "assigned_to": null,
      "created_at": "2026-10-02T15:40:00-04:00"
    }
  ],
  "next_cursor": null
}
```

### get_history

History/Notes of a tenant, newest first. Access: read. REST: `POST /api/v1/rent-manager/get_history`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `tenant_id` | string | yes | Tenant ID from list_tenants. |
| `limit` | integer | no | 1 to 100. Default: 25. |

Returns the History/Notes entries of one tenant, newest first, each with date, author and text. Use it to read what was agreed before you write to the tenant.

Example response:

```json
{
  "tenant_id": "10482",
  "entries": [
    {
      "date": "2026-10-08",
      "author": "Dana Ruiz",
      "note": "Called about the late October rent. Tenant will pay on Friday."
    },
    {
      "date": "2026-09-12",
      "author": "Dana Ruiz",
      "note": "Renewed lease through January 2027."
    }
  ]
}
```

### create_service_issue

Open a service issue for a unit, optionally assigned and scheduled. Access: write, asks the user first. REST: `POST /api/v1/rent-manager/create_service_issue`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property ID from list_properties. |
| `unit` | string | no | Unit name or number. |
| `tenant_id` | string | no | Tenant who reported it. |
| `title` | string | yes | Short description, e.g. "Kitchen sink leak". |
| `details` | string | no | Longer description for the technician. |
| `assigned_to` | string | no | Rent Manager user name to assign. |
| `scheduled_for` | datetime | no | ISO 8601 with time zone. |

Opens a service issue for a property and unit, with the status New. Give tenant_id to tie it to the tenant who reported it and assigned_to to give it to a Rent Manager user. Rent Manager can notify the assignee and the tenant by its own rules, which is why this reaches other people. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "issue_id": "si_20931",
  "status": "New",
  "property": "Maple Court",
  "unit": "12A",
  "tenant_id": "10517",
  "title": "Kitchen sink leak",
  "assigned_to": "Dana Ruiz",
  "created_at": "2026-10-12T08:30:00-04:00"
}
```

### update_service_issue

Change the status, assignee or schedule of a service issue, or add a note. Access: write, asks the user first. REST: `POST /api/v1/rent-manager/update_service_issue`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `issue_id` | string | yes | Service issue ID from list_service_issues. |
| `status` | string | no | Status name as set in your database, e.g. New, Work in Progress or Resolved. |
| `assigned_to` | string | no | Rent Manager user name. |
| `scheduled_for` | datetime | no | ISO 8601 with time zone. |
| `note` | string | no | Note added to the issue. |

Changes one service issue: status, assignee, schedule, or a note added to it. Use a status name from your database. A change can trigger the notifications your Rent Manager rules define, which is why this reaches other people. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "issue_id": "si_20744",
  "status": "Resolved",
  "assigned_to": "Sam Ortiz",
  "note_added": true
}
```

### add_history_note

Add a note to the History/Notes of a tenant. Internal, nothing is sent. Access: write. REST: `POST /api/v1/rent-manager/add_history_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `tenant_id` | string | yes | Tenant ID from list_tenants. |
| `note` | string | yes | Note text. |

Adds one note to the History/Notes of a tenant, under your user. Nothing is sent to the tenant or anyone else, and one more note corrects a mistake, so add_history_note runs without asking first.

Example response:

```json
{
  "tenant_id": "10482",
  "status": "added",
  "date": "2026-10-12"
}
```

### post_charge

Post a one-off charge to a tenant account. Access: write, asks the user first. REST: `POST /api/v1/rent-manager/post_charge`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `tenant_id` | string | yes | Tenant ID from list_tenants. |
| `charge_type` | string | yes | Charge type name from list_charge_types. |
| `amount` | string | yes | Decimal amount, e.g. 75.00. |
| `date` | date | no | Transaction date. Default: today. |
| `comment` | string | no | Shown on the ledger line. |

Posts one charge to one tenant account and returns the balance before and after. charge_type must be a name from list_charge_types. The date defaults to today. There is no undo tool: a wrong charge is corrected in Rent Manager. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "transaction_id": "884213",
  "tenant_id": "10482",
  "unit": "4B",
  "charge_type": "Late Fee",
  "amount": "50.00",
  "date": "2026-10-06",
  "previous_balance": "1200.00",
  "new_balance": "1250.00"
}
```

### send_text

Text a tenant through Rent Manager texting. Access: write, asks the user first. REST: `POST /api/v1/rent-manager/send_text`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `tenant_id` | string | yes | Tenant ID from list_tenants. |
| `message` | string | yes | Text message to the tenant. |

Sends one text message to one tenant through Rent Manager texting. The tenant needs a contact set up with SMS enabled. The text goes out under your Rent Manager account. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "tenant_id": "10482",
  "to": "Jordan Lee",
  "status": "sent",
  "sent_at": "2026-10-12T09:05:00-04:00"
}
```

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

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

### Connect Rent Manager to your agent.

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

2. **Sign in to Rent Manager once** Open the connect page from the console and sign in to Rent Manager 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 Rent Manager 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 Maple Court tenants who owe more than $500, check their ledger and History/Notes, and text a personal reminder to the ones who have not promised a payment date. Log each text.
```

### Call Rent Manager 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/rent-manager/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/rent-manager/post_charge \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tenant_id":"10482","charge_type":"Late Fee","amount":"50.00","date":"2026-10-06","comment":"October rent paid after the 5th"}'
```

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

```
{
  "transaction_id": "884213",
  "tenant_id": "10482",
  "unit": "4B",
  "charge_type": "Late Fee",
  "amount": "50.00",
  "date": "2026-10-06",
  "previous_balance": "1200.00",
  "new_balance": "1250.00"
}
```

## Why use Cotlet for Rent Manager?

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

## Is there a Rent Manager MCP server on GitHub?

Yes. A community Rent Manager MCP server exists on GitHub, maintained by one person. It is read only, needs API access enabled by Rent Manager, and you install and fix it yourself. Cotlet hosts and maintains the same kind of server for you, with write tools, and works through your browser login instead of API access.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Get API access enabled by Rent Manager, create an API user, install the server, add it to each MCP client | Request access, sign in to Rent Manager once, add one MCP server or API key |
| What it can do | The one we found reads data only: no charges, notes or texts | Reads, plus posting charges, service issues, notes and texts, each write confirmed by default |
| When Rent Manager changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your credentials | API username and password in the config file on your computer | Only your session, encrypted in an EU vault, never your password; revoked in one click |
| When the session expires | Calls fail until you fix the credentials by hand | If Rent Manager logs you out, your agent gets a link to sign in again |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, 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 Rent Manager 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 Rent Manager API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Rent Manager 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 Rent Manager 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 Rent Manager 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 Rent Manager tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Rent Manager 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.
- **Rent Manager's terms:** You use your own Rent Manager account and stay responsible for following Rent Manager's terms. Cotlet is independent and not affiliated with Rent Manager. [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 Rent Manager. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Rent Manager 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 Rent Manager session would leave my computer.**

Cotlet keeps your Rent Manager 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.

**Do I need to apply for Rent Manager API access?**

No. Cotlet works through your own browser login, not the API, so you do not go through the Integrations Partner Program or an API support request. It can only do what your Rent Manager user can do.

**Do I need Rent Manager Express?**

Cotlet signs in through the browser, so your account needs the browser-based Rent Manager Express. Rent Manager says Express combines the classic features of Rent Manager 12 and works with it on the same data.

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

No. Every call to create_service_issue, update_service_issue, post_charge or send_text waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_history_note runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Rent Manager 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/rent-manager/{tool} from the HTTP Request node.