Skip to content

DocsDevelopers

Developer overview

The API, the MCP server and the CLI, and which one to use.

Three ways to drive loudscene from code, all with the same API key and the same credits: the REST API, the MCP server for AI agents, and the loudscene command line. They are part of the Agency plan.

Which one to use#

REST APIJSON over HTTPS: extract brands, create videos, patch fields, render MP4s, get webhooks.MCP serverLet Claude, Cursor and other agents make and render videos for you.CLILog in once, then create, render and download from your terminal or CI.WebhooksSigned events when videos are generated and renders finish.

Quick start#

  1. 1

    Create a key

    In the app, open Settings → API keys and create a key named after where it will run. Copy it: it is shown once.

  2. 2

    Make a video from a website

    curl
    curl https://www.loudscene.com/api/v1/videos \
  -H "Authorization: Bearer $LOUDSCENE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"url":"https://yourbrand.com","brief":"We just launched v2: twice as fast.","format":"9:16"}'
  3. 3

    Wait for it

    The answer has status: "generating". Subscribe to the video.generated webhook, or poll GET /v1/videos/:id.

  4. 4

    Render

    Call POST /v1/videos/:id/renders with a format, then read the MP4 URL from GET /v1/renders/:id or the render.completed webhook.

OpenAPI#

The full contract is an OpenAPI 3.1 document at /api/v1/openapi.json, generated from the same schemas the server validates with. Point your client generator at it.