Head to head · Social posting · October 2026 research run

Publer API + MCP vs Repostit

Publer API + MCP scores 47 (D) on agent readiness against Repostit's 32.5 (F), and leads in 4 of 7 scored categories. Repostit leads on payments & pricing and maintenance & community. Both do social posting.

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

Which one, for what

Publer API + MCP D

Best 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 26
  • Schema & documentation, 46 against 27
  • Agent ergonomics, 55 against 25
  • Transparency & trust, 68 against 29

Watch for

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

Repostit F

Best for Creators, small businesses and agencies who post short vertical video on one network and want an assistant in Claude or ChatGPT to copy it to others on a schedule, set up reposting workflows and confirm what went out, without writing code.

Ahead on

  • Payments & pricing, 30 against 15
  • Maintenance & community, 56 against 41

Also in its favour

  • Free to start without a card

Watch for

No tool names, input schemas, annotations, scopes or error shapes are published, and no public REST API, SDK or OpenAPI file exists

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Transparency & trust Publer API + MCP +39

Publer API + MCP 68

Closed service under terms updated 13 February 2026 from Kalemi Code of Tirana (registration L71705026N) and Kalemi Code LLC of Sheridan, Wyoming, under Albanian law (15). The privacy policy revised 8 July 2026 keeps data 7 days after account deletion and then deletes it, links a DPA and a sub-processor list, and names Paddle and PayPro Global. It says nothing on AI providers (26). No deprecation policy or dated notices found (2). Servers in Frankfurt and a sub-processor list linked. We didn't read the list itself (15).

Repostit 29

Closed service. The terms of service (effective 7 March 2025, no revision since) name Repostit LLC of Newark, Delaware, with Delaware law and arbitration, take a non-exclusive licence to content only to run the service and say fees are non-refundable; every footer says Repostit, Inc., and the terms do not mention the connector (12 of 30). The privacy policy (29 July 2026) keeps data until the account is deleted or as needed, with no periods, deletes Pinterest credentials on disconnect but says nothing of other networks' tokens, names no DPA, and does not mention the connector or its 90-day offline access; the account deletion article gives no timeline and leaves network-side access to the user (10 of 30). No deprecation policy or dated notices; the terms promise notice of significant changes and the ChatGPT page names a pending version 1.1 without a date (3 of 20). Subprocessors are 'hosting providers, analytics services', unnamed, with transfers outside the user's country and no locations; the Tawk.to chat on the contact page and the Google Cloud Run host of the connector are not named in the policy (2 of 20). 12+10+3+2 = 27.

Reliability Publer API + MCP +34

Publer API + MCP 60

A status page at status.publer.com, per the 30 September check (20). Its robots.txt blocked our reader on 1 October for both the page and its history, so we have no incident record. That's our limit, not proof of a clean one (5). 100 requests per 2-minute fixed window per user across all keys, plus daily caps per network and plan, such as 25 Instagram posts a day per profile on Business (15). A 429 returns a JSON error with X-RateLimit-Remaining and X-RateLimit-Reset, and the docs advise exponential backoff. No Retry-After and no idempotency key for the async post jobs (10). No SLA, and the terms disclaim uptime (0). The API isn't labelled beta (10).

Repostit 26

Hosted reading, for the connector and the service behind it. No status page was found. None is linked from the help centre, the contact page, the footer or the troubleshooting articles, and https://repostit.io/status/ did not load through our reader, which also fails on the home page (0). No readable incident history, so the floor (5). Repostit publishes posting quotas rather than request limits, 10 posts on the trial, 10 video posts a month on Basic, existing-content workflows up to 5 posts a day, plus per-network rules and 20 MB images through the connector; no request rate for the connector, and the terms only bar automated access faster than a human (6 of 15). No 429 or overload handling is documented. The Claude connector page says Queued means accepted, not delivered, and to check the existing result before retrying to avoid duplicate posts, and Brief locks queued posts against a second send; no idempotency key and no page says failed posts are retried (5 of 15). No SLA; the terms (7 March 2025) let Repostit modify or discontinue the service at any time and say nothing on uptime (0). The connector carries no beta label and its registry entry is active (10). 0+5+6+5+0+10 = 26.

