How LazyRelay is built, in four parts. Every line below describes something it does today.
LazyRelay is a usage based social media scheduler. Connect your accounts once, schedule a post, and it goes to every destination you picked. Each destination costs 1 credit, and the credit is taken only after the platform confirms the post is live.
LazyRelay publishes to 18 distribution platforms plus WhatsApp.
WordPress, dev.to and Hashnode can publish live or save a draft, your choice for each post. A draft is never reported as live. X connects with your own X developer keys, see part 3.
WhatsApp is client messaging. It is not one of the 18 distribution platforms and is not counted as one.
Any paid plan: Growth, Pro or Pay as you go. Free accounts and accounts whose plan has lapsed cannot connect WhatsApp. You link your own Meta WhatsApp Business account, phone number and access token. They are stored encrypted, every message goes out with them, and Meta bills that account directly. LazyRelay takes no credits for WhatsApp messages and has no shared number.
All sending happens from the signed in dashboard.
A post cannot be sent to WhatsApp through the API, an API key, MCP, Zapier, bulk import or duplicate. Those routes refuse WhatsApp. You cannot send a template to someone who has not opted in, or a free form message outside the 24 hour window.
If a contact replies with only STOP, UNSUBSCRIBE, CANCEL, END, QUIT, OPT OUT, OPTOUT or STOP ALL, or Meta reports that the person stopped marketing messages, LazyRelay records the opt out and marks the contact as opted out. That record is checked again just before every send. Reply keywords are read once you point your own Meta app's webhook at LazyRelay.
Posting and checking are two separate steps. First post() sends the content to the platform. Then verifyPublished() reads it back from the platform. A post is marked live only when that read back confirms it, and the public URL of the post is stored with the result. If the read back does not confirm it, the post shows as unverified and no credit is taken.
You get a result record for each destination. It shows whether the read back confirmed the post is live, and the public URL of the post.
post() sends the content to the platformverifyPublished() reads it back from the platformA competitor blueprint is a one off teardown, not ongoing tracking. You find it under More, in Content Sources. A teardown costs 10 credits. The 10 credits are charged only when the blueprint is delivered, and a failed teardown costs nothing.
Paste a link to a public web page from a competitor. You tick a consent box before anything is sent. LazyRelay reads the public text of the page with Firecrawl, main content only, and a copy up to a day old may be used. This is landing page structure extraction: it pulls out the headings, how the page opens and its call to action links.
The extracted structure goes to Claude Sonnet 5.5, which returns two parts. It describes structure only. It does not quote the page, and its answer is rejected if it holds a link, an @mention, a claim that the page performs well, or a copied run of eight words or more from the page.
Competitor strategy map. The hook, which is one of question, statistic, bold claim, story, how to, list, problem and agitate, social proof, offer or other, with a note of up to 160 characters. Up to 8 sections in page order, each with a role label of up to 40 characters, such as Promise, Proof, Steps, Pricing or FAQ, and a summary of up to 140 characters. The call to action: its placement (top, middle, bottom, multiple or none), a style of up to 100 characters, and a count. LazyRelay counts and places the call to action links itself, so the placement and count do not come from the model.
Recommended adjustments. Three to six short adjustments of up to 160 characters each, written from the structure of that competitor page.
Also returned. The result also shows the page title.
LazyRelay has an API, and two ways to bring your own credentials.
LazyRelay has 27 MCP tools. They work as Claude Code Model Context Protocol tools, and in any other AI agent that supports MCP, such as Claude Desktop, ChatGPT, Gemini and Cursor. An agent can check platform rules, create drafts, schedule, reschedule, pause and approve posts, create client review links and read analytics. The tools schedule and manage your LazyRelay posts through the LazyRelay API. Use the hosted endpoint with sign in, or the local package with an API key. See the integration guides.
Find out what is connected and what each platform accepts before you post.
Create, schedule, edit, pause and cancel posts.
Approve waiting posts and run client review links and feedback.
Check what happened: post status and Proof of Publish, shareable proof, analytics and comments.
Connect X with the keys from your own X developer app, and WhatsApp with your own Meta WhatsApp Business credentials. Your own keys are available on Growth, Pro and Pay as you go. They are not available on Free. Calls go out under your own credentials, so X and Meta apply their rate limits and billing to your own developer accounts. Your keys are stored encrypted.
Everything above is run from one dashboard, paid for from one wallet of credits.
One wallet of credits pays for everything. Free gives you 30 credits once. Pay as you go is $15 for 300 credits that stay until used. Growth is $29 a month for 1,000 credits each cycle and Pro is $99 a month for 6,000 each cycle. Full details are on the pricing page.
Overview, Compose, Posts, Failed, Calendar, Insights, Connections and Brands are in the main bar. Content Sources, API Keys, Settings, Mentions, Bio Page and WhatsApp sit behind More.
Mentions shows the recent comments on your posts from dev.to, Hashnode, Mastodon, Bluesky, YouTube, Lemmy, WordPress, Telegram and Discord, with a note on which ones need an answer.
On paid plans LazyRelay drafts a suggested reply to new comments on Mastodon and Bluesky. Nothing is posted until you approve it, and comments about money, legal matters, security or a complaint get no draft.
On paid plans you can send a client a review link. They approve a post or leave feedback, and you can answer inside LazyRelay. Every post confirmed live can have a public proof link you can share with a client.
Keep separate brands in one account: 1 on Free, 2 on Pay as you go, 4 on Growth and unlimited on Pro.
The Free plan gives you 30 credits once at registration and up to 3 connected accounts.
LazyRelay publishes to 18 distribution platforms plus WhatsApp. The 18 are TikTok, Pinterest, YouTube, Mastodon, Bluesky, Telegram, LinkedIn, Threads, Facebook, Instagram, Discord, Tumblr, WordPress, dev.to, Hashnode, Lemmy, Slack and X. WhatsApp is client messaging and is not one of the 18.
Proof of Publish is a second step. After LazyRelay posts, it reads the post back from the platform. A post is marked live only when that read back confirms it. Otherwise it shows as unverified.
A competitor teardown costs 10 credits. The credits are charged only when the blueprint is delivered, and a failed teardown costs nothing.
LazyRelay has 27 MCP tools. An AI agent that supports MCP, such as Claude Code, can use them to schedule and manage your LazyRelay posts through the API. Use the hosted endpoint with sign in, or the local package with an API key.
LazyRelay runs on one wallet of credits. One credit publishes to one destination and is taken only after the platform confirms the post is live. Free starts with 30 credits once, and the paid plans and credit packs add more. The pricing page lists every plan.
Yes. The Free plan gives you 30 credits once at registration and up to 3 connected accounts.