AI Agent overview

Connect your AI assistant to the account so it can read stats, create videos and steer campaigns in conversation.

What MCP is

MCP (Model Context Protocol) is the common standard for letting an AI assistant call an external service's tools. Once connected you just talk — "which channel performed best this month?", "pause the October campaign" — and the assistant picks the right tool.

This system ships an MCP server. You write nothing; you point your assistant at an address and sign in once.

How it differs from an API key

	API key	AI Agent
For	Code you write, running a fixed script	An assistant acting on what you say
Auth	A string you paste into config	Sign in once, then approve
Surface	The whole public API	11 curated tools
Irreversible actions	Available; your responsibility	Not present

The two are independent. Using both is fine: the assistant for quick questions and steering, API keys for automation that runs unattended.

Server address

Connect an assistant to this account

The address below matches the domain you are reading on — paste it straight into your assistant.

MCP server address

…/api/v1/public/mcp

Config for file-based clients

{
  "mcpServers": {
    "viai-video": {
      "type": "http",
      "url": "…/api/v1/public/mcp"
    }
  }
}

The entry name "viai-video" is only for you to recognise; any name works. On first connection the assistant opens a browser for you to sign in and approve.

It is a streamable HTTP MCP server. Assistants discover where to authorize through the two standard endpoints at the domain root:

/.well-known/oauth-authorization-server
/.well-known/oauth-protected-resource

You never call these yourself. They exist so the assistant knows where to send you to sign in.

How authorization works

On first connection the assistant opens a browser at this system's sign-in page.
After signing in you see a consent page naming the application requesting access to your account.
Approve, and the assistant receives a token bound to your account. Every tool then reads and writes only within that account.
Your password never passes through the assistant — you type it on this system's own page.

Per-application steps live in Connect an assistant.

Limits that let you sleep

The assistant can still spend your money

create_video and resume_campaign spend real credits. Both tool descriptions tell the assistant to confirm with you first, but that is guidance, not a fence. If you let an assistant run unattended, assume it can spend.

Irreversible actions are deliberately absent from the tool set:

No deleting videos, media files or news sources.
No cancelling campaigns — only pause and resume, both reversible.
No connecting or removing social channels.
No buying plans or topping up credits.

Every extra tool is another way for a vague sentence to turn into a charge. Do those things in the web app or through an API key, where you control each call.