P2p Mirotalk MiroTalk P2P API

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 isolation

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.

Intent-based discovery

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.