Quickstart

Beatra is not tied to any single agent product: if your agent can install a skill package and connect to an MCP server, the flow below just works.

Install Beatra

Send this message to your agent:

Install Beatra and tell me when I need to sign in: https://beatra.ai/install.md

Your agent will identify the platform, complete the setup steps it can, and tell you if a platform setting needs your help. When Beatra opens in your browser, sign in and approve access once.

After setup, start a new agent session so Beatra is available. The same sign-in covers image, video, music, and speech creation; switching media types does not require another authorization.

Checkpoint — your agent confirms the install, the browser sign-in page opened and you approved access once, and the agent reports the Beatra connection is verified. If any of these is missing, send the install message again.

Start creating

Ask for the result you want in normal language, for example:

Create a warm editorial illustration for this landing page.

Beatra keeps longer work moving in the background and returns the result to your agent when it is ready. Creating media uses Beatra credits.

Checkpoint — the agent acknowledges a Beatra task was created, and when it finishes you receive the artifact (image, video, audio) with the credits that were charged. A task still in queued or running is normal — the agent keeps polling; it is not a failure.

If installation or sign-in is interrupted, send the install message again. Your agent will keep the steps that are already correct and continue from the part that still needs attention.

Building your own service

Developers connecting a custom application can use the REST/OpenAPI interface:

• OpenAPI reference
• Authentication
• Task lifecycle