Get an audit

Head to head · Social posting · October 2026 research run

bundle.social vs Typefully

bundle.social scores 60.1 (C) on agent readiness against Typefully's 49.1 (D), and leads in 5 of 7 scored categories. Both do social posting.

Best social media posting and scheduling APIs for AI agents · All 103 social comparisons

bundle.socialBUNDLE SP. Z O.O. · HTTP API C60.1/100#530 of 950 TypefullyTypefully Inc. · HTTP API D49.1/100#802 of 950

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, 63 against 27
  • Payments & pricing, 35 against 30

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • No incidents deducted, where Typefully loses 3 points for them

Watch for

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

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.

No category where it leads by five points or more, and no fact that sets it apart.

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 runbundle.socialTypefullyEdge
Reliability16%206327bundle.social +36
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28683bundle.social +3
Agent ergonomics13%16.26662bundle.social +4
Security & auth14%17.53438Typefully +4
Payments & pricing10%12.53530bundle.social +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87882Typefully +4
Transparency & trust7%8.86564bundle.social +1
Negative events≤150-3
Total60.1 · C49.1 · D

Facts side by side

Factbundle.socialTypefully
KindHTTP APIHTTP API
VendorBUNDLE SP. Z O.O.Typefully Inc.
Hosted endpointhttps://api.bundle.social/api/v1https://api.typefully.com
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
Price for social posting$0.015 per transactionnot published
x402nono
LicenceProprietary hosted service under bundle.social's terms of service. The TypeScript SDK, the CLI and the MCP server on GitHub are MITProprietary service under Typefully's Terms of Service. The Agent Skill and its CLI script in typefully/agent-skills are MIT
Tools exposed68none
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.typefully/mcp
Last release2026-10-062026-10-01
Terms last updated2026-07-142026-02-23
Privacy policy last updated2026-07-02no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2 stars, 4.1k npm/wknone

Verdicts

bundle.social

The REST API has a public OpenAPI 3.0 description of 194 operations, Markdown docs and published rate limits, and the free plan needs no card. Organisation API keys carry no scopes, there is no idempotency key, and the status page shows one API outage of 4 hours 3 minutes on 31 August 2026.

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

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 and look it up with the reference-key endpoint before retrying a create, because there is no idempotency key
  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

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, bundle.social or Typefully?

bundle.social scores 60.1 (C) on agent readiness against Typefully's 49.1 (D), and leads in 5 of 7 scored categories.

Do bundle.social and Typefully need an API key?

bundle.social needs an API key. Typefully takes an API key or an OAuth sign-in.

Can an agent call bundle.social and Typefully without installing anything?

Yes. bundle.social has a hosted endpoint at https://api.bundle.social/api/v1 and Typefully at https://api.typefully.com.

Other comparisons with bundle.social 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