The AI agent

Where: /agents

The agent is a chat that can operate UseNadia for you. Rather than opening the composer and filling it in, you describe what you want. It reads your calendar, your inbox and how your videos have actually performed, and it writes — once you confirm.

The layout

• Left: Start a new chat and your previous threads. Hidden below 768 px.
• Centre: the conversation, with a Channels in view line above it.

There is no channel picker here. The agent works on the channels of the global scope, like every other page.

The channels of the scope are sent with each message, and so are the other channels of the organisation, by ID, name and platform. The agent therefore knows about accounts it cannot act on: asking “how did my last video do” while scoped to a brand without that account does not end in “I cannot see that account” but in “which account do you mean — Instagram vincentleserpent?”.

Once you confirm which one, the reading tools work on it. Scheduling stays on the scope, and the agent will ask you to change it from the sidebar.

What it can do

The agent has exactly the tools of the MCP server — the same 43, declared one by one. It has no shell and no eval: it can call these and nothing else. In broad strokes:

Area	What the tools cover
Channels	List channels and brands, read a platform’s settings rules, find a free slot
Posts	Read the calendar, schedule, move, edit or delete a post
Analytics	A channel’s numbers, the collected history, and a video’s performance at equal age
Inbox and comments	List and read conversations, poll for new messages, send a DM, list the comments of a post and reply, hide or delete one
Automations	List, create, edit, pose, pause or remove comment → DM templates, and read who went through them
Content board	Read the cards, add an idea, edit a card or move it to another column
Media	List the library, upload from a URL, generate an image or a video, transcribe, cut a video, split it into stories
Webhooks and notifications	List and manage webhooks, read notifications

The full list, tool by tool, with parameters, is on MCP tools; it is not repeated here.

Video performance is the tool worth knowing: current counters, rates as a percentage of views, views at equal age (H+4 … H+168), the focus video ranked against the others at its own age, the H+24 → H+120 multiplier and its projection, velocity, followers (the baseline at publication, Δ24 h and Δ48 h), and the gaps in collection. It is read-only, calls no provider, and answers collected: false with a reason when the channel is not collected — see Analytics.

Two things wait for your click

Caution

This is the deliberate difference from the MCP path. In the chat, two tools never write on their own: the scheduling tool only validates, and the DM tool only prepares the message. Both return a card, and nothing happens until you press its button.

A post. The agent raises a confirmation card: channel, date, content, media, then Schedule or Cancel. A batch containing an immediate post turns the card red and the button into Publish now — the one irreversible action. Clicking it calls the server, which revalidates — the same validation as the composer and the Public API — and only then creates the posts. The agent can also open the composer prefilled instead, which schedules nothing.

A direct message. Asked to answer someone in the inbox, the agent shows you the message with a Send button. Nothing leaves until you click it, and the agent is told never to claim a DM was sent before that button answered. Instagram’s 24 hour window applies here as in the inbox.

Everything else — moving a post, a content card, a template, a webhook — runs as soon as the agent calls it, the way it does over MCP. Moving a post is reversible and refuses a post that already published.

Note

Over MCP and the Public API there is no card: the scheduling tool writes directly and the DM leaves. That path is for a client you drive yourself, where the confirmation is you sending the request.

Working with it

Ask it to draft rather than publish while you are getting a feel for it. A draft lands on the calendar where you can inspect it, and nothing reaches an audience until you promote it.

You can attach media from the media library to the conversation, so “post this image on Thursday morning with a caption about X” works as one message.

Conversations are kept, so you can return to one and continue rather than re-explaining context.

What it cannot do

• Connect a channel for you.
• Change the scope. It will tell you to.

The agent versus MCP

The agent is UseNadia’s own chat, on UseNadia’s model. If you would rather drive UseNadia from a client you already use — Claude, Cursor, Codex — connect through MCP instead: your choice of model, the same tools, and it works alongside whatever else that client can do.