Get an audit

Head to head · Social post · October 2026 research run

Blotato vs Typefully

Typefully scores 49.1 (D) on agent readiness against Blotato's 46.1 (D), and leads in 6 of 7 scored categories. Blotato leads on reliability. Both do social post.

BlotatoBlotato Inc. · HTTP API D46.1/100#759 of 841 TypefullyTypefully Inc. · HTTP API D49.1/100#713 of 841

Which one, for what

Blotato D

Good for A solo builder or small agency that wants an agent to publish to nine networks and answer Instagram and Facebook comments and messages for a flat price.

Ahead on

  • Reliability, 38 against 27

Also in its favour

  • No incidents deducted, where Typefully loses 3 points for them

Watch for

No status page, incident history or SLA was found, and the help pages send users to a third-party outage site

Typefully D

Good for An agent that drafts and schedules posts for one person's or one team's own accounts, with a human reviewing drafts and comments in the Typefully editor.

Ahead on

  • Agent ergonomics, 62 against 57
  • Security & auth, 38 against 29
  • Payments & pricing, 30 against 10
  • Maintenance & community, 82 against 65
  • Transparency & trust, 64 against 45

Watch for

Rate limits are described by response headers only. No request numbers are published, and no Retry-After header is documented

Score by category

CategoryWeight this runBlotatoTypefullyEdge
Reliability16%203827Blotato +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28283Typefully +1
Agent ergonomics13%16.25762Typefully +5
Security & auth14%17.52938Typefully +9
Payments & pricing10%12.51030Typefully +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86582Typefully +17
Transparency & trust7%8.84564Typefully +19
Negative events≤150-3
Total46.1 · D49.1 · D

Facts side by side

FactBlotatoTypefully
KindHTTP APIHTTP API
VendorBlotato Inc.Typefully Inc.
Hosted endpointhttps://backend.blotato.com/v2https://api.typefully.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary hosted service under Blotato's Terms of Use. The n8n node is MITProprietary service under Typefully's Terms of Service. The Agent Skill and its CLI script in typefully/agent-skills are MIT
Tools exposed36none
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.blotato/mcpcom.typefully/mcp
Last release2026-09-102026-10-01
Terms last updated2026-05-182026-02-23
Privacy policy last updated2026-05-18no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity524 npm/wknone

Verdicts

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.

Typefully

A public OpenAPI 3.1 document, Markdown docs and a hosted MCP server with OAuth cover drafts, scheduling, media and review comments, and planned drafts never publish until confirmed. Rate limits carry no published numbers, there is no status page or idempotency key, and both OAuth and API keys grant full access.

Before you call either

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

Typefully

  1. Call GET /v2/social-sets first. Every draft, media, tag and queue path needs a social_set_id
  2. Use plan_at or omit both dates to leave a draft unpublished. publish_at: "now" posts at once and is asynchronous
  3. Do not retry a failed publish blindly. Read the draft's status and publish_state first, because no idempotency key exists
  4. Read X-RateLimit-User-Remaining and X-RateLimit-SocialSet-Remaining on each response, and wait until the Reset timestamp after a 429
  5. Send the key only as Authorization: Bearer. The legacy MCP URL with ?TYPEFULLY_API_KEY= still works and puts the key in logs

Questions

Which is better for AI agents, Blotato or Typefully?

Typefully scores 49.1 (D) on agent readiness against Blotato's 46.1 (D), and leads in 6 of 7 scored categories. Blotato leads on reliability.

Do Blotato and Typefully need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Blotato and Typefully without installing anything?

Yes. Blotato has a hosted endpoint at https://backend.blotato.com/v2 and Typefully at https://api.typefully.com.

Other comparisons with Blotato or Typefully

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report