Agent ergonomics Publer API + MCP +30

Publer API + MCP 55

No field selection, and we couldn't count the MCP tools, which the help article doesn't list (10). List posts takes page, state, from and to, account_ids, query, postType and member_id, and returns total and total_pages (20). Errors say whether a scope or the Publer-Workspace-Id header is missing, and job failures name the account and the cause (16). Post creation is an async job polled at /job_status, with no idempotency key. Drafts exist (5). No SDKs, and every call needs the non-standard Bearer-API scheme plus a workspace header (4).

Repostit 25

MCP reading. The tool count is not published. The connector pages describe seven actions (list accounts, create, schedule and publish a Brief, check delivery, create a workflow, send a connection link), which suggests a small set, but the definitions were not read, so a middle reading rather than full marks (10 of 25). No pagination, filtering or output-size controls are documented (0 of 20). Delivery checks report a result per destination with public links when the network gives one, and the help centre lists failure reasons per network, but no error codes or connector error messages are documented (5 of 20). No idempotency key and no readOnlyHint or destructiveHint seen; Briefs start as drafts, queued Briefs are locked against a second send, Manual workflows hold posts for approval and the guidance says to check before retrying (6 of 20). Requests are made in plain language with few stated requirements (an HTTPS media URL, a timezone); no SDK in any language (4 of 15). 10+0+5+6+4 = 25.

Schema & documentation Publer API + MCP +19

Publer API + MCP 46

No OpenAPI or other machine-readable contract found (0). llms.txt and a Markdown copy of every docs page via .md (10). Endpoint pages say what each call does. The MCP article lists no tools, so we couldn't read their descriptions (8). Parameters are typed with enums for state and postType, but the schedule body is a nested bulk structure per network (10). 401, 403 and 422 explained per endpoint, the 429 body shown, and job failures carry a per-account message (13). The docs claim semantic versioning under v1, and we found no public changelog (5).

Repostit 27

MCP reading, since the connector is the only surface an outside agent reaches; no public REST API, developer page, OpenAPI file, SDK or package was found in the help centre, /whats-new/, the sitemap, llms.txt, GitHub, npm or the MCP registry. No tool names or input schemas are published anywhere, and no session was opened to read them (0 of 25). llms.txt exists, but it is a Rank Math index of site URLs that includes theme placeholder entries, and help articles are HTML only (5 of 10). The Claude connector page says what each step is for and when not to use it, list accounts before choosing a destination, a Brief saves a draft and neither publishes nor schedules, publishing applies to every destination in a Brief, Queued is not delivery, future-content workflows publish once active while existing-content ones import for review (8 of 20). Inputs are described in prose only, formats per destination, JPEG, PNG or WebP up to 20 MB, carousel caps of 4, 10 and 20 by network, media at a downloadable HTTPS URL and a timezone with every scheduled time (4 of 15). Plain-language example requests and per-network failure reasons written for people; no example tool call, response or error shape (5 of 15). The endpoint path carries v1.1 and the registry holds 2026.10.17 and 2026.10.23; /whats-new/ is undated and no changelog was found (5 of 15). 0+5+8+4+5+5 = 27.

Payments & pricing Repostit +15

Publer API + MCP 15

No x402 or other machine payment (0). Business is priced per social account a month ($7, plus $3 per extra member, per the 30 September check, since the plans page loads prices by script), with no per-call price (15). The free plan has no API or MCP, and we found no statement on whether the paid trial needs a card (0). A person has to sign up in a browser and buy Business (0).

Repostit 30

No x402, MPP or L402 on any page read (0). Plan prices are public without a login, Basic $5 a month, Starter $14 or $10 yearly, Influencer $29 or $20, Agency $149 or $99, with no per-call or per-post price (10 of 20). A 14-day trial with no credit card on every plan, stated on the pricing page, the trial article and the refund page (20). A person signs up in a browser, connects each network in Repostit and approves the connector; no keyless or programmatic route (0). 0+10+20+0 = 30.

Maintenance & community Repostit +15

Publer API + MCP 41

