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
Congrats on shipping!
Is it possible to use Publora under the hood of my own product, white-label style? So my clients hook up their own channels, but it all sits under my account.
@timur_sekamov Thank you!
Absolutely — that's exactly the workspace flow
1. You (as the owner) purchase the channels you need.
2. Via the API you create a user and get a unique URL for channel connection.
3. Your customer follows that URL to complete OAuth and connect their channel — generating a unique channel ID.
4. Your agent then uses that channel ID + your owner API key to post.
All connected channels draw from your main channel quota, so your customers don't need their own subscriptions.
Guide: https://docs.publora.com/guides/workspace
TabAI
Is it able to learn on my taste and style of doing posts? if yes my Fable model will become CMO of my company with ur product, congrats w/ the launch anyways!!!!
Publora
@igor_martinyuk Thanks! 🙏 Honest answer — no, Publora doesn't learn your style. It's a purely technical tool: it publishes and schedules the content you pass to it across your social networks. The taste and style stay on your model's side — Publora is just the layer that ships what your agent creates.
@igor_martinyuk BTW if the "writing in my style" part is what you're after we have another product, Co.Actor, that does exactly that. It's built on top of Publora under the hood, but Co.Actor is the layer that actually learns your voice and drafts posts in your style, then Publora ships them. Kind of the perfect combo for your "AI CMO" idea 😄
The self-setup flow stood out to me - instead of pasting a config, you just give the agent the docs and let it configure itself. How reliable is that across different agents? Claude Code probably handles it cleanly, but I'm curious how it holds up with less capable ones.
Congrats on the launch!
Publora
@jared_salois Claude Code handles it really cleanly. For other agents it mostly comes down to how well they deal with tool schemas — but in practice it holds up well, and we've built a couple of fallbacks so capability isn't a blocker:
• Ready-made skills — you can just install one instead of self-configuring, e.g. our Threads skill: https://www.skills.sh/publora/skills
• Or go straight to the API — feed any agent our API docs and it'll wire itself up reliably. We put a lot of care into keeping the docs clean and clear exactly for this. https://docs.publora.com/getting-started
And we're continuously improving the docs to make the self-set
Oh yeah, this is a way to go. Not so clear from the short description how credentials are handled.
Publora
@ilya_kolesnikov1 Good point! You connect your account once via OAuth — we handle token storage and refresh automatically on our side. You only re-auth if you revoke access yourself. 😊
the full engagement loop including comments and reactions is the part that raises the most questions about intended use. posting content via API is generally accepted. automated commenting and reacting at scale is where platforms actively push back and where the ethics of agent-driven engagement get complicated. curious what the intended use case is for the comment and react features specifically and whether you've seen any platform policy pushback on those capabilities
@ansari_adin
Really thoughtful question — and honestly the one we think about the most. 🙏
You're right that there's a fine line here, and the fear people often raise is "great, now there'll be even more slop." That's not what we're building toward. Our actual focus is the operational layer: removing the mechanical friction so a person can act on their real intent fast — instead of living inside dashboards and doom-scrolling feeds to do something they already decided to do.
So the intended use for comment/react isn't spray-and-pray engagement farming. It's: you decide what's worth responding to, and the agent saves you the busywork of doing it across platforms. The judgment stays human — Publora just handles the technical/bureaucratic part of getting it out there. Same content you'd have posted by hand, minus the friction.
On policy: we run entirely on the official APIs and stay within their rules and rate limits, so we're working with the platforms, not around them. Quality-of-intent over volume is very much the line we want to stay on.
very much support the cause, coz tested around 5 different tools and none were as good at this, seemingly, simple task
it takes media professionals to make something for media to move the needle
Publora
@dowhatmatter That means a lot — and we totally feel that. Simple on the surface, surprisingly hard underneath. Thank you! 🙏
The MCP angle is what makes this genuinely interesting, most social APIs stop at "publish a post" but the full engagement loop (comment, react, mention) is what agents actually need to run a real presence. The $2.99/account pricing removes the usual "is this worth wiring up" hesitation. One question: for Instagram specifically, does it support carousel posts and reels scheduling, or only single images/text for now?
Publora
@keirodev Both Instagram features are fully supported! 😊
@eugenia_ivanova3 Perfect, that's exactly what I needed to hear :) Adding it to my stack to test for my own app's social presence. Thanks for the quick answer!
Publora
@keirodev Awesome, can't wait to hear how it goes! 🚀
Velo
Quick questions:
Do you guys also provide metrics and insights on the posts?
Currently I use Buffer for the same thing, how are you guys different from it?
@soni_karan 🙌
1) Metrics & insights — yes. You get analytics on the posts you publish through Publora: LinkedIn is the deepest right now (impressions, unique reach, reactions, comments, reshares — per-post or aggregated), and the other platforms are a bit lighter for now, with more on the way. Since it's all through the MCP, you can just ask your agent "how did my last post do?" → https://docs.publora.com/guides/linkedin-analytics
2) vs Buffer — honestly, it comes down to who we are: we're a small, fast, AI-first team (~8 people), so we move quickly, ship constantly, and build everything agent-native from the ground up rather than bolting AI on later. That speed is also why we're one of the most affordable / best-value options out there. So you get an AI-first product that evolves fast, at a friendlier price 🚀
Skylive
Congrats on the launch! 🚀 One question: how do you handle rate limits and API changes across all 10 social platforms while maintaining a single unified API? That seems like one of the hardest challenges here.
Publora
@stbenji_ That's our job — we handle all of it so you don't have to. 😊
An interesting solution; I've been waiting for something like this for a long time, especially for LinkedIn.
Using Zod is a great practice!
Tell me, do you plan to save and aggregate conversations with specific users? For example, to track the most active readers of my posts?
Publora
@peter_rudenko1 Interesting idea, but LinkedIn doesn't allow accessing readers through the API due to their privacy policy. We'd love to have that ourselves too — and if LinkedIn's rules ever change, we'll definitely build it! 😊
@peter_rudenko1 Thanks! 😊 We already collect and store analytics for posts and comments created through Publora. For LinkedIn specifically, we also support reading and replying to comments, so you can already build workflows around audience engagement.
You can find more details in our documentation here: https://docs.publora.com/endpoints/linkedin-comments
Tracking and aggregating interactions with specific users is definitely an interesting direction, especially for identifying your most engaged readers.