# NoClick

> NoClick is an assistant you text. Message it on WhatsApp or iMessage, email it, call it or use the web chat, and it builds and runs what you ask for: websites and apps, AI agents that work in your connected accounts, automations, phone numbers and calls, domains and inboxes. It asks before it buys anything. Developers get the same pieces as an API, with Python and TypeScript SDKs, a CLI and an MCP server. Every service costs what its provider charges NoClick; the plan's only margin is a fee when you add funds.

NoClick has two sides, on one account and one balance:

- **The assistant, for anyone.** Text NoClick on [WhatsApp](https://wa.me/14242421064) (+14242421064) or iMessage (+16126493126): the first text makes an account, with nothing to sign up for. After that you can also call it, email it at the address it gives you, or chat at https://www.noclick.com/dashboard. It builds and publishes websites, buys a domain or a phone number once you approve the price, places calls for you and sends back the recording, builds agents and automations that run on schedules and app events in the accounts you connect (144+ apps, from Gmail and Slack to Stripe), reports back, reminds you, and looks into runs that fail.
- **The platform, for developers and their coding agents.** The same pieces through the API at https://api.noclick.com (every path under `/v1`, authenticated with a bearer `nk_live_` key), the SDKs (`pip install noclick`, `npm install noclick`), the `noclick` CLI and the MCP server at https://mcp.noclick.com. Run hosted agents for your own users, in their connected accounts, with phone numbers, inboxes, domains, apps, databases and storage, and see every operation and dollar per user. Start with the [Introduction](https://www.noclick.com/docs/guide/intro) and [Getting started](https://www.noclick.com/docs/guide/getting-started).

**Pricing.** Every service (AI models, phone numbers and calls, domains, email, sandboxes and the rest) costs exactly what its provider charges NoClick, through the API too. The one margin is a fee added when you add funds to your balance: 15% on Free ($0, with $1 of usage included a day, up to $5 a month) and 5% on Member ($25 a month, with $10 of usage included and no NoClick branding). Work run on your own model key or ChatGPT or Claude subscription carries no fee. Buying a phone number or a domain needs a $5 balance from funds you added. Prices for each service: https://www.noclick.com/pricing.

**Give a coding agent a key without showing it the key.** In the [developer console](https://www.noclick.com/dashboard/developers), Quickstart's prompt carries a one-time setup code (good for 30 minutes), and the agent's one command writes a new key straight into the project's `.env` ([API keys and scopes](https://www.noclick.com/docs/guide/keys)):

```bash
curl -fsS -X POST https://api.noclick.com/v1/setup -d code=nc_setup_... >> .env
```

**Connect an MCP client** (Claude, ChatGPT, Cursor, Codex) to `https://mcp.noclick.com` over Streamable HTTP, signing in with OAuth or sending `Authorization: Bearer nk_live_...`. In Claude Code: `claude mcp add --transport http noclick https://mcp.noclick.com`, then `/mcp` to sign in ([The NoClick MCP server](https://www.noclick.com/docs/guide/mcp)).

Anything marked invite-only beta answers 404 or `not_available` until NoClick grants access (ask support@noclick.com).

## Guide: Get started

- [Introduction](https://www.noclick.com/docs/guide/intro): Everything your AI product runs on, through one SDK and priced at cost: agents, your users' accounts, phone numbers, inboxes, domains, apps, databases and storage.
- [Getting started](https://www.noclick.com/docs/guide/getting-started): Create a key, install the SDK and make your first calls.

## Guide: Your users

- [Users](https://www.noclick.com/docs/guide/users): A user is someone your product acts for. Everything you do for them is scoped to them.
- [Sessions for the browser](https://www.noclick.com/docs/guide/sessions): Give your frontend a short-lived token that acts as one user, so your secret key never leaves your server.
- [Brand](https://www.noclick.com/docs/guide/brand): Show your product's name, logo and colour on the pages and emails NoClick sends your users.

## Guide: Their accounts

- [Connections](https://www.noclick.com/docs/guide/connections): Name each account your code and agents act in, let your users connect it once, and use it by name.
- [Calling integrations](https://www.noclick.com/docs/guide/integrations): Find a service, see what it can do, and run its operations, including the ones that need no account and no connection.

## Guide: Hosted agents

- [Agents](https://www.noclick.com/docs/guide/agents): Create a hosted agent in one call, give it your users' connections, and message it.
- [Triggers and automations](https://www.noclick.com/docs/guide/triggers): Wake an agent on a webhook, an app event, one of NoClick's own events, a schedule (as an automation) or each message on a queue.
- [Memory and files](https://www.noclick.com/docs/guide/memory): Give an agent a memory it keeps across conversations, share memories between agents, and give it files it works on in each one.
- [Sharing and streaming](https://www.noclick.com/docs/guide/sharing): Share an agent at a public link, stream its turn live into your own UI, and follow a conversation as it moves.
- [Test runs](https://www.noclick.com/docs/guide/testing): Rehearse an agent against a simulated world: real turns, no side effects.
- [Letting agents ask for connections](https://www.noclick.com/docs/guide/grants): Let an agent ask its user to connect the accounts it turns out to need, within limits your code sets.
- [Coordinators and sub-agents](https://www.noclick.com/docs/guide/sub-agents): Let one agent spawn others, hear from them when it must, ask them anything without stopping them, and let agents outside NoClick talk to yours.
- [Channels](https://www.noclick.com/docs/guide/channels): Put agents, your user and agents from elsewhere in one room, with hard stops on turns and spend.
- [Workspaces](https://www.noclick.com/docs/guide/workspaces): Group channels, agents and your users into workspaces, each with its own members, subscriptions and monthly spend cap.

## Guide: Tools for your own LLM

- [Toolkits](https://www.noclick.com/docs/guide/toolkits): Give your own LLM calls tools that run in your users' connected accounts, plus web search, page fetching and a code sandbox.
- [Hosted MCP servers](https://www.noclick.com/docs/guide/mcp-servers): Put your tools at one URL for Claude, ChatGPT, Cursor or any MCP client.
- [AI models](https://www.noclick.com/docs/guide/ai): Chat, embeddings, images, videos and transcription paid from your NoClick balance, an OpenAI-compatible endpoint, and your agents as models.
- [The NoClick MCP server](https://www.noclick.com/docs/guide/mcp): Let Claude, ChatGPT, Cursor or any MCP client build on the platform, signed in with OAuth or with a platform key.
- [The workflow MCP server](https://www.noclick.com/docs/guide/workflow-mcp): Edit a workflow node by node from an MCP client connected to the app's own server, or from an agent inside a workflow with the NoClick node.

## Guide: People in the loop

- [Asking people](https://www.noclick.com/docs/guide/humans): Ask a person a question, get their approval or send them a notice, then wait for the answer.
- [Policy and approvals](https://www.noclick.com/docs/guide/policy): Decide which tools may run, which never may, and which need a person to say yes first.

## Guide: Acting in the world

- [Inboxes](https://www.noclick.com/docs/guide/inboxes): Give your code or an agent its own email address, read what arrives, reply, and write new mail from your own domain.
- [Phone numbers](https://www.noclick.com/docs/guide/phone-numbers): Buy a real phone number or bring your own, have an agent answer its calls, and have it call people with a goal.
- [Browsers](https://www.noclick.com/docs/guide/browser): Give an agent a browser, and keep a person's logins in a profile it can use.
- [Cards](https://www.noclick.com/docs/guide/cards): Virtual cards with limits and approvals, for agents that buy things. (invite-only beta)
- [Sandboxes](https://www.noclick.com/docs/guide/sandboxes): Start an isolated Linux machine, run commands and move files in and out, billed by the second.
- [Machines](https://www.noclick.com/docs/guide/machines): Run agents on an always-on machine at a flat monthly price, instead of a sandbox per conversation.

## Guide: Build and host

- [Apps and deployments](https://www.noclick.com/docs/guide/apps): Deploy a repo to a URL, with previews, bindings, secrets, schedules, logs and traffic.
- [Code repos](https://www.noclick.com/docs/guide/repos): Git repositories your code and agents commit to, with plain git access and export to GitHub.
- [Email, payments and sign-in](https://www.noclick.com/docs/guide/app-services): Transactional email, payments and sign-in for an app, without accounts of your own.
- [Domains](https://www.noclick.com/docs/guide/domains): Buy a domain in your user's name, connect one they own or transfer it in, and point it at an app or an inbox.
- [Workflows](https://www.noclick.com/docs/guide/workflows): Build workflows from a description, read them in full, run, pause and publish them, or give them an endpoint.

## Guide: Data

- [Databases](https://www.noclick.com/docs/guide/databases): A SQL database for an app or an agent. SQLite by default, Postgres when you outgrow it, with migrations, restores and branches.
- [Storage](https://www.noclick.com/docs/guide/storage): Buckets of files by key, private by default, with signed links, public URLs and S3-compatible access.
- [Volumes](https://www.noclick.com/docs/guide/volumes): A persistent filesystem you mount into sandboxes and agents, for datasets, caches and build output.
- [Dicts](https://www.noclick.com/docs/guide/dicts): A key-value store for small shared state, what has been seen, counters, locks and caches with expiry, that reads like a Python dict.
- [Queues](https://www.noclick.com/docs/guide/queues): Durable background work between your code, workers and agents, delivered at least once, with retries and dead letters.
- [Secrets](https://www.noclick.com/docs/guide/secrets): Named environment values, like API keys, for the code your sandboxes, agents and apps run.

## Guide: In production

- [Operations](https://www.noclick.com/docs/guide/operations): Anything that waits on the world returns an operation. Block on it, poll it, or come back to it by id.
- [Undo and the trash](https://www.noclick.com/docs/guide/undo): Deleting an app or a resource moves it to the trash for 30 days, a reversible write records its undo, and a dict, a secret or a setting keeps what it held. Only purging is permanent.
- [Activity](https://www.noclick.com/docs/guide/activity): Read back everything done with your account, from operations and tool calls to API requests, across every user.
- [Webhooks and events](https://www.noclick.com/docs/guide/webhooks): Get every event that matters delivered to your server, signed, with retries.
- [Spend and limits](https://www.noclick.com/docs/guide/spend): See what your account spends per user, key and agent, cap each of them, and charge your users for theirs.
- [Regions](https://www.noclick.com/docs/guide/regions): Choose where sandboxes and agents run, set your account's default, and keep resources together.
- [Errors and retries](https://www.noclick.com/docs/guide/errors): Every failure is a typed error that says what to do next. Transient ones are retried for you, safely.
- [Export](https://www.noclick.com/docs/guide/export): Pack up everything a user or an app holds, in formats that work elsewhere.

## Guide: SDK and API

- [API keys and scopes](https://www.noclick.com/docs/guide/keys): Create keys with only the access they need, pin them to a user, and cap what they spend.
- [Access for AI agents](https://www.noclick.com/docs/guide/agent-access): How an AI agent gets a NoClick key, by signing itself up or from a person, and what it can do before a person claims its account.
- [Async and concurrency](https://www.noclick.com/docs/guide/async): Every method is also awaitable, and the user you act for follows your code across tasks and threads.
- [The HTTP API](https://www.noclick.com/docs/guide/http-api): Call the platform from any language. The SDKs are thin clients over these conventions.
- [The CLI](https://www.noclick.com/docs/guide/cli): Sign in, chat with agents, query databases, copy files, deploy apps, buy domains and forward webhooks from your terminal.

## Examples

- [All examples](https://www.noclick.com/docs/examples): Complete programs you can run. Each one is also a guide: read it top to bottom, then run it.
- [An assistant for every user, in their own Gmail and Calendar](https://www.noclick.com/docs/examples/assistant-for-every-user): A web app where each of your users connects their own Gmail and Google Calendar and gets an assistant that works only in their accounts, under a monthly spending cap.
- [One support agent for chat, email and phone](https://www.noclick.com/docs/examples/support-agent): One support agent on your site's chat, your support email address and a phone number, answering from your help center, looking up the customer's own orders in Stripe, and asking your team before large refunds.
- [An accounts-payable clerk with its own inbox](https://www.noclick.com/docs/examples/accounts-payable-inbox): An accounts-payable clerk with its own email address that checks each vendor invoice against QuickBooks, gets a person's approval over a limit, pays with a single-use card and replies to the vendor. (uses invite-only beta APIs)
- [An AI receptionist on a real phone number](https://www.noclick.com/docs/examples/phone-receptionist): A real phone number that answers like a front desk, books into the business's Google Calendar, texts callers their confirmation and puts the hard calls through to the owner. (uses invite-only beta APIs)
- [Turn labelled GitHub issues into pull requests](https://www.noclick.com/docs/examples/issue-to-pull-request): Label a GitHub issue `agent` and Claude Code reproduces the bug, fixes it, runs your tests and opens a pull request.
- [Describe an app, get a live URL](https://www.noclick.com/docs/examples/prompt-to-deployed-app): Your users describe an app, a Codex agent builds it, and it goes live on your domain with the database, email and payments it asks for.
- [Ask your sales calls anything](https://www.noclick.com/docs/examples/sales-call-search): Turn a folder of sales-call recordings into something you can ask, answered with quotes, timestamps and a link to the moment.

## Reference and changelog

- [Python SDK reference](https://www.noclick.com/docs/reference/python): Every class, method and error in the noclick package (pip install noclick).
- [TypeScript SDK reference](https://www.noclick.com/docs/reference/typescript): The same reference in TypeScript (npm install noclick); Node 20+, Deno, Bun and browsers.
- [Changelog](https://www.noclick.com/docs/changelog): What changed in NoClick: the SDK, the API and the app, newest first.
- [Changelog feed](https://www.noclick.com/docs/changelog/feed.xml): The changelog as an Atom feed.

## Product

- [Pricing](https://www.noclick.com/pricing): The two plans, Free and Member, and every service's price.
- [Integrations](https://www.noclick.com/integrations): The 144+ apps NoClick connects to, each with its operations.
- [Agents](https://www.noclick.com/agents): Agents on Claude Code, Codex, OpenCode, OpenClaw or Hermes, with your apps as tools.
- [Templates](https://www.noclick.com/templates): Ready-to-run agents for sales, support, marketing and ops.
- [MCP servers from your apps](https://www.noclick.com/mcp): Turn the apps you connect into an MCP server for Claude, Cursor or any MCP client.
- [Support](https://www.noclick.com/support): Email support@noclick.com, the docs, service status, privacy requests and security reports.

## Optional

- [Full text](https://www.noclick.com/llms-full.txt): This index followed by every guide page and example in full, as Markdown.
- [Developer Terms](https://www.noclick.com/legal/developer-terms): NoClick's Developer Terms: the agreement for building on the NoClick Platform, its API, SDKs, MCP server and developer console.
- [Acceptable Use Policy](https://www.noclick.com/legal/acceptable-use): What you, your users and your agents may not do with the NoClick Platform.
- [Domain Registration Agreement](https://www.noclick.com/legal/domain-registration): The agreement for a domain name registered through NoClick, which resells registration from Name.com.
- [Subprocessors](https://www.noclick.com/legal/subprocessors): The companies NoClick uses to run its service and process customer data, and what each one does.
- [Privacy Policy](https://www.noclick.com/privacy-policy)
- [Terms of Service](https://www.noclick.com/terms-of-service)