Today we are launching MediaBloom Actions. An Action is a typed, versioned tool your agents can safely call — book a tour, create a ticket, update an opportunity, issue a refund — with schemas, authentication, and audit logging handled for you. It is the missing middle layer between an LLM and a production system, and it is the piece every internal AI team ends up hand-rolling.
The problem Actions solves is the one almost every enterprise AI project eventually hits. A chatbot can talk. A voice agent can listen. But the moment you ask either to actually do something — write a row, send a request, change a state — you have to answer hard questions about safety, authorization, and auditability that LLM frameworks alone were never designed for.
Every Action starts with a schema. You define the inputs, the outputs, the required scopes, and the idempotency key. The runtime validates every call before it reaches your handler. If the model hallucinates a field, the call is rejected before it touches your systems. If a call is retried, the runtime dedupes it by idempotency key, so no customer is ever charged twice or booked twice.
Authentication is scoped per tenant and per user. An agent running for Acme Corp can only invoke Actions that have been authorized for Acme Corp, with the credentials configured for Acme Corp. There is no shared secret across tenants, and there is no way for a prompt injection to escalate privileges.
Every execution is logged with the full request, response, and the model reasoning that triggered it. When a customer asks why the agent did something, you can answer them with a trace, not a guess. Auditors love this, and so do engineering teams who used to spend Friday afternoons reading log files.
The Action SDK gives you a TypeScript-first developer experience. Define an Action in a file, push it to the registry, and every agent in your workspace can use it immediately across voice, chat, and async channels. Versioning is built in; old agents keep working on the old schema while new ones adopt the new one, with a clean deprecation path.
We shipped forty certified Actions on day one for the most common CRMs, EHRs, payment processors, and scheduling platforms. Customers who want something custom can ship a certified internal Action in an afternoon, with the same safety guarantees as the first-party ones.
Actions is what turns a conversation into a business outcome. It is the difference between "the AI told me it would book the tour" and "the tour is booked, confirmed, and on the customer’s calendar."
