canonical: https://jentic.com/apis/p2p.mirotalk.com/p2p-mirotalk

# P2p Mirotalk MiroTalk P2P API

REST API for external applications that integrate with MiroTalk P2P video conferencing. Provides endpoints for managing meetings, generating join URLs, and retrieving statistics.

## For AI agents

REST API for external applications that integrate with MiroTalk P2P video conferencing. Provides endpoints for managing meetings, generating join URLs, and retrieving statistics.

## Scope

Provides access to MiroTalk P2P API functionality as defined in the OpenAPI specification.

## Capabilities

- Get meeting statistics
- List all active meetings
- Create a new meeting
- Generate a direct join URL
- Create an authentication token

## Use cases

### Basic MiroTalk P2P API Integration

Integrate MiroTalk P2P API into your application to access its core functionality.

Example prompt: Use the MiroTalk P2P API API to access vendor services and data.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /stats | Get meeting statistics |
| GET | /meetings | List all active meetings |
| POST | /meeting | Create a new meeting |
| POST | /join | Generate a direct join URL |
| POST | /token | Create an authentication token |

## Key resources

- **Main API** — Primary MiroTalk P2P API resources and operations

## Why Jentic

- **Setup:** Wiring MiroTalk P2P by hand means passing your API key secret in the authorization header on every call and handling its meeting and token creation flow yourself. Through Jentic you install once, import the MiroTalk P2P API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** MiroTalk P2P carries meeting and join details in the request body rather than the URL path, so scope the agent to the operations it needs, such as reading stats, listing meetings, or creating a meeting. Because you choose the allowed operations, minting join tokens is not included unless you add it.
- **Credential handling:** Your MiroTalk P2P API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a meeting room' or 'list active meetings', and Jentic returns the matching MiroTalk P2P operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## FAQ

### What authentication does the MiroTalk P2P API use?

The MiroTalk P2P API uses apiKey authentication.

### How many endpoints does the MiroTalk P2P API have?

The MiroTalk P2P API has 5 endpoints available.

### Can I limit what my agent is allowed to do with the MiroTalk P2P API?

Yes. Because Jentic One is self-hosted, you write the rules that decide which MiroTalk P2P operations your agent may call, so you can allow read-only work like getting meeting statistics and listing active meetings while blocking anything that changes state. MiroTalk P2P carries meeting and join details in the request body rather than the URL path, so you scope by operation, for example permitting creating a meeting but not minting authentication tokens or generating join URLs. Since you choose the allowed operations, token creation is excluded unless you explicitly add it, and your stored API key is injected at execution time without ever entering the agent's prompt or context.