# Meshcast

Meshcast provides live media transport and an account API for headless automation.
Creating a stream reserves an ID and credentials; it does not start an encoder.

- [Automation guide](https://app.meshcast.io/docs/account-api): Token setup, stream creation, credentials, retries and control limitations. [Markdown](https://app.meshcast.io/docs/account-api.md).
- [OpenAPI contract](https://app.meshcast.io/openapi.json): Supported operations, schemas and required scopes. Check the target deployment before use.
- [API reference](https://app.meshcast.io/api/docs): Interactive reference.
- [Token settings](https://app.meshcast.io/settings/api-tokens): Account owner creates an expiring, scoped token once through browser login.
- [Self-hosting guide](https://app.meshcast.io/docs/self-hosting): Optional self-hosting; not required for headless stream creation. [Markdown](https://app.meshcast.io/docs/self-hosting.md).

Account tokens authenticate only documented /api/v1 operations. Publishing keys
are separate secrets. Do not send account tokens to media nodes or viewer URLs.