# Polarsteps API and MCP server

> Polarsteps has no public API and no official MCP server (checked 11 Oct 2026). The only official way out of the app is "Download my data", an archive of your whole account that arrives by email, and there is no way to create trips or add steps from outside the app and website.

Travel app that tracks your route, turns each place into a step with photos and a story, and lets followers and Travel Buddies see your trip or order a printed Travel Book.

## What is the Polarsteps API?

Cotlet's Polarsteps API exposes 14 endpoints for your own Polarsteps account: list trips, get trip, list steps, get step, list step comments, get travel stats, export trip, create trip, add step, import steps, update step, add step photos, reply to step comment and set trip privacy. The list_trips endpoint returns your trips, newest first, with dates, privacy level, distance and step count. Each endpoint takes simple JSON inputs like trip_id, step_id or privacy and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Travel](https://cotlet.dev/integrations/category/travel)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-11

Polarsteps has no public API and no official MCP server (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Polarsteps with 14 endpoints (7 read, 7 write): your AI agent signs in as you and does the work.

## Does Polarsteps have an official API?

Polarsteps has no public API and no official MCP server (checked 11 Oct 2026). The only official way out of the app is "Download my data", an archive of your whole account that arrives by email, and there is no way to create trips or add steps from outside the app and website.

| Task | Polarsteps official | Cotlet |
|---|---|---|
| List your trips | No | Yes |
| Read steps with story, place, date and photos | Partly: Only inside the full account archive | Yes |
| Export one trip | Partly: Whole account archive only, sent by email | Yes |
| Create a trip, past or upcoming | No | Yes |
| Add a step with photos | No | Yes |
| Edit step text, place or date | No | Yes |
| Reply to comments on a step | No | Yes |
| Change who can see a trip | No | Yes |

Sources: [Polarsteps Help: How can I export a copy of my data?](https://support.polarsteps.com/hc/en-us/articles/24266264821138-How-can-I-export-a-copy-of-my-data), [Polarsteps Help: What are steps and how do I add or edit them?](https://support.polarsteps.com/hc/en-us/articles/23760478173586-What-are-steps-and-how-do-I-add-or-edit-them), [Polarsteps Help: How do I create my first trip?](https://support.polarsteps.com/hc/en-us/articles/29003811909394-How-do-I-create-my-first-trip), [Polarsteps: Account and trip privacy](https://www.polarsteps.com/account-and-trip-privacy), [Polarsteps Help: Can I export my trip into a PDF file?](https://support.polarsteps.com/hc/en-us/articles/24268063526802-Can-I-export-my-trip-into-a-PDF-file), [Polarsteps Help: Can I import a GPX or other location-file into Polarsteps?](https://support.polarsteps.com/hc/en-us/articles/24267546737426-Can-I-import-a-GPX-or-other-location-file-into-Polarsteps), [Polarsteps Help: Can I embed my Polarsteps trip on my website?](https://support.polarsteps.com/hc/en-us/articles/24267931784466-Can-I-embed-my-Polarsteps-trip-on-my-website)

## For AI agents

```text
Polarsteps has no public API and no official MCP server (checked 11 Oct 2026). The only official way out of the app is "Download my data", an archive of your whole account that arrives by email, and there is no way to create trips or add steps from outside the app and website.
Cotlet provides a hosted MCP server and REST API for Polarsteps: 14 tools (7 read, 7 write).
Access       Request access at https://cotlet.dev/app/signup?app=polarsteps; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/polarsteps
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_trips, get_trip, list_steps, get_step, list_step_comments, get_travel_stats, export_trip, create_trip, add_step, import_steps, update_step, add_step_photos, reply_to_step_comment, set_trip_privacy
Confirm      create_trip, add_step, import_steps, update_step, add_step_photos, reply_to_step_comment, set_trip_privacy (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/polarsteps-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=polarsteps (Polarsteps is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Polarsteps 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 Polarsteps 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 Polarsteps 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 Polarsteps 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 Polarsteps's terms; Cotlet is not affiliated with Polarsteps.
```

## What can an AI agent do in Polarsteps?

Cotlet is best for Polarsteps travelers who want their AI agent to export trips, add and fix steps and answer comments without running or fixing a server.

- **[Export a single trip as GPX](https://cotlet.dev/integrations/polarsteps-api-mcp-server/export-trip-gpx)**: "Export my Patagonia trip as a GPX file for Komoot and a Markdown journal, without the photos." → `list_trips`, `export_trip`
- **[Turn a trip into a blog post](https://cotlet.dev/integrations/polarsteps-api-mcp-server/trip-to-blog-post)**: "Turn my Japan trip into a draft blog post: one section per city, the best two photos of each step, and a map embed at the top." → `list_trips`, `get_trip`, `list_steps`, `get_step`
- **[Import a past trip from a spreadsheet](https://cotlet.dev/integrations/polarsteps-api-mcp-server/import-past-trip)**: "I did Vietnam in 2019, before I had Polarsteps. Create the trip as private and import the 12 places in vietnam.csv as steps, with the photo links from the last column." → `list_trips`, `create_trip`, `import_steps`, `add_step`
- **[Proofread a trip before ordering a Travel Book](https://cotlet.dev/integrations/polarsteps-api-mcp-server/proofread-trip-for-travel-book)**: "I am ordering a Travel Book of my New Zealand trip. Fix typos and capitals in every step story, keep my wording, and do not touch dates or places." → `list_trips`, `list_steps`, `get_step`, `update_step`
- **Add a step with photos from your notes**: "Add today's step in Lisbon with these 4 photos and a short story from my notes." → `list_trips`, `add_step`
- **Reply to follower comments** (runs: daily): "Show me new comments on my current trip and draft a reply to each one." → `list_steps`, `list_step_comments`, `reply_to_step_comment`

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

Yes. Cotlet does not replace your automation platform: it gives it a Polarsteps connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to reply to follower comments, 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/polarsteps/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/polarsteps/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/polarsteps/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/polarsteps/{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 Polarsteps.

### list_trips

Your trips, newest first, with dates, privacy level, distance and step count. Access: read. REST: `POST /api/v1/polarsteps/list_trips`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | all, planned, ongoing or past. Default: all. |
| `limit` | integer | no | 1 to 100. Default: 50. |

Returns the trips on your own account, newest first. Filter by status to see only planned, ongoing or past trips. Use trip_id from each item in the other endpoints.

Example response:

```json
{
  "trips": [
    {
      "trip_id": "18452237",
      "name": "Portugal by train",
      "start_date": "2026-10-01",
      "end_date": null,
      "privacy": "followers",
      "steps": 9,
      "distance_km": 612
    },
    {
      "trip_id": "16720458",
      "name": "Patagonia",
      "start_date": "2025-12-04",
      "end_date": "2026-01-19",
      "privacy": "everyone",
      "steps": 41,
      "distance_km": 3870
    }
  ]
}
```

### get_trip

One trip: name, summary, dates, privacy, Travel Buddies, distance and countries. Access: read. REST: `POST /api/v1/polarsteps/get_trip`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `trip_id` | string | yes | Trip ID from list_trips. |

Returns one trip with its summary, start and end dates, privacy level and the Travel Buddies on it. Trip dates are separate from the dates of its steps.

Example response:

```json
{
  "trip_id": "18452237",
  "name": "Portugal by train",
  "summary": "Two weeks from Porto to Faro on regional trains.",
  "start_date": "2026-10-01",
  "end_date": null,
  "privacy": "followers",
  "travel_buddies": [
    "Marta Silva"
  ],
  "distance_km": 612,
  "countries": [
    "Portugal"
  ]
}
```

### list_steps

Steps of a trip in order, with place, country, date, title and photo count. Access: read. REST: `POST /api/v1/polarsteps/list_steps`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `trip_id` | string | yes | Trip ID from list_trips. |
| `since` | date | no | Only steps on or after this date. |

Lists the steps of one trip in the order of the trip. Story is a short preview; get_step returns the full text, coordinates and photo links. Pass since to see only steps from a given date.

Example response:

```json
{
  "steps": [
    {
      "step_id": "231908554",
      "title": "Fado night in Alfama",
      "place": "Lisbon",
      "country": "Portugal",
      "date": "2026-10-09T19:30:00+01:00",
      "photos": 2,
      "comments": 1
    },
    {
      "step_id": "231544107",
      "title": "Tram 28 to Graça",
      "place": "Lisbon",
      "country": "Portugal",
      "date": "2026-10-09T11:10:00+01:00",
      "photos": 3,
      "comments": 0
    }
  ]
}
```

### get_step

Full step: story text, place and coordinates, date, photo and video links. Access: read. REST: `POST /api/v1/polarsteps/get_step`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `step_id` | string | yes | Step ID from list_steps. |

Returns one step with its full story, the place and its coordinates, the date and time, and links to every photo and video. Use it before editing a step or turning it into a post.

Example response:

```json
{
  "step_id": "231908554",
  "trip_id": "18452237",
  "title": "Fado night in Alfama",
  "story": "Got lost in the old town, then found a tiny fado bar with six tables.",
  "place": "Alfama, Lisbon, Portugal",
  "coordinates": {
    "lat": 38.711,
    "lon": -9.1304
  },
  "date": "2026-10-09T19:30:00+01:00",
  "media": [
    "https://example.com/photos/alfama-1.jpg",
    "https://example.com/photos/alfama-2.jpg"
  ]
}
```

### list_step_comments

Comments your followers left on a step, with author and date. Access: read. REST: `POST /api/v1/polarsteps/list_step_comments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `step_id` | string | yes | Step ID from list_steps. |

Returns the comments on one step, oldest first, with author and date. Replies from you are included under the comment they answer. Use comment_id with reply_to_step_comment.

Example response:

```json
{
  "comments": [
    {
      "comment_id": "cm_4821",
      "author": "Eva Novak",
      "body": "That fado bar looks amazing!",
      "created_at": "2026-10-09T21:05:00+01:00",
      "replies": []
    }
  ]
}
```

### get_travel_stats

Countries visited, total kilometers, number of trips and steps on your profile. Access: read. REST: `POST /api/v1/polarsteps/get_travel_stats`.

No parameters.

Returns the figures from the Travel stats on your profile: countries visited, kilometers, trips and steps. Countries are counted from the steps you add.

Example response:

```json
{
  "countries": 14,
  "distance_km": 28640,
  "trips": 6,
  "steps": 187
}
```

### export_trip

One trip as a download link, valid for 1 hour: route, steps and photo links. Access: read. REST: `POST /api/v1/polarsteps/export_trip`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `trip_id` | string | yes | Trip ID from list_trips. |
| `format` | enum | no | json, gpx or markdown. Default: json. |
| `include_media` | boolean | no | Add a zip of full-size photos and videos. Default: false. |

Exports one trip as json, gpx or markdown and returns a download link valid for 1 hour. gpx holds the route, markdown holds the step stories. Set include_media for a zip of the full-size photos and videos. It only reads, so it never asks for your OK.

Example response:

```json
{
  "trip_id": "16720458",
  "format": "gpx",
  "download_url": "https://example.com/exports/16720458.gpx",
  "expires_at": "2026-10-11T15:00:00+02:00",
  "steps": 41
}
```

### create_trip

New trip, past or upcoming, with the privacy level you pick. Access: write, asks the user first. REST: `POST /api/v1/polarsteps/create_trip`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Trip name. |
| `start_date` | date | yes | First day of the trip. Can be in the past. |
| `end_date` | date | no | Last day. Leave empty for an ongoing trip. |
| `summary` | string | no | Short trip description. |
| `privacy` | enum | no | only_me, followers or everyone. Default: only_me. |

Creates a trip with a name and start date. The start date can be in the past, for a trip from before you used Polarsteps. Privacy is Only me (only_me) unless you set followers or everyone, so nothing is shared by accident. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "trip_id": "20931176",
  "name": "Vietnam 2019",
  "start_date": "2019-03-02",
  "end_date": "2019-03-20",
  "privacy": "only_me",
  "steps": 0
}
```

### add_step

Add a step to a trip with a story and photos. People who can see the trip see it. Access: write, asks the user first. REST: `POST /api/v1/polarsteps/add_step`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `trip_id` | string | yes | Trip ID from list_trips. |
| `place` | string | yes | Place name or "lat,lon". |
| `date` | datetime | yes | ISO 8601 with time zone. |
| `title` | string | no | Step title. Default: the place name. |
| `story` | string | no | Step text. |
| `photo_urls` | string[] | no | Photo or video URLs to attach. |

Adds one step to a trip at a place and time, with an optional title, story and photos by URL. The date and place set where the step sits on the route. Everyone who can see the trip, by its privacy level, sees the step. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "step_id": "231908554",
  "trip_id": "18452237",
  "title": "Fado night in Alfama",
  "place": "Lisbon, Portugal",
  "date": "2026-10-09T19:30:00+01:00",
  "photos": 2
}
```

### import_steps

Add many steps at once, e.g. a past trip from a CSV, sorted by date. Access: write, asks the user first. REST: `POST /api/v1/polarsteps/import_steps`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `trip_id` | string | yes | Trip ID from list_trips. |
| `steps` | object[] | yes | Up to 50 items of { place, date, title, story, photo_urls }. place and date are required. |

Adds up to 50 steps to one trip in a single call and sorts them by date, so the route draws in travel order. Each step needs a place and a date. The OK covers the whole batch. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "trip_id": "20931176",
  "added": 2,
  "steps": [
    {
      "step_id": "301440018",
      "title": "Arrival in Hanoi",
      "date": "2019-03-02T09:00:00+07:00"
    },
    {
      "step_id": "301440019",
      "title": "Boat to Ha Long Bay",
      "date": "2019-03-05T08:00:00+07:00"
    }
  ]
}
```

### update_step

Change the title, story, place or date of a step. Access: write, asks the user first. REST: `POST /api/v1/polarsteps/update_step`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `step_id` | string | yes | Step ID from list_steps. |
| `fields` | object | yes | Any of title, story, place, date. |

Changes the fields you send and leaves the rest of the step as it is. Changing the place or date moves the step on the route. Trip start and end dates are not changed. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "step_id": "231908554",
  "updated": [
    "story"
  ],
  "date": "2026-10-09T19:30:00+01:00"
}
```

### add_step_photos

Add photos or videos to an existing step. Access: write, asks the user first. REST: `POST /api/v1/polarsteps/add_step_photos`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `step_id` | string | yes | Step ID from list_steps. |
| `photo_urls` | string[] | yes | Photo or video URLs. |

Attaches photos or videos by URL to a step that already exists. People who can see the trip see them. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "step_id": "231908554",
  "added": 2,
  "photos_total": 4
}
```

### reply_to_step_comment

Reply to a follower comment on one of your steps, as you. Access: write, asks the user first. REST: `POST /api/v1/polarsteps/reply_to_step_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `step_id` | string | yes | Step ID from list_steps. |
| `comment_id` | string | yes | Comment ID from list_step_comments. |
| `body` | string | yes | Reply text. |

Adds a reply under a comment on your step. The reply appears under your name for people who can see the trip. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": "cm_4822",
  "parent_comment_id": "cm_4821",
  "step_id": "231908554",
  "status": "published"
}
```

### set_trip_privacy

Choose who can see a trip: only you, your followers or everyone. Access: write, asks the user first. REST: `POST /api/v1/polarsteps/set_trip_privacy`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `trip_id` | string | yes | Trip ID from list_trips. |
| `privacy` | enum | yes | only_me, followers or everyone. |

Sets the privacy level of one trip to Only me, Followers or Everyone. It applies to the trip with all its steps. Followers can also see the trip through the secret link. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "trip_id": "18452237",
  "privacy": "everyone"
}
```

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

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

### Connect Polarsteps to your agent.

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

2. **Sign in to Polarsteps once** Open the connect page from the console and sign in to Polarsteps 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 Polarsteps 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.

```
Export my Patagonia trip as a GPX file for Komoot and a Markdown journal, without the photos.
```

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

```
curl https://cotlet.dev/api/v1/polarsteps/add_step \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"trip_id":"18452237","place":"Alfama, Lisbon, Portugal","date":"2026-10-09T19:30:00+01:00","title":"Fado night in Alfama","story":"Got lost in the old town, then found a tiny fado bar with six tables.","photo_urls":["https://example.com/photos/alfama-1.jpg","https://example.com/photos/alfama-2.jpg"]}'
```

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

```
{
  "step_id": "231908554",
  "trip_id": "18452237",
  "title": "Fado night in Alfama",
  "place": "Lisbon, Portugal",
  "date": "2026-10-09T19:30:00+01:00",
  "photos": 2
}
```

## Why use Cotlet for Polarsteps?

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

## Is there a Polarsteps MCP server on GitHub?

Yes. Community Polarsteps MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, sign it in to Polarsteps, and keep it running yourself; when Polarsteps changes its app, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, sign it in to Polarsteps, add it to each MCP client | Request access, sign in to Polarsteps once, add one MCP server or API key |
| When Polarsteps 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 Polarsteps session | In a file or variable on your computer, readable by any program you run | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When the session expires | Tools fail until you sign in again by hand | We keep it alive; if Polarsteps logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts |
| 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 Polarsteps 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 Polarsteps API cost?

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

**Do I need to be technical?**

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

Cotlet keeps your Polarsteps 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 my agent export trips I follow?**

No. Cotlet works in your own Polarsteps account and lists the trips on it. Trips you only follow are not part of list_trips.

**Who sees a step my agent adds?**

Everyone who can see that trip. Polarsteps trips have three privacy levels, Only me, Followers and Everyone, and a new trip is set to Followers in the app. add_step asks for your OK by default.

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

No. Every call to create_trip, add_step, import_steps, update_step, add_step_photos, reply_to_step_comment or set_trip_privacy 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 Polarsteps 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/polarsteps/{tool} from the HTTP Request node.