[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Dext API and MCP server

> Dext has no public developer API and no API docs on dext.com, and no official MCP server (checked 14 Oct 2026). The only official connection is the Zapier app, with 3 triggers and 4 actions: it submits receipts and sales invoices, reads processed receipts and creates client accounts.

Bookkeeping software that reads receipts, bills and sales invoices, extracts supplier, date, category and amounts, and publishes them to accounting software such as Xero or QuickBooks.

## What is the Dext API?

Cotlet's Dext API exposes 10 endpoints for your own Dext account: list document owners, list items, get item, get item history, export items, upload document, update item, publish items, archive items and unarchive items. The list_document_owners endpoint returns users you can assign as document owner when uploading. Each endpoint takes simple JSON inputs like item_ids, inbox or item_id and works both as an operation of the dext_read or dext_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm.md)
- **Endpoints:** 10 (5 read, 5 write)
- **Updated:** 2026-10-22

Dext has no public developer API and no API docs on dext.com, and no official MCP server (checked 14 Oct 2026). Cotlet is a hosted MCP server and REST API for Dext with 10 endpoints (5 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Dext have an official API?

Dext has no public developer API and no API docs on dext.com, and no official MCP server (checked 14 Oct 2026). The only official connection is the Zapier app, with 3 triggers and 4 actions: it submits receipts and sales invoices, reads processed receipts and creates client accounts.

| Task | Dext official | Cotlet |
|---|---|---|
| Upload receipts and bills | Partly: Zapier submits receipts and sales invoices as images | Yes |
| List items in the Inbox and To review | No | Yes |
| Read extracted data of an item | Partly: Zapier triggers send processed receipt data once it is ready | Yes |
| Edit extracted data | No | Yes |
| Publish items to the accounting software | No | Yes |
| Archive and unarchive items | No | Yes |
| Export costs as CSV, PDF or ZIP | No | Yes |
| Read the audit history of an item | No | Yes |

Sources: [Dext on Zapier: triggers and actions](https://zapier.com/apps/dext/integrations), [Dext Help: Editing, publishing and exporting items](https://help.dext.com/en/articles/416716-editing-publishing-and-exporting-items), [Dext Help: How to upload costs and sales documents](https://help.dext.com/en/s/article/how-to-upload-costs-sales-documents)

## For AI agents

```text
Dext has no public developer API and no API docs on dext.com, and no official MCP server (checked 14 Oct 2026). The only official connection is the Zapier app, with 3 triggers and 4 actions: it submits receipts and sales invoices, reads processed receipts and creates client accounts.
Cotlet provides a hosted MCP server and REST API for Dext: 10 tools (5 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=dext, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    dext_read, dext_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/dext, each operation at its own route, e.g. POST /api/v1/dext/items/publish
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_document_owners, list_items, get_item, get_item_history, export_items, upload_document, update_item, publish_items, archive_items, unarchive_items
Confirm      publish_items, unarchive_items (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/dext-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=dext, requests Dext in the Cotlet console and creates an API key there.
2. The user signs in to Dext once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Dext for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Dext server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Dext in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Dext only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Dext login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Dext's terms; Cotlet is not affiliated with Dext.
```

## What can an AI agent do in Dext?

Cotlet is best for bookkeepers and small business owners who use Dext and want an AI agent to upload, review and publish receipts without running or fixing a server.

- **[Upload receipts and bills in bulk](https://cotlet.dev/integrations/dext-api-mcp-server/upload-receipts-and-bills.md)** (runs: weekly): "Upload these PDFs and JPGs to the Dext Costs inbox with me as document owner, then tell me which items landed in To review." → `list_document_owners`, `upload_document`, `list_items`
- **[Fix items stuck in To review](https://cotlet.dev/integrations/dext-api-mcp-server/fix-items-in-to-review.md)** (runs: daily): "List my Dext Costs items in To review, fill in the missing category from the supplier's earlier items where it is obvious, and leave the rest for me with the reason." → `list_items`, `get_item`, `update_item`
- **[Publish ready items to your accounting software](https://cotlet.dev/integrations/dext-api-mcp-server/publish-ready-items.md)** (runs: weekly): "Publish all Ready Dext Costs items for October to Xero as drafts, then list anything still in To review." → `list_items`, `publish_items`, `archive_items`
- **Export costs to CSV every month**: "Export all Dext Costs items from the Archive for last month as a CSV and give me the download link." → `list_items`, `export_items`

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

Yes. Cotlet does not replace your automation platform: it gives it a Dext 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 upload receipts and bills in bulk, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/dext/document-owners. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/dext/document-owners with your API key. | cron or GitHub Actions. |

## Tools

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

### list_document_owners

Users you can assign as document owner when uploading. Access: read. REST: `GET /api/v1/dext/document-owners`. MCP: `dext_read → list_document_owners`.

No parameters.

Returns the users shown in the Document owner dropdown of Add documents. Use the owner_id as document_owner in upload_document. None is always allowed for costs such as rent.

Example response:

```json
{
  "owners": [
    {
      "owner_id": "u_41",
      "name": "Dana Reyes"
    },
    {
      "owner_id": "u_42",
      "name": "Chris Wong"
    }
  ]
}
```

### list_items

Items in the Costs or Sales inbox or Archive with status, supplier, date and total, newest first. Access: read. REST: `GET /api/v1/dext/items`. MCP: `dext_read → list_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `inbox` | enum | no | costs or sales. Default: costs. |
| `status` | enum | no | processing, to_review, ready or archived. Default: all except archived. |
| `supplier` | string | no | Only items from this supplier. |
| `date_from` | date | no | Only items dated on or after this date. |
| `date_to` | date | no | Only items dated on or before this date. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists items from one inbox, newest first. Status is processing, to_review, ready or archived, the sections of the Dext Inbox. Items in to_review miss a Category, Supplier or Total amount. Pages hold up to 100 items; pass next_cursor back as cursor.

Example response:

```json
{
  "items": [
    {
      "item_id": "it_7f3a10",
      "status": "to_review",
      "supplier": "Staples Inc",
      "date": "2026-10-09",
      "currency": "USD",
      "total_amount": 84.5,
      "category": null,
      "missing": [
        "category"
      ]
    },
    {
      "item_id": "it_7f3a11",
      "status": "ready",
      "supplier": "Shell",
      "date": "2026-10-10",
      "currency": "USD",
      "total_amount": 61.2,
      "category": "Fuel",
      "missing": []
    }
  ],
  "next_cursor": null
}
```

### get_item

One item with all extracted fields, publishing state and note. Access: read. REST: `GET /api/v1/dext/items/{item_id}`. MCP: `dext_read → get_item`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_id` | string | yes | Item ID from list_items. |

Returns the fields of the Item details page: supplier, date, document reference, category, description, currency, total, tax and net amount, paid state, payment method and publish destination. Due date is returned for invoices only. Publishing errors are included when a publish failed.

Example response:

```json
{
  "item_id": "it_7f3a10",
  "inbox": "costs",
  "status": "to_review",
  "supplier": "Staples Inc",
  "date": "2026-10-09",
  "document_reference": "INV-30211",
  "category": null,
  "description": "Printer paper and toner",
  "currency": "USD",
  "total_amount": 84.5,
  "tax_amount": 14.08,
  "net_amount": 70.42,
  "paid": true,
  "payment_method": "Card",
  "publish_to": "Xero",
  "published": false,
  "note": null
}
```

### get_item_history

Audit trail of one item: submission, field changes, publishing, approval and archiving. Access: read. REST: `GET /api/v1/dext/items/{item_id}/history`. MCP: `dext_read → get_item_history`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_id` | string | yes | Item ID from list_items. |

Returns the History tab of an item. Each entry has the time, the user or source and what changed. Use it to see who published an item before you unarchive it.

Example response:

```json
{
  "history": [
    {
      "at": "2026-10-09T08:14:00Z",
      "by": "Email upload",
      "action": "submitted"
    },
    {
      "at": "2026-10-09T08:16:00Z",
      "by": "Dext",
      "action": "extracted"
    },
    {
      "at": "2026-10-09T09:02:00Z",
      "by": "Dana Reyes",
      "action": "changed total_amount from 74.5 to 84.5"
    }
  ]
}
```

### export_items

Export items from an inbox or the Archive as CSV, PDF or ZIP and get a download link. Access: read. REST: `GET /api/v1/dext/items/export`. MCP: `dext_read → export_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `inbox` | enum | no | costs or sales. Default: costs. |
| `format` | enum | yes | csv, pdf or zip. |
| `item_ids` | string[] | no | Items to export. Omit to use the filters below. |
| `location` | enum | no | inbox or archive. Default: inbox. |
| `date_from` | date | no | Only items dated on or after this date. |
| `date_to` | date | no | Only items dated on or before this date. |

Exports the chosen items, or every item matching the filter. PDF holds up to 250 items; ZIP suits large batches and includes the original files. Dext can archive items after an export, depending on the Archiving settings in Business settings.

Example response:

```json
{
  "export_id": "ex_5120",
  "format": "csv",
  "items": 41,
  "download_url": "https://files.cotlet.dev/exports/ex_5120.csv"
}
```

### upload_document

Upload a receipt, bill or sales invoice to the Costs or Sales inbox. Access: write. REST: `POST /api/v1/dext/documents`. MCP: `dext_write → upload_document`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `inbox` | enum | no | costs or sales. Default: costs. |
| `file_url` | string | yes | HTTPS link to the file Cotlet downloads. |
| `document_owner` | string | no | Owner ID from list_document_owners, or none. Default: none. |
| `mode` | enum | no | one_per_file, one_per_page or auto_split. Default: one_per_file. |

Uploads one file through Add documents and returns the new item in Processing. Images and PDFs may be up to 6MB, ZIP files 100MB. Mode one_per_file takes PDF, JPG, PNG or ZIP; one_per_page and auto_split take PDF only. The upload reaches no one and the item can be archived, so it runs without asking.

Example response:

```json
{
  "item_id": "it_7f3b02",
  "inbox": "costs",
  "status": "processing",
  "document_owner": "Dana Reyes"
}
```

### update_item

Change extracted fields of an item, such as supplier, category, date or total. Access: write. REST: `PATCH /api/v1/dext/items/{item_id}`. MCP: `dext_write → update_item`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_id` | string | yes | Item ID from list_items. |
| `supplier` | string | no | Supplier or customer name. |
| `category` | string | no | Category name as in Dext. |
| `date` | date | no | Document date. |
| `document_reference` | string | no | Invoice or receipt number. |
| `description` | string | no | Item description. |
| `total_amount` | number | no | Total amount including tax. |
| `tax_amount` | number | no | Tax amount. |
| `paid` | boolean | no | Paid toggle. |
| `payment_method` | string | no | Payment method name as in Dext. |
| `publish_to` | string | no | Publish destination, a connected accounting software. |

Updates the fields you pass and leaves the rest. Dext moves an item to Ready once Category, Supplier and Total amount are filled. The change reaches no one and is undone with another update, so it runs without asking.

Example response:

```json
{
  "item_id": "it_7f3a10",
  "status": "ready",
  "category": "Office supplies",
  "supplier": "Staples Inc",
  "total_amount": 84.5
}
```

### publish_items

Publish Ready items to the connected accounting software. Access: write, asks the user first. REST: `POST /api/v1/dext/items/publish`. MCP: `dext_write → publish_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_ids` | string[] | yes | Item IDs from list_items. |
| `publish_to` | string | no | Destination. Default: the item's Publish to. |
| `publish_as` | string | no | Xero only: the status to publish as, one of those Dext offers. |

Sends the extracted data and the document image of each item to its destination, where it appears within a few seconds. Only Ready items publish; others come back with the missing field. Needs the Admin role or publishing permission. Dext archives published items by default. Failed items return the publishing error. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "published": [
    {
      "item_id": "it_7f3a11",
      "publish_to": "Xero",
      "publish_as": "draft"
    }
  ],
  "failed": [],
  "skipped": [
    {
      "item_id": "it_7f3a10",
      "reason": "missing category"
    }
  ]
}
```

### archive_items

Move items from the Inbox to the Archive. Access: write. REST: `POST /api/v1/dext/items/archive`. MCP: `dext_write → archive_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_ids` | string[] | yes | Item IDs from list_items. |

Archives the items, in bulk. The call reaches no one and is undone with unarchive_items, so it runs without asking.

Example response:

```json
{
  "archived": [
    "it_7f3a11",
    "it_7f3a12"
  ]
}
```

### unarchive_items

Move items from the Archive back to the Inbox, optionally clearing publishing data. Access: write, asks the user first. REST: `POST /api/v1/dext/items/unarchive`. MCP: `dext_write → unarchive_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_ids` | string[] | yes | Item IDs from list_items. |
| `clear_publishing_data` | boolean | no | true allows republishing. Default: false. |

Returns items to the Inbox. With clear_publishing_data true, an already published item can be published again as a new transaction, which may create a duplicate in the accounting software. With false the item cannot be published again and shows a publishing error. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "unarchived": [
    "it_7f2e90"
  ],
  "clear_publishing_data": false
}
```

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

Connecting Dext takes three steps: sign up, sign in to Dext once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Dext to your agent.

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

2. **Sign in to Dext in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Dext there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Dext 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.

```
Upload these PDFs and JPGs to the Dext Costs inbox with me as document owner, then tell me which items landed in To review.
```

### Call Dext from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/dext with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/dext/items/publish \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"item_ids":["it_7f3a11","it_7f3a12"],"publish_to":"Xero","publish_as":"draft"}'
```

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

```
{
  "published": [
    {
      "item_id": "it_7f3a11",
      "publish_to": "Xero",
      "publish_as": "draft"
    },
    {
      "item_id": "it_7f3a12",
      "publish_to": "Xero",
      "publish_as": "draft"
    }
  ],
  "failed": [],
  "skipped": []
}
```

## Why use Cotlet for Dext?

**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 Dext yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

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

## Is it safe to connect Dext to Cotlet?

Yes. You sign in to Dext yourself, in your own Cloud Browser, and we never save your password. Your agents only get Dext once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Dext integration?**

No, Cotlet is independent of Dext. Dext has no public API. Cotlet works through your own Dext account, the way you use Dext in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Dext in your console: your agents lose access at once and you stay signed in. Signing out of Dext in the browser works too, and Reset browser deletes the whole profile.

## Is there a Dext MCP server on GitHub?

No open-source Dext MCP server turned up. The realistic option is Zapier: its Dext app submits receipts and sales invoices and sends processed receipt data out. It cannot review, edit, publish, archive or export items. Cotlet covers those steps in your own Dext account, with one key.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect Dext to Zapier, build a Zap per task | Sign up, sign in to Dext once, add one MCP server or API key |
| What it does in Dext | Submit receipts and sales invoices, read processed receipts, create a client account | Upload, list, edit extracted fields, publish, archive, unarchive and export |
| When Dext changes | Zapier maintains the app; only the actions it offers work | Our team tests it daily and fixes it for you; failed calls are free |
| Your Dext session | Zapier connection to your account | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | The Zap fails until you reconnect | Your Cloud Browser keeps you signed in; if Dext logs you out, your agent gets a link to sign in again |
| Where it runs | Zapier, on triggers and schedules | Hosted: Claude Code, Codex, Cursor, n8n, Zapier and scripts, also on a schedule |
| Price | Zapier plan; only successful actions count as tasks | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Dext changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Dext API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Dext API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

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

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Dext yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Dext only after you enable it. When Dext signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Dext, sign out of Dext in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Dext's terms:** You use your own Dext account and stay responsible for following Dext's terms. Cotlet is independent and not affiliated with Dext. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Dext in the console and press Request access. Then you create your API key and connect Dext there.

**Do I need to be technical?**

No. You sign in to Dext once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Dext to Cotlet?**

Yes. You sign in to Dext yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Dext once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Dext sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Dext cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Dext's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Dext sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Dext login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Dext offers no OAuth or API for this, so there is no scoped token to hold. That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a special Dext plan or role to publish?**

Publishing needs the Admin role, or a publishing permission from an administrator. Cotlet works in your own Dext account, so it can do what that user can.

**Can my agent publish items twice by mistake?**

No by default. publish_items skips items that are not Ready and does not retry failures. Dext itself warns that unarchiving with cleared publishing data may create a duplicate in the accounting software, so unarchive_items asks for your OK.

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

No. Every call to publish_items or unarchive_items waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. upload_document, update_item, archive_items runs without asking, because it sends nothing to anyone and one call undoes it.

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

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/dext from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.