# Quickstart
> Send one message and sign in once, and Beatra is available in your agent. If the agent can install a Skill and connect to an MCP server, the flow below is the same.

### Send the install message to your agent

```text title="Send to your agent"
Install Beatra and tell me when I need to sign in: https://beatra.ai/install.md
```

Your agent identifies the platform, finishes the setup it can do on its own, and tells you if a platform setting needs your help.

**Checkpoint**

- [x] The agent confirms the install is complete.

### Sign in once in the browser

When Beatra opens in the browser, sign in and approve access once. That one sign-in covers image, video, music, and speech; switching media types does not need another authorization. After that, start a new agent session so Beatra loads.

**Checkpoint**

- [x] The browser opened the sign-in page and you approved access once.
- [x] The agent reports the Beatra connection is verified.

### Start creating

Describe the result in ordinary language:

```text title="Send to your agent"
Create a warm editorial illustration for this landing page.
```

Longer work keeps moving in the background, and the agent returns the result when it is ready. Creating media uses credits.

**Checkpoint**

- [x] The agent confirms a Beatra task was created.
- [x] When it finishes you receive the artifact and the charge. A task still waiting in line, or still generating, is normal. The agent keeps checking progress.

### View it in the console or on your phone

The work appears on the [console assets page](https://console.beatra.ai/assets). You can also scan with WeChat and open it in the [Beatra mini program](https://beatra.ai/en/mini-program?utm_source=docs&utm_medium=quickstart).

> **Install or sign-in interrupted?**
>
> Send the same install message again. The agent keeps the steps that are already correct and continues from the part that still needs attention.

## Building your own service

To integrate Beatra in your own application, use REST/OpenAPI:

- [REST · API reference](https://docs.beatra.ai/en/docs/api-reference) — Every v1 endpoint and the machine-readable contract.
- [Before you start · Authentication & request conventions](https://docs.beatra.ai/en/docs/authentication) — API keys, shared headers, and idempotency.
- [Mechanics · Async tasks](https://docs.beatra.ai/en/docs/mechanisms/async-tasks) — The lifecycle from submit to a terminal state.