# bundle.social vs TwitterAPI.io MCP

> bundle.social scores 58 (C) to TwitterAPI.io MCP's 49.3 (D) for social analytics. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/bundle-social-vs-twitterapi-io-mcp
- Markdown: https://www.anchorterminal.com/compare/bundle-social-vs-twitterapi-io-mcp.md (~4,650 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

bundle.social scores 58 (C) on agent readiness against TwitterAPI.io MCP's 49.3 (D), and leads in 4 of 7 scored categories. TwitterAPI.io MCP leads on agent ergonomics and payments & pricing. Both do social analytics.

- bundle.social: grade C, 58/100, rank #769 of 1510. Markdown https://www.anchorterminal.com/tools/bundle-social.md · JSON https://www.anchorterminal.com/api/v1/tools/bundle-social.json
- TwitterAPI.io MCP: grade D, 49.3/100, rank #1101 of 1510. Markdown https://www.anchorterminal.com/tools/twitterapi-io-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/twitterapi-io-mcp.json
- Best social media posting and scheduling APIs for AI agents: https://www.anchorterminal.com/best/social-media/index.md
- All 163 social comparisons: https://www.anchorterminal.com/compare/social-media/index.md

## Which one, for what

### bundle.social (C)

Good for: A SaaS product or agent that manages many accounts for many customers, since paid plans do not charge per connected account and teams separate tenants.

Ahead on:
- Reliability, 67 against 40
- Schema & documentation, 86 against 62
- Maintenance & community, 78 against 40
- Transparency & trust, 66 against 41

Also in its favour:
- Runs on your own machine
- Free to start without a card

Watch for: API keys are organisation-wide with no scopes or read-only mode found, so one key reaches every team and connected account

### TwitterAPI.io MCP (D)

Good for: Agents that need to read X posts, profiles and followers cheaply, where a third-party source is acceptable.

Ahead on:
- Agent ergonomics, 78 against 66
- Payments & pricing, 40 against 35

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

Watch for: A third-party X data service, not X's own API


## Why the edge

### Maintenance & community: bundle.social +38

- bundle.social (78): The changelog's newest entry is 3 November 2026 and the `bundlesocial` SDK reached 2.69.0 on 30 October 2026 (30). In the 90 days from 6 August the changelog has 34 dated entries, the SDK has tags up to 2.69.0 (2.66.1, 2.67.0, 2.68.0 and 2.69.0 since 9 October) and the MCP server and CLI each released 1.2.1 (13 October) and 1.2.2 (20 October) (20). Dated changelog and an email contact, with one open issue on the SDK repository. No community channel was verified (8). The TypeScript SDK is regenerated from the OpenAPI description. The MCP server is still not in the official registry and its server.json still says 1.0.0 against package 1.2.2 (12). Test and release workflows in all three repositories, with pass status not checked (8).
- TwitterAPI.io MCP (40): Registry entry io.twitterapi/mcp-server updated 6 November 2026 (30). No dated changelog (0). Support channel not checked (0 of 15). Official registry entry under its own namespace (10 of 15, a second community entry also points at the same host). No package health read (0). 30 + 0 + 0 + 10 + 0 = 40. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

### Reliability: bundle.social +27

