Developer Platform Overview

SketricGen exposes three developer surfaces. Choose the surface based on whether an AI assistant should manage SketricGen, your software should manage SketricGen resources, or your application should run an agent. A single Teamspace API key can carry runtime access, management access, or both.

Choose the right integration

Surface	Use it when	Authentication	What it controls
MCP server	Claude, ChatGPT, Codex, or another MCP client should build and manage Brand Agents conversationally	SketricGen OAuth or an API key with Manage resources access	Brand Agent creation and editing, templates, knowledge bases, widget configuration, and connectors
Admin API	Your backend, CLI, or automation should manage Teamspace resources directly	API key with Manage resources access, beginning with `sk_api_`	Projects, agents, Brand Agents, knowledge bases, conversations, traces, members, usage, and connectors
Runtime API	Your application should send a message to an existing agent and receive its response	API key with Run agents access, beginning with `sk_api_`	Agent execution through `POST /api/v1/run-workflow`
Python and Node.js SDKs	You want a typed client for the Runtime API	API key with Run agents access, beginning with `sk_api_`	Agent execution, streaming, and supported file uploads

How the surfaces fit together

AI assistant or MCP client
        |
        | Streamable HTTP + OAuth or sk_api_ key with Manage resources
        v
SketricGen MCP server
        |
        | Calls the same authorized control plane
        v
SketricGen Admin API  <----- Your backend, CLI, or automation

Your product, website, or backend
        |
        | API-KEY: sk_api_... with Run agents
        v
SketricGen Runtime API -----> Existing agent run and streamed response

The MCP server is an AI-friendly adapter over the Admin API. It does not bypass Teamspace roles, project boundaries, plan limits, or connector permissions. The Runtime API and Admin API remain separate endpoints, but their permissions are capabilities on the same API-key entity. A key can have Run agents, Manage resources, or both. A key without Run agents cannot execute an agent, and a key without Manage resources cannot create, edit, or delete Teamspace resources.

Start here

Connect an AI assistant with the SketricGen MCP guide.
Manage resources programmatically with the Admin API.
Run an existing agent with the Runtime API.
Use the Python SDK or Node.js SDK for a higher-level Runtime API client.

API key location

Create API keys from the active Teamspace:

Open Teamspace settings in SketricGen.
Select API keys.
Select Create key.
Enable Run agents, Manage resources, or both.
Choose the narrowest Project scope. If Run agents is enabled, add agent restrictions when needed; if Manage resources is enabled, choose a role and expiry.
Copy the plaintext sk_api_... key immediately. SketricGen shows it only once.

API key creation requires an eligible Teamspace plan and permission to manage API keys.

Security rule

Treat API keys as secrets:

Keep keys on a server or in a secret manager.
Never put a key in a public repository, screenshot, browser bundle, or prompt transcript.
Prefer OAuth for hosted MCP clients because the AI client never needs your management-capable API key.
Use a narrowly scoped key for local agents and automation.
Revoke a key from Teamspace settings when it is no longer needed.

​Choose the right integration

​How the surfaces fit together

​Start here

​API key location

​Security rule

Choose the right integration

How the surfaces fit together

Start here

API key location

Security rule