Scenema API

The Scenema API lets you drive the Studio from scripts, CI pipelines, MCP clients, and any HTTP-capable tool. Every generation the Studio can run is available through the API on the same billing account. Credits, entitlements, and plan limits behave identically to the in-app surface.

This guide covers the current REST surface, authentication with API keys, rate limits, and error handling. When MCP ships you will see it slot in alongside the REST section without breaking anything you build against the current API.

What you can do today

• Mint, list, disable, and revoke API keys from the Settings surface.
• Authenticate any HTTP request with a personal Bearer token.
• Read a JSON response for every endpoint the Studio uses.
• Receive proper HTTP status codes for auth failures, rate limits, and plan gates so your client’s default backoff logic works out of the box.

Base URL

Quick example

curl -H "Authorization: Bearer sk_your_key_here" \
  https://scenema.ai/api/service/user/api-keys

Response:

{
  "keys": [
    {
      "id": "...",
      "name": "MCP client",
      "start": "sk_abcd",
      "enabled": true,
      "createdAt": "2026-09-24T19:41:32.449Z",
      "expiresAt": null,
      "lastRequest": "2026-09-24T19:56:39.182Z",
      "requestCount": 42
    }
  ]
}

Plan tiers and API access

Every plan includes API access, including Free. Rate limits scale with the plan. See Rate Limits for the ceiling per tier.

What’s coming

MCP integration lands as a first-class client for Claude Desktop, ChatGPT, and Meta Muse. The MCP tools expose the same Studio actions the REST API does, framed for AI assistants. When it ships the MCP Integration page fills out with setup guides for each client.