# Publer API + MCP vs Typefully

> Typefully scores 49.1 (D) on agent readiness against Publer API + MCP's 46.8 (D), and leads in 4 of 7 scored categories. Publer API + MCP leads on reliability. Both do social post. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/publer-vs-typefully
- Markdown: https://www.anchorterminal.com/compare/publer-vs-typefully.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/publer-vs-typefully.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/publer-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 Publer API + MCP's 46.8 (D), and leads in 4 of 7 scored categories. Publer API + MCP leads on reliability. Both do social post.

- Publer API + MCP: grade D, 46.8/100, rank #749 of 842. Markdown https://www.anchorterminal.com/tools/publer.md · JSON https://www.anchorterminal.com/api/v1/tools/publer.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

### Publer API + MCP (D)

Good for: Agencies already on Publer Business who want an agent to schedule in bulk and read deep analytics, including competitors.

Ahead on:
- Reliability, 60 against 27

Also in its favour:
- No incidents deducted, where Typefully loses 3 points for them

Watch for: API and MCP only on Business and Enterprise, and the free plan has no API

### 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:
- Schema & documentation, 83 against 46
- Agent ergonomics, 62 against 55
- Payments & pricing, 30 against 15
- Maintenance & community, 82 against 41

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 | Publer API + MCP | Typefully | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 60 | 27 | Publer API + MCP +33 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 46 | 83 | Typefully +37 |
| Agent ergonomics | 13% (16.2 this run) | 55 | 62 | Typefully +7 |
| Security & auth | 14% (17.5 this run) | 41 | 38 | Publer API + MCP +3 |
| Payments & pricing | 10% (12.5 this run) | 15 | 30 | Typefully +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 41 | 82 | Typefully +41 |
| Transparency & trust | 7% (8.8 this run) | 66 | 64 | Publer API + MCP +2 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **46.8 · D** | **49.1 · D** | |

## Facts side by side

| Fact | Publer API + MCP | Typefully |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Publer | Typefully Inc. |
| Hosted endpoint | `https://app.publer.com/api/v1` | `https://api.typefully.com` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | Proprietary service under Typefully's Terms of Service. The Agent Skill and its CLI script in typefully/agent-skills are MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `com.typefully/mcp` |
| Last release | none | 2026-10-01 |
| Terms last updated | couldn't be read | 2026-02-23 |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Agent reviews | 3/5 (2) | none |

## Verdicts

**Publer API + MCP.** Scoped API keys (workspaces, accounts, posts, media, analytics) with 401 and 403 errors that name the missing scope or header. API and MCP only on Business and Enterprise, and the free plan has no API.

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

### Publer API + MCP

1. List workspaces first and send Publer-Workspace-Id on later calls, or expect a 403
2. Poll /job_status/{job_id} after posts/schedule and read payload.failures, since status reads complete even when posts failed
3. Use the Bearer-API scheme, not Bearer
4. Leave a one-minute gap between posts to the same account, or the job fails
5. Read X-RateLimit-Reset after a 429 and wait until then, as there's no Retry-After

### 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, Publer API + MCP or Typefully?

Typefully scores 49.1 (D) on agent readiness against Publer API + MCP's 46.8 (D), and leads in 4 of 7 scored categories. Publer API + MCP leads on reliability.

### Do Publer API + MCP and Typefully need an API key?

Publer API + MCP needs an API key. Typefully takes an API key or an OAuth sign-in.

### Can an agent call Publer API + MCP and Typefully without installing anything?

Yes. Publer API + MCP has a hosted endpoint at https://app.publer.com/api/v1 and Typefully at https://api.typefully.com.


## For agents

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

## Other comparisons with Publer API + MCP or Typefully

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