Masky Docs

Make avatars, images, videos and conversations from your own code or your AI assistant. Pick a guide, or scroll down to generate an API key.

API referenceEvery HTTP endpoint: auth, images, videos, avatars, conversations, brains and email. curl quickstartCopy-paste commands and worked examples from a shell. MCP serverMasky as native tools in Claude and other MCP clients. Login with MaskyOAuth 2.0 sign-in for your site, with avatar identities. Agent skillThe entry point an AI assistant reads first.

Basic Setup

The fastest way in — no install. Point your agent at the Masky agent skill — a markdown entry point that teaches any capable AI (Claude, or anything with a shell or HTTP tool) how to get a key and routes it to the right guide: the full API reference, a curl quickstart, MCP setup, or the “Login with Masky” SSO guide. Those links are the markdown your agent reads; the cards above are the same guides for you. Paste a URL into your prompt, or drop the file in your project, then ask it to make avatars, conversations, and images, or to add “Login with Masky” to your site. Endpoint reference also at /api/docs.

Set up Masky in Claude (MCP)

One-time setup, about 30 seconds. The Masky MCP server exposes your avatars, image generation, conversations, turn rendering, and SSO app registration as tools Claude can call directly — in Claude Code, Claude Desktop, or the Anthropic API.

1. Generate a key. Sign in, then click Generate key below and copy the mky_… token — it's shown only once.

2. Add Masky with one command. The hosted endpoint at https://masky.ai/api/mcp needs nothing installed — in your terminal, drop your token into:

claude mcp add --transport http masky https://masky.ai/api/mcp --header "Authorization: Bearer mky_YOURKEY"

That's the whole install — no file editing, no npx. The next time you start Claude Code, the Masky tools are loaded. Any other remote-capable MCP client works the same way: point it at https://masky.ai/api/mcp (streamable HTTP) and send Authorization: Bearer mky_YOURKEY.

Prefer a local process (or your client can't send auth headers)? The same tools ship as the masky-mcp-server npm package:

claude mcp add masky -e MASKY_API_KEY=mky_YOURKEY -- npx -y masky-mcp-server

On Claude Desktop there's no CLI: open Settings → Developer → Edit Config, add this entry inside mcpServers, then quit and reopen the app:

"masky": {
  "command": "npx",
  "args": ["-y", "masky-mcp-server"],
  "env": { "MASKY_API_KEY": "mky_YOURKEY" }
}

3. Prompt it. "Use Masky to make a two-avatar podcast where a startup founder pitches a skeptical engineer — give me the embeddable live URL."

Masky API keys

Long-lived bearer tokens for the public Masky HTTP API and the Masky MCP server. Keep keys secret — anyone with one acts as you.

Use it directly (HTTP API)

Prefer raw HTTP? Authenticate with Authorization: Bearer mky_.... Every endpoint is in the API reference.

curl -X POST https://masky.ai/api/conversations \
  -H "Authorization: Bearer $MASKY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"avatarOwnerUserId":"twitch:12345","avatarId":"abc"}'