Descanto Docs

Developer portal

Everything you need to build on Descanto — API keys, quickstart, API reference, SDKs, CLI, MCP server, and a self-hosted sandbox.

This page is the front door for building on Descanto: where to get credentials, where every developer resource lives, and how to try the platform before you wire it into anything real.

Get API keys

Descanto is in early access, so keys are provisioned per organization:

  1. Request access — tell us your use case and preferred tier.
  2. Once onboarded, sign in and create a key with descanto login or POST /v1/keys (API keys reference).
  3. Keys look like canto_sk_... and are org-scoped: a key only ever sees its own organization's desktops. See Orgs and auth.

Descanto documentation

Descanto tools and clients

  • OpenAPI spec — machine-readable contract at descanto.com/openapi.json (also served live at GET /v1/openapi.json).
  • TypeScript SDKnpm install @descanto/sdk.
  • Python SDKpip install descanto-vm, sync and async.
  • CLInpm install -g @descanto/cli, then descanto --help.
  • MCP servernpx -y @descanto/mcp: drive desktops from Claude Code, Claude Desktop, Cursor, or any MCP client.
  • llms.txt — the agent-facing guide at descanto.com/llms.txt, including when-to-use guidance and markdown content negotiation.

Sandbox

Two ways to experiment without touching production quota:

  • Self-hosting — run the whole stack (controld + hostd) locally or on your own hardware; the API surface is identical, so anything you build against a self-hosted instance works unchanged against the hosted platform.
  • Fork-and-discardfork a desktop, experiment destructively on the copy, and destroy it; the parent is never touched.

Support

Questions, bug reports, or a fleet to size: [email protected], the contact form, or GitHub.

On this page