# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/blotato-vs-typefully
- Markdown: https://www.anchorterminal.com/compare/blotato-vs-typefully.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/blotato-vs-typefully.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/blotato-vs-typefully.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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.

- Blotato: grade D, 46.1/100, rank #760 of 842. Markdown https://www.anchorterminal.com/tools/blotato.md · JSON https://www.anchorterminal.com/api/v1/tools/blotato.json
- Typefully: grade D, 49.1/100, rank #714 of 842. Markdown https://www.anchorterminal.com/tools/typefully.md · JSON https://www.anchorterminal.com/api/v1/tools/typefully.json

## 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

| Category | Weight | Blotato | Typefully | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 38 | 27 | Blotato +11 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 82 | 83 | Typefully +1 |
| Agent ergonomics | 13% (16.2 this run) | 57 | 62 | Typefully +5 |
| Security & auth | 14% (17.5 this run) | 29 | 38 | Typefully +9 |
| Payments & pricing | 10% (12.5 this run) | 10 | 30 | Typefully +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 65 | 82 | Typefully +17 |
| Transparency & trust | 7% (8.8 this run) | 45 | 64 | Typefully +19 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **46.1 · D** | **49.1 · D** | |

## Facts side by side

| Fact | Blotato | Typefully |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Blotato Inc. | Typefully Inc. |
| Hosted endpoint | `https://backend.blotato.com/v2` | `https://api.typefully.com` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service under Blotato's Terms of Use. The n8n node is MIT | Proprietary service under Typefully's Terms of Service. The Agent Skill and its CLI script in typefully/agent-skills are MIT |
| Tools exposed | 36 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `com.blotato/mcp` | `com.typefully/mcp` |
| Last release | 2026-09-10 | 2026-10-01 |
| Terms last updated | 2026-05-18 | 2026-02-23 |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 524 npm/wk | none |

## 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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/blotato-vs-typefully.json, and with the fewest tokens: https://www.anchorterminal.com/compare/blotato-vs-typefully.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "blotato", "b": "typefully"}`. From a terminal: `anchor compare blotato typefully`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/blotato.json and https://www.anchorterminal.com/api/v1/tools/typefully.json

## Other comparisons with Blotato or Typefully

- [Ayrshare API + MCP vs Blotato](https://www.anchorterminal.com/compare/ayrshare-vs-blotato.md)
- [Ayrshare API + MCP vs Typefully](https://www.anchorterminal.com/compare/ayrshare-vs-typefully.md)
- [Blotato vs Buffer API + MCP](https://www.anchorterminal.com/compare/blotato-vs-buffer.md)
- [Blotato vs Zernio (formerly Late) API + MCP](https://www.anchorterminal.com/compare/blotato-vs-late.md)
- [Blotato vs Metricool API + MCP](https://www.anchorterminal.com/compare/blotato-vs-metricool.md)
- [Blotato vs Mixpost API + MCP](https://www.anchorterminal.com/compare/blotato-vs-mixpost.md)
- [Blotato vs OneUp API + MCP](https://www.anchorterminal.com/compare/blotato-vs-oneup.md)
- [Blotato vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/blotato-vs-post-bridge.md)
- [Blotato vs Postiz API + MCP](https://www.anchorterminal.com/compare/blotato-vs-postiz.md)
- [Blotato vs Publer API + MCP](https://www.anchorterminal.com/compare/blotato-vs-publer.md)
- [Blotato vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/blotato-vs-upload-post.md)
- [Buffer API + MCP vs Typefully](https://www.anchorterminal.com/compare/buffer-vs-typefully.md)
- [Zernio (formerly Late) API + MCP vs Typefully](https://www.anchorterminal.com/compare/late-vs-typefully.md)
- [Metricool API + MCP vs Typefully](https://www.anchorterminal.com/compare/metricool-vs-typefully.md)
- [Mixpost API + MCP vs Typefully](https://www.anchorterminal.com/compare/mixpost-vs-typefully.md)
- [OneUp API + MCP vs Typefully](https://www.anchorterminal.com/compare/oneup-vs-typefully.md)
- [Post Bridge API + MCP vs Typefully](https://www.anchorterminal.com/compare/post-bridge-vs-typefully.md)
- [Postiz API + MCP vs Typefully](https://www.anchorterminal.com/compare/postiz-vs-typefully.md)
- [Publer API + MCP vs Typefully](https://www.anchorterminal.com/compare/publer-vs-typefully.md)
- [Typefully vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/typefully-vs-upload-post.md)
- [Blotato vs X MCP](https://www.anchorterminal.com/compare/blotato-vs-x-mcp.md)