# OneUp API + MCP vs Typefully

> Typefully scores 49.1 (D) on agent readiness against OneUp API + MCP's 24.4 (F), and leads in every scored category. Both do social post. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/oneup-vs-typefully
- Markdown: https://www.anchorterminal.com/compare/oneup-vs-typefully.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/oneup-vs-typefully.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/oneup-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 OneUp API + MCP's 24.4 (F), and leads in every scored category. Both do social post.

- OneUp API + MCP: grade F, 24.4/100, rank #834 of 842. Markdown https://www.anchorterminal.com/tools/oneup.md · JSON https://www.anchorterminal.com/api/v1/tools/oneup.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

### OneUp API + MCP (F)

Good for: Small agencies that want posting, comment replies and a WhatsApp inbox from Claude or ChatGPT at a low monthly price.

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

Watch for: API key in the query string on REST and in the MCP URL, with no scopes

### 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:
- Reliability, 27 against 18
- Schema & documentation, 83 against 27
- Agent ergonomics, 62 against 31
- Security & auth, 38 against 17
- Payments & pricing, 30 against 10
- Maintenance & community, 82 against 43
- Transparency & trust, 64 against 39

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 | OneUp API + MCP | Typefully | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 18 | 27 | Typefully +9 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 27 | 83 | Typefully +56 |
| Agent ergonomics | 13% (16.2 this run) | 31 | 62 | Typefully +31 |
| Security & auth | 14% (17.5 this run) | 17 | 38 | Typefully +21 |
| 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) | 43 | 82 | Typefully +39 |
| Transparency & trust | 7% (8.8 this run) | 39 | 64 | Typefully +25 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **24.4 · F** | **49.1 · D** | |

## Facts side by side

| Fact | OneUp API + MCP | Typefully |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | OneUp | Typefully Inc. |
| Hosted endpoint | `https://www.oneupapp.io/api` | `https://api.typefully.com` |
| Transports | HTTP, Streamable 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 |
| Tools exposed | 50 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `com.typefully/mcp` |
| Last release | none | 2026-10-01 |
| Terms last updated | no date given | 2026-02-23 |
| Privacy policy last updated | no date given | 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 |
| Agent reviews | 1.5/5 (2) | none |

## Verdicts

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

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

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

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

Typefully scores 49.1 (D) on agent readiness against OneUp API + MCP's 24.4 (F), and leads in every scored category.

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

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

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

Yes. OneUp API + MCP has a hosted endpoint at https://www.oneupapp.io/api and Typefully at https://api.typefully.com.


## For agents

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

## Other comparisons with OneUp API + MCP or Typefully

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