/

/

Track generative media spend: ElevenLabs, Kling AI and BytePlus

Track generative media spend: ElevenLabs, Kling AI and BytePlus

Track generative media spend: ElevenLabs, Kling AI and BytePlus

Import voice, video and media generation spend next to cloud and LLM costs, and allocate it to products.

Runs in

Claude · Slack

First optimization recommendation

The next day

ROI

Pays for itself with the first recommendation you act on

Show last month's spend on ElevenLabs, Kling AI and BytePlus by product.

› get_context

› get_context

› query ↗ Explorer

› query ↗ Explorer

Media generation, September: €7,900. Kling AI €4,600 (video previews), ElevenLabs €2,100 (voice-over), BytePlus €1,200. Video previews grew 2.4× after the template launch.

The product team adjusts usage or limits.

Playbook

What the agent does

From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.

Costory notices

Weekly media generation spend crosses your threshold.

Context used

Billing data only

Billing data only

Remembered

The product and feature allocation rules are defined in your Context layer.

The product and feature allocation rules are defined in your Context layer.

Costory investigates

01

Connect

ElevenLabs workspace usage, Kling AI pack usage and wallet charges, BytePlus bill details.

02

Normalize

The same cost model as cloud.

03

Allocate

To products and features.

04

Watch

Alerts on weekly spend.

Where you see it

Claude

You decide

The product team adjusts usage or limits.

Why it matters

Generative media tools are billed through wallets and packs, outside the cloud bill. They grow fast and stay invisible.

Who it’s for

AI product teams, finance

Where it runs

Claude · Slack

What you get

What lands in front of your team

Visible media spend

Next to cloud and LLMs.

Allocated

By product or feature.

Spend alerts

Before the wallet surprises you.

Sources and assistants

What it connects

The billing data, context and assistants this playbook uses. Each links to its setup page.

The billing data, context and assistants this playbook uses. Each links to its setup page.

Example prompts

Or drive it yourself

The agent runs this on its own once set up. These prompts open in Claude, pre-filled, to set it up, review it or dig into a result.

The agent runs this on its own once set up. These prompts open in Claude, pre-filled, to set it up, review it or dig into a result.

Review

Show last month's spend on ElevenLabs, Kling AI and BytePlus by product.

Alert

Alert #ai-product when weekly media generation spend exceeds €2,000.

FAQ

Questions about this playbook

Which AI providers can Costory import?

OpenAI, Anthropic (API and claude.ai Enterprise), Azure OpenAI, AWS Bedrock, Google Vertex AI, OpenRouter, Cursor, ElevenLabs, Kling AI and BytePlus.

How long does this playbook take to set up?

Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.

Can we adjust what the agent does?

Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.

Does Costory change anything in our cloud accounts?

No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.

Step-by-step guide in the Costory docs

Put this playbook on call

Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.

First optimization recommendation

The next day

ROI

Pays for itself with the first recommendation you act on

Setup

About 30 minutes

Data residency

EU

Access

Read-only on your cloud