How your AI app works

What UniFeeds tells your AI app when it connects, and what to do when UniFeeds isn't connected.

When your AI app connects, UniFeeds sends it a short set of instructions. They make every app work with your workspace the same careful way.

What the AI does

Checks where it is. It calls whoami first and tells you which workspace it's connected to, and whether it can only read or can also make changes.
Looks up your accounts. It calls list_accounts to get the right account ids. It never guesses them.
Asks before it posts. Before it schedules, publishes or deletes anything, it shows you the text, the accounts and the time, and waits for your yes. It saves drafts without asking.
Retries safely. Every change carries a requestId. If a call fails or times out, the AI retries with the same requestId, so nothing gets posted twice.
Checks the result. Publishing runs in the background. The AI calls get_post and only tells you a post is live once UniFeeds shows it published.

It can only read. Any workspace member can connect an AI app to read. To let it make changes, a workspace admin signs in again from the app and ticks the option to allow changes. With an API key, ask an admin for a read and write key.
Only admins can allow changes. The AI tells you to ask a workspace admin, and doesn't retry.
It needs another workspace. Sign in again from the app and pick that workspace.

See Troubleshooting for other problems.

If your AI app doesn't have UniFeeds' tools, it can't see your workspace. To connect it:

Add the UniFeeds server URL to your app:
MCP server URL
https://mcp.unifeeds.io/mcp
Sign in to UniFeeds when the app asks, pick your workspace and click Allow.

Your app's guide has the exact steps. See Connect your AI app.

Never paste an API key into a chat

Anyone who sees the chat can use the key. If your app needs a key, put it in the app's settings or an environment variable, as its guide shows.