Overview
What Beatra is, how the Skill, MCP, and REST layers fit together, and where to start.
Beatra gives agents production multimodal creation — video, image, speech, and music — through one install, one sign-in, and one credit balance. These docs are written for two readers: the developer integrating Beatra, and the agent executing against it.
How the pieces fit
| Layer | What it is | When it applies |
|---|---|---|
| Universal Skill | A portable skill package your agent installs with one message. It teaches the agent Beatra's workflows: billing discipline, task identity, uploads, model discovery. | The starting point for every agent platform. |
| OAuth MCP | The authenticated execution layer at mcp.beatra.ai. Every creation, upload, model, voice, and task operation is an MCP tool call. | Driven by the Skill; agents call it directly once connected. |
| REST/OpenAPI | The same capabilities as HTTP endpoints at api.beatra.ai. | Direct integration for custom, non-agent applications. |
The recommended integration is Skill + MCP: install once and your agent calls every capability directly. The REST API serves custom, non-agent applications.
Choose your path
- You use an agent: follow the Quickstart — one message, one sign-in. Works with any agent that can install a skill package and connect to MCP.
- You build a custom application: start with Authentication, then the API Reference and Async tasks.
- You are an agent reading this: ingest llms.txt for the site
map, the
/llms/*.mdguides for self-contained workflows, and openapi.json for the machine contract.
Capabilities
Four modalities, every one delivered as an asynchronous, credit-billed task with the same envelope, polling, and callback contract:
- Images — generate, transform, and edit images.
- Videos — generate from text, images, frames, or references; edit and extend existing footage.
- Speech & voices — synthesize speech, clone authorized voices, manage a voice library.
- Music — generate music from prompts, lyrics, or reference audio.
The capabilities overview is the one-page matrix:
capability × MCP tool × REST endpoint × execution mode. Capability pages are
not tied to specific models — agents discover models and prices live with
beatra.models.list; to browse them directly, see the
current model lineup.
Platform mechanics
The shared contracts every capability builds on: Async tasks · Uploads · Callbacks · Billing · Errors · Rate limits