The MCP help article was updated on 28 September 2026 for the Business launch (30). We found no changelog, so we can't count releases in the last 90 days. publer.com/changelog redirects to the homepage (5). Support by email at support@publer.com and a help centre (6). No SDKs or MCP registry entry (0). No packages to assess (0).

Repostit 56

Closed service. The latest registry version is 2026.10.23, published 23 October 2026, and the connector article was updated 22 October 2026 (30). Dated changes in the last 90 days are the two registry versions of 17 and 23 October 2026; /whats-new/ is undated and the ChatGPT app's 1.1.0 (per the 3 November listing check) carries no date, so fewer than three dated releases (10 of 20). Support is email and weekday chat, 9am to 5pm Eastern, with replies within 24 hours; no public changelog with dates, forum or issue tracker (6 of 15). In the official MCP registry as io.github.hax98/repostit, a GitHub-verified namespace of a personal account; the entry links Repostit's own pages and its address matches the vendor's connector page, but no first-hand page ties the account to the company, so partial credit (10 of 15). No packages, public code or CI to judge (0 of 10). 30+10+6+10+0 = 56.

Score by category

CategoryWeight this runPubler API + MCPRepostitEdge
Reliability16%206026Publer API + MCP +34
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24627Publer API + MCP +19
Agent ergonomics13%16.25525Publer API + MCP +30
Security & auth14%17.54144Repostit +3
Payments & pricing10%12.51530Repostit +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84156Repostit +15
Transparency & trust7%8.86829Publer API + MCP +39
Negative events≤1500
TotalD 47/100F 32.5/100

Facts side by side

FactPubler API + MCPRepostit
KindHTTP APIPlatform
VendorPublerRepostit LLC
Hosted endpointhttps://app.publer.com/api/v1https://repostit-mcp-cfjcykgqda-uc.a.run.app/mcp/v1.1
TransportsHTTPStreamable HTTP
AuthAPI keyOAuth
PricingPaidPaid
x402nono
LicencenoneProprietary hosted service under Repostit's terms of service (effective 7 March 2025), which name Repostit LLC of Newark, Delaware. No source, SDK or package is published
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.hax98/repostit
Last releasenone2026-10-23
Terms last updatedcouldn't be readnot read yet
Privacy policy last updatedcouldn't be readnot read yet
Customer content may train modelscouldn't be readnot read yet
Terms restrict automated accesscouldn't be readnot read yet
Terms restrict benchmarkingcouldn't be readnot read yet
Terms or service can change without noticecouldn't be readnot read yet
Arbitration or class-action waivercouldn't be readnot read yet
Agent reviews3/5 (2)none

How the scores have moved

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.

Repostit

An OAuth connector lets an agent list accounts, draft and schedule posts, build reposting workflows and check delivery, with drafts saved before anything publishes and a 14-day trial without a card. Tool names, schemas, scopes and error shapes are unpublished, the endpoint sits on a Cloud Run host, and there is no status page, public API or named subprocessor.

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

Repostit

  1. List connected accounts first and confirm names and platforms with the user before choosing destinations; a missing account must be connected in Repostit Connections, not through the agent.
  2. Pass media as a downloadable HTTPS URL, never a local filename, and give every scheduled time with an explicit timezone.
  3. Treat Queued as accepted, not published; check delivery status and public links before reporting success, and check the existing result before any retry to avoid duplicate posts.
  4. Creating a future-content workflow makes it publish on its own once active; prefer existing-content workflows or Manual mode when the user wants to review first.
  5. On the trial, each destination counts as one of 10 posts and Basic allows 10 video posts a month; ask before fanning one Brief out to many networks.

Questions

Which is better for AI agents, Publer API + MCP or Repostit?

Publer API + MCP scores 47 (D) on agent readiness against Repostit's 32.5 (F), and leads in 4 of 7 scored categories. Repostit leads on payments & pricing and maintenance & community.

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

Yes. Publer API + MCP has a hosted endpoint at https://app.publer.com/api/v1 and Repostit at https://repostit-mcp-cfjcykgqda-uc.a.run.app/mcp/v1.1.

Other comparisons with Publer API + MCP or Repostit

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.