CLOUSD
Open account
Cloud PhonesDevicesCloud Android phones for your agentsObservabilityWatch the agent live: screen, screenshots, UI treeRegionsDevices online in 45 countries
For DevelopersVirtual AssistantSoonNo-code assistant that runs phone tasks for youAI Agents & MCPHosted MCP and SDK for Claude, Codex and Cursor
Open SourcePython SDKScript devices and agents in a few linesMCP ServerOne command to plug devices into any MCP clientAgent SkillTeach your coding agent to run phones
Start Free Trial
Built ForAI Agent BuildersA real phone for every agent or userAI EmployeesA work phone for every AI workerQA TeamsTest your app on the phones people actually own
IndustryCommercePrices, promos and checkout per marketGamingTest builds and evaluate game agentsIT & SecurityPentest apps on real phone modelsComplianceWhat apps show users in each country
See All Use Cases
LearnBenchmarkSoonHow agents score on Clousd phonesBlogSoonGuides, deep dives and field notesCompareSoonClousd next to the alternatives
BuildIntegrationsSoonMCP, Claude Code, Codex, Cursor, n8nGitHubSDK, MCP server and examples
HelpServer StatusLive checks with 90 days of historyContact SupportA person answers within a working day
Read the Docs

Get started

API keys

One key opens the REST API, the Python SDK and the MCP server.

Base URL and header

Every request
# base URL
https://api.clousd.com/v1

# header
Authorization: Bearer cl_live_••••••••

Create a key

Open API & MCP in the dashboard. One click creates a key with control over all your phones, ready for an AI agent, and shows the lines to paste into Claude Code, Codex, Cursor and other clients. The key is shown once.

Scope and devices

Each key has a scope and a list of devices:

ScopeWhat it can do
readList devices, take screenshots, observe the screen, read jobs. Any call that changes something answers 403.
controlEverything above, plus start, stop, install apps, act on the screen and run group jobs.

A key covers either all phones of the account or a list you choose. A phone outside the list answers 404, as if it did not exist.

Revoke a key

Revoking a key stops it at once, for every client that uses it. Keys belong to the account, not to a person, so they keep working when a teammate leaves.

Team

An account has owners and operators. Owners handle billing, API keys, the team, and creating or deleting devices. Operators run the devices assigned to them, without billing, keys or deletion.