Blotato vs OneUp API + MCP

Blotato

One paid account gives an agent a REST API with a public OpenAPI document and an MCP server with 36 tools, with request limits and error codes documented in detail. No status page, changelog, security contact or free API access was found, and each account has a single key with full access.

OneUp API + MCP

API and MCP on every plan from $25 a month ($15 billed yearly). API key in the query string on REST and in the MCP URL, with no scopes.

Blotato

1. Call blotato_list_accounts or GET /v2/users/me/accounts first, and fetch pageId or boardId before posting to a Facebook Page, LinkedIn company Page or Pinterest
2. Keep the postSubmissionId and poll the status until published, scheduled or failed. It is a receipt, not proof of publication
3. After a timeout on a create call, list existing posts before sending again, because there is no idempotency key
4. Do not generate an API key on a trial account unless the owner accepts the Starter charge
5. Keep REST bodies and MCP arguments apart. REST nests post.content and post.target, and the MCP tool takes flat arguments

OneUp API + MCP

1. Call listcategory, then listcategoryaccount, then schedule. Pass social_network_id as ALL to post to every account in a category
2. Keep the ?apiKey= URLs out of logs and shared configs, and regenerate the key on the API Access page if one leaks
3. Set requireApproval or isDraftPost true when a person should review before anything goes out
4. Page through lists with start, 50 posts at a time
5. Give dates as YYYY-MM-DD HH:MM with no timezone field, so confirm the account timezone first