Connect the tools you built to one production workspace.

AI video production infrastructure for your team and agents. Connect your own tools and AI agents to Martini over the API, MCP or CLI. Every shot remembers who made it, how, and what it cost. Generations bill to your own fal key.

Studios, agencies and companies that make AI video seriously and build their own tools or use AI agents. It works whether your films are fully AI or AI is one part of production.

Everything around the model call. A shared canvas and timeline where your team and agents work on the same shots, live. A record of which model or tool made every asset, and every change since. Spend by person, agent, project and model. Martini Bar gives your own tools that layer, so you don’t have to build it.

Three ways in. The API is for your app’s server. MCP is how Claude, ChatGPT and coding agents like Claude Code, Codex and Cursor connect to Martini. The CLI is for scripts and batch jobs from the terminal.

Yes. They connect over MCP or the CLI and work on the same project as your team: drafting shots, running batch generations and assembling cuts. What they make shows up in each shot’s history and in spend by agent.

Create a key in Settings → API keys, then connect your tool over the API, MCP or CLI. The API docs include a prompt you can paste into the coding agent you built your tool with, so it can wire up the connection with you. Your tool then sends shots in and reads the results back.

No. Your tools stay yours. They send work to Martini and read the results back.

Every shot keeps what it cost. You see spend by person, agent, project and model, so you know where the budget went before the invoice arrives.

fal runs the models. Martini is where the shots go next: your team reviews and cuts them on one canvas and timeline, and every shot keeps a record of how it was made and what it cost. Martini Bar uses your fal key, so you keep your fal rates.

No, but it’s the point of these plans. With your studio’s fal key, generations bill to your fal account at your fal rates. Without one you pay in olives, Martini’s credits. A few things cost olives on every plan: models not on fal, and set shots, voice creation, chat and agent work, which run on Martini’s own key.

Yes. The API, MCP and the CLI work with every Martini account, on every plan. You make API keys in Settings → API keys. API generations bill to your fal key when one is set, and spend olives otherwise.

No webhooks yet: your app checks for results (the clients’ subscribe(), or martini wait). Your tool can’t appear inside Martini; it links into a project, shot or sequence instead. And Martini doesn’t bill your own customers for you.