Publora - A publishing API for agents to post on 10 social platforms
Publora is a publishing API for 10 social platforms. One REST API call handles multi-network distribution — no SDKs, no OAuth wiring. The native MCP server with 18 tools gives AI agents like Claude and Cursor a full engagement loop: post, comment, react, pull analytics — across LinkedIn, X, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky, Mastodon, and Telegram
Replies
Do I need X api credits to post in the Pro plan or is it included?
Publora
@aymnart Yes, it's included! 😊
@aymnart That’s exactly the point! You don’t need an X developer account or API credits. Just connect your account once via OAuth in Publora, and we handle all the API complexity on our side.
@michael_vavilov At the moment, we don’t expose proxy/IP geo selection to users. Our infrastructure currently runs from the US (Virginia).
That said, it’s a great point. We know that for TikTok, not only the country but often even the publication location can affect distribution. We’ve also seen creators deliberately optimize for local presence.
We’re definitely thinking about adding support for publishing through residential proxies and allowing users to choose the target country (or even city) in the future.
Naoma AI Demo Agent
Publora
@dmitry_zakharov_ai Thank you!
Scade.pro
@dmitry_zakharov_ai 😁😁😁
Gonna try this for our team, do you guys have a trial?
Publora
@alexander_anastasin Yes! We have a free Starter plan — 15 posts/month, no credit card required. Just sign up and go 😊
MapMagic
Cool stuff. I actually built something like this for myself, but burned out trying to get official Twitter/X API access 😅 that approval process is brutal
@shirokolobov Ha - you just described why we exist 🙂 This isn't a "vibe-code it in a weekend" project. The hard part is the huge bureaucracy of the digital giants, where you sink tons of time, effort and money into official channel approvals. We've done that legwork across every platform so you don't have to.
Publora
@shirokolobov That struggle is real — we've been there too! That's exactly the headache we took on so you don't have to. 😊
Exposing 18 distinct tools across 10 networks inside a single MCP server is incredibly powerful. How do you optimize the tool schemas to prevent LLMs (like Claude in Cursor or Claude Code) from getting 'tool fatigue' or hallucinating arguments when trying to orchestrate complex, multi-platform actions like cross-posting to both X and Bluesky simultaneously?
@nurlyzhann
The short version: we push all the constraints down to the schema layer, not the prompt — so the model can't really get this wrong.
A few specifics:
• Every closed value set is a z.enum, so a hallucinated argument dies in Zod validation before it ever reaches the API — the LLM gets an immediate, typed error to correct from instead of a silent bad call.
• Opaque platform IDs are only accepted verbatim from a paired list_connections discovery call — the field description literally says "do NOT invent or guess IDs", so there's nothing for the model to make up.
• Cross-posting to X + Bluesky (or all of them) is a single create_post with a platforms[] array. The per-network fan-out happens server-side, so the model never has to reason about platform differences at all — it just says "post this, to these".
That combo is what keeps it from turning into 18-tools-worth of cognitive load: the agent reasons about intent, the schema + server handle correctness. Happy to nerd out more if you're building in this space!
This is cool, real need to get communication in sync with work. Do you have indexing as well ?
@thinkharshh Ah, if you mean scraping/indexing social networks — then no, that's not something we do 🙂
Publora is focused purely on the content side: creating, publishing and handling your posts (and replies/comments) through the official APIs. We're not in the data-harvesting business. If your use case is more on the "post & engage from my agent" side, that's exactly our wheelhouse — happy to dig in!
Congrats on the launch! This looks like a very useful layer for AI-native content workflows — especially if teams want agents to handle distribution without building 10 separate platform integrations.
Curious how you handle the approval flow: can an agent prepare posts and replies while a human still confirms before publishing?
Publora
@muravyov Thanks for the question! Yes, that's possible — give it a try! 😊
not gonna lie, every new social integration usually means another thing to maintain. The idea of handling everything through one layer is pretty appealing
Publora
@furkan_kara1 One integration, posting to multiple platforms — give it a try! 😊
RankSpot
Congrats on the launch team! Super fair pricing. Will give it a try 🚀
Publora
@danshipit Thank you! Would love to hear your feedback once you try it! 😊