[01]API · MCP server_

Every AI model. [One] key. For your code [and] your agents.

Generate images, video and voice, AI influencers, ads and clips, from your backend over a REST API, or from Claude, Cursor and any agent through our MCP server. Every top model, billed per output.

Add to Claude in one line

Or install the SDK

35
models
1
schema
$0
failed runs
0
polling

[02]MCP server_

Give your agent a camera.

Add one URL and your assistant can search models, quote a price, start a run, wait for it and hand back the file. It uses your balance and your characters, so @mia looks the same whether you or your agent made the clip.

  1. youMake 3 vertical ads of @mia holding our new serum, voice-over in Portuguese.
  2. toolsearch_models · task=image-to-video, output=video
  3. toolestimate_cost · kling-2-1-pro × 3 · 5s · 9:16
  4. toolrun_model × 3 · character=@mia
  5. toolwait_for_task · tsk_01J9Z8K2QF, tsk_01J9Z8K3A1, tsk_01J9Z8K3C7
  6. agentDone. Three 9:16 clips with @mia, charged on success. Links below.
claude mcp add --transport http influmaker https://mcp.influmaker.com.br \
  --header "Authorization: Bearer $INFLUMAKER_KEY"
  • search_models

    Find models by task, media type or name.

  • get_model

    Read a model's inputs, price rule and samples.

  • estimate_cost

    Quote a run before it starts.

  • run_model

    Start a run. Waits up to ~45s, then returns a task handle.

  • get_task

    Read a task's status and outputs.

  • wait_for_task

    Wait on a pending task instead of running it again.

  • upload_file

    Upload a file from a URL to use as an input.

  • get_balance

    Read the workspace balance.

[03]REST API_

Run, wait, get a webhook.

Same engine as Studio. One route for every model, a task you can poll or stream, and a signed webhook when the file lands.

POST/v1/run/{owner}/{model}

Start a run on any model

One route shape for every model. Send the inputs from its schema, an optional @character and a webhook. You get a task id back right away.

  1. 1Create runPOST /v1/runs
  2. 2Check statusGET /v1/runs/{id}
  3. 3Get the resultwebhook or GET
  • ✓Price is held, charged only on success
  • ✓Same schema as the Studio form
  • ✓Idempotency-Key header supported
Request
curl https://api.influmaker.com.br/v1/run/kuaishou/kling-2-1-pro \
  -H "Authorization: Bearer $INFLUMAKER_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 6f1c0d2e" \
  -d '{
    "prompt": "walks to camera, golden hour",
    "character": "@luna",
    "duration": 5,
    "webhook_url": "https://your.app/hooks/influmaker"
  }'

Response

Press Send to see a sample response.

[04]What you can build_

A content team, behind one endpoint.

  • 01

    Content apps

    Put influencers, ads and clips inside your own product. White-label generation on one key, priced per output.

  • 02

    Marketing agents

    Let Claude or your own agent brief, generate and deliver creatives, with the same characters your team uses in Studio.

  • 03

    Clip pipelines

    Wire n8n, Zapier or Make to a channel: every new long video comes back as captioned 9:16 shorts.

  • 04

    E-commerce catalogs

    One product photo per SKU in, a UGC-style video and lifestyle shots out, for the whole catalog.

Built to not surprise you.

One schema

35 models behind one route shape. Swap Kling for Veo by changing a path.

Charged on success

The price is held while a run works and released if it fails.

Idempotent

Send an Idempotency-Key and a retry never bills twice.

Webhooks and SSE

Signed webhooks with retries, or stream a task live. No polling loops.

Characters over the API

Pass @character and the same face and voice from the app shows up.

One library

Runs from the API, MCP and Studio land in the same library and usage view.

[05]Integrations_

Plug into your stack.

Any MCP client, any automation tool, any backend that can make an HTTP call.

  • Claude Code
  • Claude Desktop
  • Cursor
  • VS Code
  • Windsurf
  • n8n
  • Zapier
  • Make
  • Webhooks
  • REST
  • TypeScript SDK
  • + Any MCP client

[06]FAQ_

Developer questions

01Does the API cost more than the app?

No. A Studio run, a Workflow node and an API call create the same task at the same price, and failed runs are never charged.

02Which MCP clients work?

Any client that speaks Streamable HTTP: Claude Code, Claude Desktop, Cursor, VS Code, Windsurf and others. Authenticate with an API key in the Authorization header.

03Can I use my characters from code?

Yes. Cast a character in the app, then pass its @handle in any run. The API sends the same reference sheet and voice.

04How do I know what a run will cost?

Call the estimate endpoint, or estimate_cost over MCP. You get the exact price before anything starts.

05Is there an SDK?

A TypeScript SDK (npm install @influmaker/sdk). The REST API works from any language that can make an HTTP call.

Ship your first render in five minutes.

Same prices as the app. Free credit on sign-up. Failed runs never charged.