Zernio is a single REST API that lets software products and AI agents publish, schedule, message, and run ads across sixteen social platforms and seven ad networks , with a hosted MCP server so agents in Claude Desktop, Cursor, or similar clients can take those actions in natural language . The pitch to builders is straightforward: rather than chase individual Meta, TikTok, LinkedIn, and WhatsApp integrations, teams ship one integration and let Zernio absorb the platform reviews, token rotations, media transcoding, and rate limits . The launch lands as more products embed autonomous marketing agents and need a reliable way for those agents to actually reach customers on owned and paid channels.
Beyond posting, the surface area covers comments and DMs, analytics and webhooks, paid campaigns across managers like Meta, Google, TikTok, LinkedIn, Pinterest, and X Ads, and a communications layer that includes WhatsApp, SMS, and voice calls routed into a single inbox. There is also a Blogs API for WordPress and Shopify. Customers listed on the site include Vibiz and HeyMark, with HeyMark described as an AI marketing agent that replaced months of Meta Graph API work and queue infrastructure with a single integration.
Zernio is built by a nine-person bootstrapped team based in Spain, founded by Miki (Miquel) Palet, who previously ran a VC-backed company before leaving to build this one . The company leans hard into developer ergonomics, with a public changelog, status page, and full logs for every call made on a customer's behalf, and a sign-up flow designed to get a key and a first API call out in minutes .
Comments (11)
Sign in to join the discussion.
N
Nadia Oyelaran8d ago
Repositioning three months in is such a founder flex. Either you saw something nobody else did or you're about to pivot again in six weeks, excited to find out which.
H
Hiro T.8d ago
ok wait, same API for ads AND WhatsApp AND calls? that's either the cleanest abstraction of 2025 or the leakiest. no in between.
T
Tanvir Rahman8d ago
Before my team even looks at this: SOC2? Data residency for EU WhatsApp traffic? Who owns the Meta Business account when an agent is pushing campaigns?
M
Maja Kovač8d ago
Curious how deep the docs go for the agent-calling-agent case. If I have to read a Loom to understand your webhooks I'm closing the tab.
K
kenji8d ago
The tweet copy has that broken-line cadence everyone copies from the same three accounts now. Works, but you can see the template.
L
Luca P.8d ago
sorry naive question but if the agent runs the ads and the agent writes the copy and the agent reads the analytics, who gets fired when CAC blows up
O
Ophelia Nwosu8d ago
The real question nobody's asking: who holds the phone number sending the WhatsApp messages. Distribution rails always have a boring owner behind them and that's where the margin lives.
Y
yusuf.exe8d ago
This is the last marketing stack anyone will ever log into. The next ten will be agents poking Zernio's API at 3am while the founder sleeps.
T
Tomás Albuquerque8d ago
agents running ad spend without an on-chain settlement layer is wild to me. you're one rogue GPT-5 away from needing programmable budgets.
P
Priya Venkatesan8d ago
Would love to see the funnel from 'agent launches ad' to 'human replies in WhatsApp'. That handoff is where every multi-channel tool I've tried quietly dies.
F
Finn Haugeland8d ago
Building something adjacent in the outbound space and honestly the 'same API' line is the right wedge. We went channel-by-channel and I regret it daily.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Zernio
Marketing infrastructure for products and agents
Marketing infrastructure for products and agents
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Zernio is a single REST API that lets software products and AI agents publish, schedule, message, and run ads across sixteen social platforms and seven ad networks , with a hosted MCP server so agents in Claude Desktop, Cursor, or similar clients can take those actions in natural language . The pitch to builders is straightforward: rather than chase individual Meta, TikTok, LinkedIn, and WhatsApp integrations, teams ship one integration and let Zernio absorb the platform reviews, token rotations, media transcoding, and rate limits . The launch lands as more products embed autonomous marketing agents and need a reliable way for those agents to actually reach customers on owned and paid channels. Beyond posting, the surface area covers comments and DMs, analytics and webhooks, paid campaigns across managers like Meta, Google, TikTok, LinkedIn, Pinterest, and X Ads, and a communications layer that includes WhatsApp, SMS, and voice calls routed into a single inbox. There is also a Blogs API for WordPress and Shopify. Customers listed on the site include Vibiz and HeyMark, with HeyMark described as an AI marketing agent that replaced months of Meta Graph API work and queue infrastructure with a single integration. Zernio is built by a nine-person bootstrapped team based in Spain, founded by Miki (Miquel) Palet, who previously ran a VC-backed company before leaving to build this one . The company leans hard into developer ergonomics, with a public changelog, status page, and full logs for every call made on a customer's behalf, and a sign-up flow designed to get a key and a first API call out in minutes .
Comments (11)
Repositioning three months in is such a founder flex. Either you saw something nobody else did or you're about to pivot again in six weeks, excited to find out which.
ok wait, same API for ads AND WhatsApp AND calls? that's either the cleanest abstraction of 2025 or the leakiest. no in between.
Before my team even looks at this: SOC2? Data residency for EU WhatsApp traffic? Who owns the Meta Business account when an agent is pushing campaigns?
Curious how deep the docs go for the agent-calling-agent case. If I have to read a Loom to understand your webhooks I'm closing the tab.
The tweet copy has that broken-line cadence everyone copies from the same three accounts now. Works, but you can see the template.
sorry naive question but if the agent runs the ads and the agent writes the copy and the agent reads the analytics, who gets fired when CAC blows up
The real question nobody's asking: who holds the phone number sending the WhatsApp messages. Distribution rails always have a boring owner behind them and that's where the margin lives.
This is the last marketing stack anyone will ever log into. The next ten will be agents poking Zernio's API at 3am while the founder sleeps.
agents running ad spend without an on-chain settlement layer is wild to me. you're one rogue GPT-5 away from needing programmable budgets.
Would love to see the funnel from 'agent launches ad' to 'human replies in WhatsApp'. That handoff is where every multi-channel tool I've tried quietly dies.
Building something adjacent in the outbound space and honestly the 'same API' line is the right wedge. We went channel-by-channel and I regret it daily.