Start here

Route a customer task or support question by surface, client, platform, artifact, and stage.

This is the entry point for customer assistants executing tasks and support agents answering questions. Website instructions describe actions an agent performs or explains to the customer. They are not interchangeable with REST or MCP calls.

Route the request

Use context already supplied. Ask only for a missing fact which changes the next action.

1. Identify the requested outcome and whether you are executing it or explaining it.

2. Identify the surface: Blotato website, MCP, REST, n8n, or Make.

3. Identify the client, destination platform, and failing stage when relevant.

4. Identify the artifact: workflow JSON, local media file, hosted media URL, generated visual, draft, scheduled item, or published post.

5. Check which provider owns the endpoint, key, or node. A Blotato key does not authenticate another provider.

For support, follow Diagnose and answer. Answer the customer's question before offering a tutorial. Preserve completed checks and human corrections.

Website Modes and Current Navigation

Developer Platform is the website navigation for monitoring API, MCP, and automation work. Content Studio is the navigation for the in-app AI Agent and visual creation. Switching modes does not change the subscription, accounts, or content, and does not connect an external assistant.

• In-app AI Agent: Content Studio > New Post. New draft inside the workspace creates a blank draft, not AI output.

• Connect or reconnect social destinations: Accounts > Connect account, or the existing account's actions menu > Reconnect. Accounts is no longer a Settings tab.

• Publication results: Posts > Scheduled, Published, or Failed. Select the platform and time window before concluding a post is missing.

• Recurring slots: Calendar > Weekly schedule, within the Weekly posting schedule section.

• Performance rankings: Analytics > Top posts, not the old Published > Top Performing tab.

• API activity and errors: Developer Platform > Logs.

• Comments and messages: Inbox > Posts or Chats.

• Inspiration, Prompts, and Viral AI Coach: Tools.

• Credentials and client setup: Settings > API. Language and reset controls: Settings > Profile. Credits and subscription: Settings > Billing.

Use Website modes and navigation for the screen-by-screen map and screenshots. The draft's Photo / Video control uploads existing media. Do not send users there to find the old image-generation menu.

Connect and verify

1. Select the exact client in MCP setup, or use the REST quickstart for HTTP, n8n, or Make.

2. Confirm paid access. Generating an API key during a trial starts billing. Read authentication before generating a key.

3. Call blotato_list_accounts, or GET /v2/users/me/accounts.

4. Select the requested social destination from the response. Connect missing accounts in Accounts.

An empty list proves authentication, not publishing readiness. A saved connector, OAuth redirect, or “Connected” label alone does not prove a tool call works. ChatGPT.com and Codex have separate setup paths.

Choose a task

Outcome	Execute through API or MCP	Explain website actions
Connect a social destination	IDs and destinations	Social account settings
Publish or cross-post	Publish and verify	Create posts
Schedule, reschedule, or cancel	Manage schedules	Calendar
Upload or use existing media	Upload and prepare media	Attach media
Generate images, carousels, or video	Generate and verify	Video templates
Extract or repurpose source content	Extract a source	Context
Inspect performance	Analytics	Checkpoints and pending data
Read or reply to public comments	Comments	Inbox
Read or reply to private messages	Messages	Inbox
Set up keyword-triggered replies	DM automations	DM automation guide
Check balance or purchase credits	Credits	Billing and credits
Diagnose a failure	Errors and retries	Support diagnosis

Instructions for the agent

1. Use only available tools and the selected operation's schema. REST and MCP differ in fields and operation coverage.

2. Retrieve current IDs. After reconnection, re-list accounts. Never substitute a social-platform post ID, submission ID, or schedule ID for another ID type.

3. Check platform requirements and media requirements before a write.

4. Confirm the requested destination and authorization. Connection tests must not publish, send messages, purchase credits, or activate automations.

5. Record returned IDs. Use operation-specific completion rules, including error fields inside successful HTTP or MCP responses.

6. Inspect existing work after an uncertain write. Do not blindly repeat a create request.

7. Report the verified status, scheduled time, or returned media/public URL. Explain what remains unresolved.

Documentation for retrieval

Start with the task page, then retrieve only the contract or diagnosis needed.

Resource	Use
Search and read help	Optional public documentation MCP lookup, separate from account access
MCP tools	Available tools and behavior
MCP input index	Required and optional tool arguments
API reference for agents	Generated setup, contracts, examples, and completion rules in 1 document
Documentation index	Find a page outside this task index
Full documentation text	Whole-corpus retrieval when required
OpenAPI JSON	Published REST schemas

Reading documentation does not install a server, authorize an account, or execute a task.