[ Removed by Reddit ]
[ Removed by Reddit on account of violating the content policy. ]
[ Removed by Reddit on account of violating the content policy. ]
Before: upload video → rewrite caption for each platform → check character limits → convert carousel to video for TikTok → adjust hashtags × 9 → schedule one by one.
After: one prompt, Claude handles the rest.
Platforms: Instagram, TikTok, LinkedIn, X, YouTube, Threads, Pinterest, Bluesky, Reddit.
Works with both Claude Code and Cowork. Here's what happens when you run it:
Two things you need:
Full skill files on Zernio's GitHub.
Two hours a week. That's what cross-platform posting actually costs - rewriting captions, adjusting hashtags, converting carousels to video, checking character limits. Per platform. Every time.
So we built an agent (Claude Skill) that takes one piece of content and handles all of it:
Five minutes instead of two hours. Here's the short version of how it works.
You connect your social accounts, drop in an asset with a simple prompt ("post this to Instagram, TikTok, and LinkedIn, optimized for each")
The agent generates everything (captions, hashtags, first comments) and shows you a preview before anything goes live. You approve, it schedules.
Two tools you need:
- Zernio API key
- Claude desktop (Caude or Cowork)
- cost: Claude Pro ($20/mo) + Zernio (2 social platform are free, 9 platform - $42/mo) = $62/mo for full automation.
Full walkthrough: https://github.com/Enriquemarq1/zernio-library-skills/tree/main
[ Removed by Reddit on account of violating the content policy. ]
Meta launched something today that's mostly been covered in developer circles but has implications for anyone managing Meta ad campaigns at scale: a command-line interface (CLI) for creating and managing ads.
So instead of clicking through Ads Manager, you can type commands in a terminal to create campaigns, pull performance data, manage product catalogs, and set up conversion tracking.
Who this is actually for:
What it doesn't do (yet):
The bigger picture:
This is part of a trend: ad platforms are opening up programmatic access because AI agents and automation tools need it. Meta is acknowledging that the future of ad management isn't clicking buttons, it's APIs and CLIs that machines can talk to.
If you're already running cross-platform campaigns and want this kind of programmatic control across Meta + Google + TikTok + LinkedIn + Pinterest + X, that's what we're building at Zernio. One API, ads go live immediately, no per-platform setup.
Meta launched something today that's mostly been covered in developer circles but has implications for anyone managing Meta ad campaigns at scale: a command-line interface (CLI) for creating and managing ads.
So instead of clicking through Ads Manager, you can type commands in a terminal to create campaigns, pull performance data, manage product catalogs, and set up conversion tracking.
Who this is actually for:
What it doesn't do (yet):
The bigger picture:
This is part of a trend: ad platforms are opening up programmatic access because AI agents and automation tools need it. Meta is acknowledging that the future of ad management isn't clicking buttons, it's APIs and CLIs that machines can talk to.
If you're already running cross-platform campaigns and want this kind of programmatic control across Meta + Google + TikTok + LinkedIn + Pinterest + X, that's what we're building at Zernio. One API, ads go live immediately, no per-platform setup.
I’m part of a small team (5 people, bootstrapped, fully profitable) working on Zernio. We build a unified API for social media platforms, and we just added Discord.
Posting here because the multi-server use case is where this actually gets interesting.
If you run more than one Discord server, you probably know the drill:
copy message → switch server → tweak embed → paste → send → repeat 😅
And scheduled posts? Even worse.
Set a reminder, forget anyway, post late, or not at all.
What we built:
A REST API where each server = an account.
You send one request with multiple accounts, and it posts everywhere at once.
What that looks like in practice:
There’s a free tier (no card).
Curious what people think (especially if you’re managing multiple servers already). Does this actually solve a real pain, or is it just “nice but unnecessary”?
Hey builders!
We’re a small bootstrapped team at Zernio building a unified API for social platforms, and we just added Discord as our 15th integration.
Wanted to share this here because the approach is kinda different from the usual Discord bot setup, and I’m curious if this actually clicks with people who’ve built bots before.
The idea:
If you only care about sending stuff out (announcements, embeds, polls, forum posts), why do you need to deal with gateways, heartbeats, sharding, or running a bot 24/7?
Feels like overkill, right? So we tried to strip all that away.
What we built:
You invite our bot to your server via a one-click OAuth flow, then hit a REST endpoint.
No Discord Application to create, no intents to request, no WebSocket to maintain.
What you can do with it:
We’ve got a free tier (no credit card or anything). Would love honest feedback, especially from people who’ve dealt with Discord bots before.