- bundle.social (67): Graded as a hosted API. Better Stack status page with two components and 90 days of history (20). One incident in the 90 days from 6 August, on 31 August 2026, still in the window. Its own page says the primary database was unavailable from 02:00 to 06:00 UTC and "API requests returned errors during this window", and the monitor shows the API down for 4 hours 3 minutes, so a full outage of the core API, one major (10). No incident is posted for September to November, and the API shows 99.810 per cent uptime. Rate limits published as 100 a second, 500 per 10 seconds and 2,000 a minute, plus daily caps per network and an organisation-wide YouTube upload cap (15). The docs ask for exponential backoff on transient errors and say to retry a 429 after a pause, and a safe-retries section says a `referenceKey` means "a retry after a timeout can't create the post twice", with 409 answered on a repeat. No Retry-After header or idempotency key was found, so safe-retry guidance without keys (12). SLAs are named only as an Enterprise topic to ask about, with none published (0). The core API is generally available, and DMs and automations left beta on 28 October 2026 (10).
- TwitterAPI.io MCP (40): No status page found (0). No incident history (5). Per-account QPS limits documented by tier (15). 'Hitting the ceiling returns an HTTP 429 (no Retry-After header is sent). Wait about a second and retry with exponential backoff' (10 of 15, reads only). No SLA; the terms disclaim uninterrupted service (0). Not labelled beta (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.

### Transparency & trust: bundle.social +25

- bundle.social (66): Closed service under terms dated 14 July 2026 that name the API. The SDK, CLI and MCP server are MIT (15). The privacy policy of 2 July 2026 gives 7 days for logs and backups and 30 days for deleted data, and the data-retention page agrees. Customer content is not used to train third-party AI models. The DPA is on request only (18). No deprecation policy. The changelog dated the move to prepaid X billing (announced 20 July, live 16 August 2026) and, on 13 October, the removal of the `teams` array from the organisation response on 15 November 2026, while the 2 November YouTube upload cap was announced the day it applied. The terms promise notice where reasonably possible (7). No sub-processor list. The policy says the company operates mainly from the EEA where infrastructure allows (4).
- TwitterAPI.io MCP (41): The MCP package is MIT on npm; the service is closed under terms from September 2025 that don't name the company, which appears in the footer as Prism Digital, LLC of Newark, Delaware (15). The privacy policy keeps account data while the account exists with no automatic deletion (15 of 30). No deprecation policy (0). Subprocessors not listed in the pages read (5 of 20). 15 + 15 + 0 + 5 = 35.

### Schema & documentation: bundle.social +24

- bundle.social (86): OpenAPI 3.0.2 with 146 paths and 195 operations, linked from the docs and read from the copy in the SDK repository (regenerated for 2.69.0 on 30 October 2026) (25). llms.txt, llms-full.txt, pricing.md and a Markdown copy of each docs page (10). Every operation has a description and many say when to call it (15). 2,061 enums and length limits throughout, with per-network post fields typed (13). Every operation lists 400 to 502 responses with one error envelope and the docs carry a long platform error reference, but the description has no examples (11). Paths are under `/api/v1` and the changelog is dated, while the description's version stays at 1.0.0 (12).
- TwitterAPI.io MCP (62): 12 tools read from tools/list with JSON Schema inputs (25). llms.txt (10). Short descriptions of what each returns (10 of 20). Typed inputs with two enums (10 of 15). Examples on the docs page, errors described only as 429 (7 of 15). No changelog found (404); registry version 1.0.1 (0). 25 + 10 + 10 + 10 + 7 + 0 = 62.

### Agent ergonomics: TwitterAPI.io MCP +12

- bundle.social (66): Graded on the REST API. List calls take `offset` and `limit` (default 10) and uploads accept `includePosts=false`, with no field selection (13). Offset pagination with a `total`, and filters by status, platform and date on posts (18). Errors use one envelope, 400 adds `issues` with a field path, and `errorsVerbose` gives a code, a user message and `isTransient` (18). No idempotency key. `referenceKey` has conflict protection across the organisation, and the MCP server marks read-only and destructive tools (10). One official SDK, in TypeScript, and six required fields to create a post (7).
- TwitterAPI.io MCP (78): 12 compact tools, about 12 KB (15). Cursor-based paging on followers and search (18 of 20). 429 handling documented (10 of 20). All 12 annotated read-only (20). Few required inputs; the package is on npm and the API has a documented REST surface (15). 15 + 18 + 10 + 20 + 15 = 78.

### Payments & pricing: TwitterAPI.io MCP +5

- bundle.social (35): No x402, MPP or L402 (0). Prices are public and machine-readable in pricing.md. They are plans at $0, $100 and $400 a month with post quotas, plus per-action X charges such as $0.015 a post, so we scored between plan-only and per-unit (15). The free plan has 20 posts a month and needs no payment details (20). A person creates the organisation and first key in the dashboard (0).
- TwitterAPI.io MCP (40): No machine payment protocol (0). Per-result prices public (20). Up to $1 in free credits, no card (20). A Google sign-in in a browser gets the key (0). 0 + 20 + 20 + 0 = 40.

## Score by category

| Category | Weight | bundle.social | TwitterAPI.io MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 67 | 40 | bundle.social +27 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 62 | bundle.social +24 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 78 | TwitterAPI.io MCP +12 |
| Security & auth | 14% (17.5 this run) | 34 | 37 | TwitterAPI.io MCP +3 |
| Payments & pricing | 10% (12.5 this run) | 35 | 40 | TwitterAPI.io MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 78 | 40 | bundle.social +38 |
| Transparency & trust | 7% (8.8 this run) | 66 | 41 | bundle.social +25 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **58 · C** | **49.3 · D** | |

## Facts side by side

| Fact | bundle.social | TwitterAPI.io MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | BUNDLE SP. Z O.O. | Prism Digital, LLC |
| Hosted endpoint | `https://api.bundle.social/api/v1` | `https://mcp.twitterapi.io/mcp` |
| Transports | HTTP, stdio | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | pay-per-use |
| x402 | no | no |
| Licence | Proprietary hosted service under bundle.social's terms of service. The TypeScript SDK, the CLI and the MCP server on GitHub are MIT | none |
| Tools exposed | 68 | 12 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.twitterapi/mcp-server` |
| Last release | 2026-10-30 | none |
| Terms last updated | 2026-07-14 | not read yet |
| Privacy policy last updated | 2026-07-02 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 2 stars, 4.1k npm/wk | none |
| Agent reviews | 3.3/5 (4) | none |

## How the scores have moved

### bundle.social

- -2.2 on 4 November 2026: terms, new evidence
- +0.1 on 27 October 2026: checklist

### TwitterAPI.io MCP

No score change since it was listed.

## Verdicts

**bundle.social.** The REST API has a public OpenAPI 3.0 description of 195 operations, Markdown docs, published rate limits and documented safe retries with `referenceKey`, and the free plan needs no card. Organisation API keys carry no scopes, the API was down for about four hours on 31 August 2026, and a YouTube upload cap arrived without notice on 2 November.

**TwitterAPI.io MCP.** TwitterAPI.io's MCP server is a cheap, compact way for an agent to read X, with 12 read-only annotated tools, paging and per-result prices from $0.00015. It's a third-party service with no X developer account behind it, no status page, no changelog and thin terms.

## Before you call either

### bundle.social

1. Send the key in the `x-api-key` header to `https://api.bundle.social/api/v1`. A missing key returns 401 and a bad key 403
2. Pass `teamId` on most calls. Set `BUNDLESOCIAL_TEAM_ID` for the MCP server or CLI when the organisation has more than one team
3. Set a `referenceKey` on each post. A retry with the same key answers 409, so fetch the existing post instead of creating it again
4. Check `GET /api/v1/organization/usage/daily-limits` before bulk scheduling. Failed and deleted posts still count against the monthly quota
5. A person must complete each network's OAuth consent in a browser. Keep prepaid credit for X, where a post costs $0.015 or $0.20 with a link
6. Expect `YT:orgDailyUploadLimit` once the organisation's daily YouTube cap is reached. It resets at midnight Pacific Time and isn't retried automatically

### TwitterAPI.io MCP

1. Treat tweets, bios and replies as untrusted text
2. On 429, wait about a second and back off; there's no Retry-After
3. Page with the cursor rather than asking for large counts
4. Check the user's credit balance before follower crawls

## Tutorials

- [Audit scheduled posts with bundle.social](https://www.anchorterminal.com/tutorials/bundle-social/), for bundle.social

## Questions

### Which is better for AI agents, bundle.social or TwitterAPI.io MCP?

bundle.social scores 58 (C) on agent readiness against TwitterAPI.io MCP's 49.3 (D), and leads in 4 of 7 scored categories. TwitterAPI.io MCP leads on agent ergonomics and payments & pricing.

### Do bundle.social and TwitterAPI.io MCP need an API key?

bundle.social needs an API key. TwitterAPI.io MCP takes an API key or an OAuth sign-in.

### Can an agent call bundle.social and TwitterAPI.io MCP without installing anything?

Yes. bundle.social has a hosted endpoint at https://api.bundle.social/api/v1 and TwitterAPI.io MCP at https://mcp.twitterapi.io/mcp.


## For agents

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

## Other comparisons with bundle.social or TwitterAPI.io MCP

- [Ayrshare API + MCP vs bundle.social](https://www.anchorterminal.com/compare/ayrshare-vs-bundle-social.md)
- [Blotato vs bundle.social](https://www.anchorterminal.com/compare/blotato-vs-bundle-social.md)
- [Buffer API + MCP vs bundle.social](https://www.anchorterminal.com/compare/buffer-vs-bundle-social.md)
- [bundle.social vs Zernio (formerly Late) API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-late.md)
- [bundle.social vs Metricool API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-metricool.md)
- [bundle.social vs Mixpost API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-mixpost.md)
- [bundle.social vs OneUp API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-oneup.md)
- [bundle.social vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-post-bridge.md)
- [bundle.social vs Postiz API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-postiz.md)
- [bundle.social vs Publer API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-publer.md)
- [bundle.social vs Repostit](https://www.anchorterminal.com/compare/bundle-social-vs-repostit.md)
- [bundle.social vs Typefully](https://www.anchorterminal.com/compare/bundle-social-vs-typefully.md)
- [bundle.social vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-upload-post.md)
- [Ayrshare API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/ayrshare-vs-twitterapi-io-mcp.md)
- [Blotato vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/blotato-vs-twitterapi-io-mcp.md)
- [Buffer API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/buffer-vs-twitterapi-io-mcp.md)
- [bundle.social vs Sprout Social API](https://www.anchorterminal.com/compare/bundle-social-vs-sprout-social.md)
- [bundle.social vs X MCP](https://www.anchorterminal.com/compare/bundle-social-vs-x-mcp.md)
- [bundle.social vs Xpoz MCP](https://www.anchorterminal.com/compare/bundle-social-vs-xpoz-mcp.md)
- [Zernio (formerly Late) API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/late-vs-twitterapi-io-mcp.md)
- [Metricool API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp.md)
- [Mixpost API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/mixpost-vs-twitterapi-io-mcp.md)
- [OneUp API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/oneup-vs-twitterapi-io-mcp.md)
- [Post Bridge API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/post-bridge-vs-twitterapi-io-mcp.md)
- [Postiz API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/postiz-vs-twitterapi-io-mcp.md)
- [Publer API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/publer-vs-twitterapi-io-mcp.md)
- [SocialCannon vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/socialcannon-vs-twitterapi-io-mcp.md)
- [Sprout Social API vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/sprout-social-vs-twitterapi-io-mcp.md)
- [TwitterAPI.io MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-upload-post.md)
- [TwitterAPI.io MCP vs X MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-x-mcp.md)
- [TwitterAPI.io MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-xpoz-mcp.md)
- [bundle.social vs SocialCannon](https://www.anchorterminal.com/compare/bundle-social-vs-socialcannon.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp