# Hemnet API and MCP server

> Hemnet has no public or developer API for buyers or owners (checked 11 Oct 2026). Its own AI access is the Hemnet app inside ChatGPT, which runs only in ChatGPT and gives your agent or scripts no way to read your saved homes or saved searches.

Sweden's largest property portal, where brokers list homes for sale and buyers search listings, see sold prices (slutpriser) and keep saved homes, collections and saved searches in Mitt Hemnet.

## What is the Hemnet API?

Cotlet's Hemnet API exposes 13 endpoints for your own Hemnet account: search listings, get listing, search sold prices, list saved homes, list collections, list upcoming viewings, list saved searches, list followed homes, save home, remove saved home, create saved search, delete saved search and follow home. The search_listings endpoint returns homes for sale and coming to market (kommande), with price, fee, rooms and area. Each endpoint takes simple JSON inputs like location, listing_id or housing_types 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:** 13 (8 read, 5 write)
- **Updated:** 2026-10-11

Hemnet has no public or developer API for buyers or owners (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Hemnet with 13 endpoints (8 read, 5 write): your AI agent signs in as you and does the work.

## Does Hemnet have an official API?

Hemnet has no public or developer API for buyers or owners (checked 11 Oct 2026). Its own AI access is the Hemnet app inside ChatGPT, which runs only in ChatGPT and gives your agent or scripts no way to read your saved homes or saved searches.

| Task | Hemnet official | Cotlet |
|---|---|---|
| Search homes for sale | Partly: Only inside Hemnet's app in ChatGPT | Yes |
| Read a listing in full | Partly: Only inside Hemnet's app in ChatGPT | Yes |
| Look up sold prices (slutpriser) | No | Yes |
| List saved homes and collections (samlingar) | No | Yes |
| See viewings and bidding status of saved homes | No | Yes |
| Create or delete saved searches | No | Yes |
| Follow the value of a home over time | No | Yes |

Sources: [Hemnet app description: Mitt Hemnet features (App Store)](https://apps.apple.com/se/app/hemnet-hitta-din-dr%C3%B6mbostad/id525017304), [Hemnet Q1 2026 report: Hemnet as an app in ChatGPT](https://www.hemnetgroup.se/files/mfn/17ce0cc4-8a51-4f76-a9ef-a0f54b9d3e94/hemnet-quarterly-report-q1-2026-swe.pdf), [Hemnet: Så använder du Hemnet i ChatGPT (25 Mar 2026)](https://www.hemnet.se/artiklar/hemnet-nyheter/2026/03/29/sa-anvander-du-hemnet-i-chatgpt), [Hemnet press release: broker-published and aggregated listings (29 Sep 2026)](https://www.hemnetgroup.se/media/pressmeddelanden/2026/hemnet-starker-sin-ledarposition-genom-att-introducera-kostnadsfria-instegsannonser-for-att-samla-alla-publikt-tillgangliga-bostadsannonser-och-genomfor-samtidigt-en-omorganisation-for-okad-snabbhet-2/)

## For AI agents

```text
Hemnet has no public or developer API for buyers or owners (checked 11 Oct 2026). Its own AI access is the Hemnet app inside ChatGPT, which runs only in ChatGPT and gives your agent or scripts no way to read your saved homes or saved searches.
Cotlet provides a hosted MCP server and REST API for Hemnet: 13 tools (8 read, 5 write).
Access       Request access at https://cotlet.dev/app/signup?app=hemnet; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/hemnet
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        search_listings, get_listing, search_sold_prices, list_saved_homes, list_collections, list_upcoming_viewings, list_saved_searches, list_followed_homes, save_home, remove_saved_home, create_saved_search, delete_saved_search, follow_home
Confirm      save_home (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/hemnet-api-mcp-server.md

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

## What can an AI agent do in Hemnet?

Cotlet is best for home buyers and owners in Sweden who want their AI agent to watch saved homes, viewings, sold prices and home values on Hemnet without running or fixing a server.

- **[Plan weekend viewings of your saved homes](https://cotlet.dev/integrations/hemnet-api-mcp-server/plan-weekend-viewings)** (runs: weekly): "Which of my saved Hemnet homes in the "Flytt 2027" collection have a viewing this Saturday or Sunday? Put them in time order, flag any that overlap, and leave out homes where bidding has started." → `list_saved_homes`, `list_upcoming_viewings`, `get_listing`
- **[Compare asking prices with sold prices](https://cotlet.dev/integrations/hemnet-api-mcp-server/compare-listings-with-sold-prices)**: "Find 3-room flats for sale in Vasastan under 9 MSEK and, for each one, tell me what similar 3-room flats nearby sold for since January: price per m² and how far above asking they went." → `search_listings`, `get_listing`, `search_sold_prices`
- **Create a saved search with alerts**: "Set up a saved search for villas in Täby under 9 MSEK with live push notifications." → `create_saved_search`
- **Add homes to a shared collection**: "Add the two Södermalm listings I liked to our "Flytt 2027" collection." → `list_collections`, `save_home`
- **Track the value of your home** (runs: weekly): "How has the value of my flat and my parents' house changed since spring?" → `list_followed_homes`, `follow_home`

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

Yes. Cotlet does not replace your automation platform: it gives it a Hemnet 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 plan weekend viewings of your saved homes, 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/hemnet/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/hemnet/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/hemnet/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/hemnet/{tool} with your API key. | cron or GitHub Actions. |

## Tools

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

### search_listings

Homes for sale and coming to market (kommande), with price, fee, rooms and area. Access: read. REST: `POST /api/v1/hemnet/search_listings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location` | string | yes | Area, municipality or street, e.g. "Vasastan, Stockholm". |
| `housing_types` | string[] | no | Any of apartment, villa, townhouse, holiday_home, plot, farm. Default: all. |
| `price_min` | integer | no | Minimum asking price in SEK. |
| `price_max` | integer | no | Maximum asking price in SEK. |
| `rooms_min` | integer | no | Minimum number of rooms. |
| `living_area_min` | integer | no | Minimum living area in m². |
| `include_upcoming` | boolean | no | Include homes coming to market. Default: true. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns homes for sale in an area that match your filters, and homes coming to market unless include_upcoming is false. Each item has the asking price, monthly fee, rooms and living area. Pages hold up to 50 homes; pass next_cursor back as cursor for the next page. Use listing_id with get_listing or save_home.

Example response:

```json
{
  "listings": [
    {
      "listing_id": "l_21730488",
      "address": "Karlbergsvägen 120, Vasastan, Stockholm",
      "type": "apartment",
      "rooms": 3,
      "living_area_m2": 68,
      "asking_price_sek": 5450000,
      "monthly_fee_sek": 4120,
      "status": "for_sale"
    }
  ],
  "next_cursor": null
}
```

### get_listing

Full listing: price, monthly fee, area, rooms, viewing times, bidding status and broker. Access: read. REST: `POST /api/v1/hemnet/get_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from search_listings or list_saved_homes. |

Returns one listing as the listing page shows it: asking price, monthly fee, rooms, living area, the broker, viewing times and whether bidding has started. Use it after search_listings to read a home in full.

Example response:

```json
{
  "listing_id": "l_21730488",
  "address": "Karlbergsvägen 120, Vasastan, Stockholm",
  "type": "apartment",
  "rooms": 3,
  "living_area_m2": 68,
  "asking_price_sek": 5450000,
  "monthly_fee_sek": 4120,
  "bidding_started": false,
  "viewings": [
    "2026-10-17T12:00:00+02:00"
  ],
  "broker": "Exempel Mäkleri, Vasastan",
  "url": "https://www.hemnet.se/bostad/l_21730488"
}
```

### search_sold_prices

Sold homes (slutpriser) with final price, asking price and sale date. Access: read. REST: `POST /api/v1/hemnet/search_sold_prices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location` | string | yes | Area, municipality or street, e.g. "Vasastan, Stockholm". |
| `housing_types` | string[] | no | Any of apartment, villa, townhouse, holiday_home, plot, farm. |
| `sold_since` | date | no | Only homes sold on or after this date. |
| `rooms_min` | integer | no | Minimum number of rooms. |
| `limit` | integer | no | 1 to 100. Default: 50. |

Returns homes sold in an area, with final price, asking price, how far the sale landed above or below asking, and the sale date. Narrow it with sold_since, housing type and rooms. Pages hold up to 100 homes.

Example response:

```json
{
  "sold": [
    {
      "address": "Odengatan 40, Vasastan, Stockholm",
      "rooms": 3,
      "living_area_m2": 71,
      "asking_price_sek": 4250000,
      "final_price_sek": 4500000,
      "over_asking_pct": 5.9,
      "sold_on": "2026-09-12"
    },
    {
      "address": "Sveavägen 98, Vasastan, Stockholm",
      "rooms": 3,
      "living_area_m2": 74,
      "asking_price_sek": 5200000,
      "final_price_sek": 5150000,
      "over_asking_pct": -1,
      "sold_on": "2026-06-03"
    }
  ]
}
```

### list_saved_homes

Homes you saved, with collection, status (for sale, bidding, sold) and final price when sold. Access: read. REST: `POST /api/v1/hemnet/list_saved_homes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `collection_id` | string | no | Only homes in this collection, from list_collections. |

Returns the homes in your saved homes, with the collection each is in. Status is for_sale, bidding or sold; a sold home carries its final price. Pass collection_id to see one collection only.

Example response:

```json
{
  "saved_homes": [
    {
      "listing_id": "l_21730488",
      "address": "Karlbergsvägen 120, Vasastan, Stockholm",
      "collection": "Flytt 2027",
      "status": "for_sale",
      "asking_price_sek": 5450000
    },
    {
      "listing_id": "l_21644102",
      "address": "Hornsgatan 55, Södermalm, Stockholm",
      "collection": "Flytt 2027",
      "status": "sold",
      "final_price_sek": 6100000
    }
  ]
}
```

### list_collections

Your collections (samlingar) of saved homes, with who they are shared with. Access: read. REST: `POST /api/v1/hemnet/list_collections`.

No parameters.

Returns your collections with the number of homes in each and the people each is shared with. Use collection_id with list_saved_homes and save_home.

Example response:

```json
{
  "collections": [
    {
      "collection_id": "col_flytt27",
      "name": "Flytt 2027",
      "homes": 2,
      "shared_with": [
        "Maria"
      ]
    },
    {
      "collection_id": "col_sommar",
      "name": "Sommarstuga",
      "homes": 0,
      "shared_with": []
    }
  ]
}
```

### list_upcoming_viewings

Viewing times of your saved homes, soonest first, with address and broker. Access: read. REST: `POST /api/v1/hemnet/list_upcoming_viewings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `until` | date | no | Only viewings up to this date. Default: 14 days ahead. |

Returns the viewings of your saved homes that have not happened yet, soonest first, with address and broker. It looks 14 days ahead unless you set until.

Example response:

```json
{
  "viewings": [
    {
      "listing_id": "l_21730488",
      "address": "Karlbergsvägen 120, Vasastan, Stockholm",
      "starts_at": "2026-10-17T12:00:00+02:00",
      "broker": "Exempel Mäkleri, Vasastan",
      "bidding_started": false
    }
  ]
}
```

### list_saved_searches

Your saved searches with filters and notification settings. Access: read. REST: `POST /api/v1/hemnet/list_saved_searches`.

No parameters.

Returns your saved searches with their filters, how you are notified (email or push) and how often. Use saved_search_id with delete_saved_search.

Example response:

```json
{
  "saved_searches": [
    {
      "saved_search_id": "ss_48213",
      "location": "Täby kommun",
      "filters": {
        "housing_types": [
          "villa"
        ],
        "price_max": 9000000,
        "rooms_min": 5
      },
      "notify_by": "push",
      "frequency": "live"
    }
  ]
}
```

### list_followed_homes

Your own home and other homes you follow, with the value Hemnet shows over time. Access: read. REST: `POST /api/v1/hemnet/list_followed_homes`.

No parameters.

Returns the homes whose value you follow, your own and others, each with the value Hemnet shows and how it changed over time. The value is Hemnet's estimate. Homes that are not for sale can be followed too.

Example response:

```json
{
  "followed_homes": [
    {
      "address": "Storgatan 1, Uppsala",
      "estimated_value_sek": 3980000,
      "change_since_start_pct": 2.4,
      "history": [
        {
          "date": "2026-04-01",
          "value_sek": 3890000
        },
        {
          "date": "2026-10-01",
          "value_sek": 3980000
        }
      ]
    }
  ]
}
```

### save_home

Save a listing to your saved homes, optionally into one of your collections. Access: write, asks the user first. REST: `POST /api/v1/hemnet/save_home`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from search_listings or list_saved_homes. |
| `collection_id` | string | no | Collection from list_collections. |

Saves a listing to your saved homes, and into a collection when collection_id is set. People a collection is shared with see the new home, which is why this asks first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "l_21730488",
  "saved": true,
  "collection_id": "col_flytt27"
}
```

### remove_saved_home

Remove a listing from your saved homes. Access: write. REST: `POST /api/v1/hemnet/remove_saved_home`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from search_listings or list_saved_homes. |

Removes a listing from your saved homes and from its collection. It runs without asking: nobody is notified and save_home undoes it in one call.

Example response:

```json
{
  "listing_id": "l_21644102",
  "saved": false
}
```

### create_saved_search

Save a search and get notified about new homes that match it. Access: write. REST: `POST /api/v1/hemnet/create_saved_search`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location` | string | yes | Area, municipality or street, e.g. "Vasastan, Stockholm". |
| `filters` | object | no | Any of housing_types, price_min, price_max, rooms_min, living_area_min. |
| `notify_by` | enum | no | email or push. Default: email. |
| `frequency` | enum | no | live or summary. Default: summary. |

Creates a saved search and returns how many homes match it now. Notifications go to you by email or push, live or as a summary. It runs without asking: it reaches no one else and delete_saved_search undoes it in one call.

Example response:

```json
{
  "saved_search_id": "ss_48213",
  "location": "Täby kommun",
  "filters": {
    "housing_types": [
      "villa"
    ],
    "price_max": 9000000,
    "rooms_min": 5
  },
  "notify_by": "push",
  "frequency": "live",
  "matching_now": 37
}
```

### delete_saved_search

Delete one of your saved searches and its notifications. Access: write. REST: `POST /api/v1/hemnet/delete_saved_search`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `saved_search_id` | string | yes | Saved search ID from list_saved_searches. |

Deletes one saved search and stops its notifications. It runs without asking: it reaches no one else, and create_saved_search with the same filters brings it back.

Example response:

```json
{
  "saved_search_id": "ss_48213",
  "deleted": true
}
```

### follow_home

Follow the value of any home by address, on the market or not. Access: write. REST: `POST /api/v1/hemnet/follow_home`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `address` | string | yes | Street address with town, e.g. "Storgatan 1, Uppsala". |

Adds a home to the homes whose value you follow, for sale or not. It changes only your own list, so it runs without asking. Unfollowing is done in the Hemnet app.

Example response:

```json
{
  "address": "Storgatan 1, Uppsala",
  "following": true,
  "estimated_value_sek": 3980000
}
```

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

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

### Connect Hemnet to your agent.

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

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

```
Which of my saved Hemnet homes in the "Flytt 2027" collection have a viewing this Saturday or Sunday? Put them in time order, flag any that overlap, and leave out homes where bidding has started.
```

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

```
curl https://cotlet.dev/api/v1/hemnet/create_saved_search \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"location":"Täby","filters":{"housing_types":["villa"],"price_max":9000000,"rooms_min":5},"notify_by":"push","frequency":"live"}'
```

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

```
{
  "saved_search_id": "ss_48213",
  "location": "Täby kommun",
  "filters": {
    "housing_types": [
      "villa"
    ],
    "price_max": 9000000,
    "rooms_min": 5
  },
  "notify_by": "push",
  "frequency": "live",
  "matching_now": 37
}
```

## Why use Cotlet for Hemnet?

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

## Is there a Hemnet MCP server on GitHub?

Yes. Community Hemnet MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer and keep it running yourself; they read public listings and sold prices anonymously, so they cannot reach your saved homes or saved searches, and when Hemnet changes its site they stop working until someone fixes them. Cotlet hosts a server for you that works in your own Hemnet account, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Install with npx, add it to each MCP client; a browser extension if Hemnet shows a bot check | Request access, sign in to Hemnet once, add one MCP server or API key |
| Your account | Not reachable: public listings and sold prices only | Saved homes, collections, saved searches and followed homes |
| Write actions | None | Save homes, create and delete saved searches, follow homes |
| When Hemnet changes | It breaks until the maintainer fixes it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Hemnet session | No session: nothing of yours is used | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| 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 Hemnet 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 Hemnet API cost?

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

**Do I need to be technical?**

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

Cotlet keeps your Hemnet 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 a Hemnet account?**

Yes. The tools work in your own Mitt Hemnet account, where saved homes, collections, saved searches and followed homes live. You sign in yourself in a browser; Cotlet keeps the session, never your password, and never bypasses a verification step.

**Can it publish or edit listings as a broker?**

No. These tools are for buyers and owners. Brokers publish listings to Hemnet themselves (Hemnet press release, 29 Sep 2026), and Cotlet does not create or change listings.

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

No. Every call to save_home waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. remove_saved_home, create_saved_search, delete_saved_search, follow_home runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Hemnet 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/hemnet/{tool} from the HTTP Request node.