Get started
Cotlet gives your agent and your scripts an API for apps that never built one. One key works across every app on your account, over MCP or REST.
Choose how you connect
Quickstart
- 1
Sign up. Create your account on the sign-up page, then add your apps and create your API key in the console.
- 2
Sign in to your app. Open your Cloud Browser in the console, your own Chrome in the cloud. Sign in to the app there yourself and press Enable for agents. We never save your password.
- 3
Make your first call. Add the MCP server to your agent, or call the REST endpoint from a script.
curl https://cotlet.dev/api/v1/skool/groups/yourgroup/members \
-H "Authorization: Bearer $COTLET_API_KEY" claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" from cotlet import Cotlet
client = Cotlet() # reads COTLET_API_KEY
members = client.call("skool", "list_members", {"group": "yourgroup"}) import { Cotlet } from 'cotlet';
const cotlet = new Cotlet(); // reads COTLET_API_KEY
const members = await cotlet.call('skool', 'list_members', { group: 'yourgroup' }); Base URLs
| Interface | URL | Use it for |
|---|---|---|
| REST API | https://cotlet.dev/api/v1 | Scripts, backends, n8n HTTP nodes |
| MCP server | https://cotlet.dev/mcp/v1 | AI agents and MCP clients |
Authentication
Every call carries your API key as a bearer token. Scope each key to the apps and tools it needs, read only or read and write, and give each agent or script its own key. Actions that reach other people wait for your approval by default, so a leaked key cannot post or message as you.
Authorization: Bearer COTLET_API_KEY - Listing apps, endpoints and schemas needs no key.
- Keep the key in an environment variable such as
COTLET_API_KEY, never in code you commit. - Every call is in your activity log. Rotate or revoke keys in your dashboard at any time.
Key concepts
| Concept | What it means |
|---|---|
| App | A product without a usable API, such as Skool or Booksy. Each has a slug: skool, booksy. |
| Endpoint | One action in an app, such as list_members at GET /api/v1/skool/groups/{group}/members. Over MCP the app has a read tool, skool_read, and a write tool, skool_write; the action is the operation list_members of skool_read. |
| Access | read endpoints only read data; write endpoints change something in the app. |
| Confirm | Endpoints that reach other people (posts, messages, emails) wait for your OK by default. You can switch that off per endpoint. |
| Cloud Browser | Your own Chrome in the cloud, one per app you sign in to, on a residential IP in the country you choose. You sign in to your apps there; its profile is stored encrypted. |
| Connected account | An app you signed in to in your Cloud Browser and enabled for agents, read only or read and write. Calls run as you, with your permissions. |
| Credits | Each successful call uses credits; failed calls are free. See pricing. |
For AI agents
Agents can explore Cotlet without an account. Everything below answers without a key.
- Every app and endpoint as JSON:
GET https://cotlet.dev/api/v1/apps. - Every app as one MCP tool with its operations:
tools/liston the MCP server. - A summary of the site for agents: /llms.txt.
- Every page as Markdown: send
Accept: text/markdown, or add.mdto the URL.
App missing? Ask for it without an account (10 requests an hour):
curl -X POST https://cotlet.dev/api/v1/integration-requests \
-H "Content-Type: application/json" \
-d '{"app": "Notion", "use_case": "what you want done"}'