One engine. Nine networks. Zero copy-paste mornings.
CoreLayerEngine writes, designs and schedules for 9 networks — Instagram, Facebook Pages, LinkedIn, TikTok, Pinterest, Google Business Profile, X, Threads, and YouTube — each with platform-true formatting, its own learned best-time model, and per-channel analytics. Channels connect by OAuth in about a minute and tokens stay fresh automatically. Instagram, LinkedIn and YouTube post by themselves the moment you approve. On the rest, the engine does every other part of the job and the approved post arrives in your post kit as a finished image and caption you send in one tap. TikTok has its own version of that: finished videos land as ready-to-post drafts in your inbox until TikTok audits the app for direct publishing — the console says so before you post, not after.
Publishing automatically today: Instagram, LinkedIn and YouTube. What the rest are waiting on is not the same thing. Facebook Pages is a separate permission in the same Meta App Review and has not been granted; Threads is a separate Meta app with its own App Review, and that has not been granted either. TikTok has its own Content Posting API audit to pass before anything posts directly. Pinterest needs Standard access; Google Business Profile needs Business Profile API access approved for the project. The X gate is ours, not the platform’s: we have to take up the paid access tier that media upload needs, and without it the console falls back to text-only rather than failing. Until direct publishing is switched on for a network, that channel runs in export mode: it waits in your approval queue, and the engine still writes the post, designs the image and picks the hour, and the post kit hands you the finished image and caption to send in one tap from your phone. WhatsApp Status is export mode permanently and by design — no API publishes a Status.
Every network, in its own format
TikTok
Short-form video from the reel builder, trend-aware ideation. Delivered through TikTok’s official Content Posting API — as a ready-to-post draft in your TikTok inbox until TikTok audits the app, then direct publishing.
Learn more →YouTube Shorts
Vertical video built in the reel studio, titled, described and ready to upload.
Learn more →WhatsApp Status
We design the Status image and write the caption in 40 languages. You post it — no API publishes a Status.
Learn more →What if my channel isn't on the list?
Nothing blocks. Any unconnected or unsupported channel gets an export pack: rendered creative, caption, hashtags, and per-platform variants, ready to paste. You keep the engine's ideation and design even where APIs don't reach.
How do connections work?
- ✓OAuth, not passwords — you grant scoped access on the platform's own consent screen; revoke anytime
- ✓Automatic token refresh — a background sweep keeps long-lived tokens alive so channels don't silently die
- ✓Connection health — status per channel, with reconnect prompts before failures, and a go-live smoke test that verifies your setup end to end
- ✓Demo mode — explore every feature with labeled demo connections before touching a real account
Workflow & data integrations
Slack
Approval buttons on proposals; approve or reject from chat.
Microsoft Teams
Proposal notifications via incoming webhook.
Email & WhatsApp digests
Daily, weekly, and monthly summaries (monthly as PDF).
SMS
Login codes and reminders.
Outbound webhooks
Signed (HMAC-SHA256) events for proposals, publishes, approvals, leads, and crises; point them at any CRM or automation platform.
REST API v1
Generate, schedule, publications, leads, analytics; OpenAPI spec published.
Docs & resources →Sign in your way
Google, Facebook, Discord, LinkedIn, or X single sign-on; email and password with optional TOTP two-factor; or phone number with SMS one-time code.
Frequently asked questions
Which social media platforms does CoreLayerEngine support?+
The engine plans, writes, designs and schedules for nine: Instagram, Facebook Pages, LinkedIn, TikTok, Pinterest, Google Business Profile, X, Threads, and YouTube. None of them posts on its own yet: an approved post lands in your post kit as a finished image and caption you send in one tap, until direct publishing is switched on for that network. What each one is waiting on differs. Meta's App Review covers Instagram and Facebook Pages and is still in progress, and Threads is a separate Meta app whose own App Review has not been granted either; YouTube needs Google's OAuth verification, Pinterest needs Standard access, and Google Business Profile needs Business Profile API access approved for the project. The X gate is ours, not the platform's: we have to take up the paid access tier that media upload needs. WhatsApp Status is a kit, not a publish target — no API posts a Status. TikTok videos arrive as ready-to-post drafts in your TikTok inbox until TikTok audits the app for direct publishing. Listening additionally covers Reddit and news. Unsupported channels still work via ready-to-paste export packs.
Do I need separate accounts or apps per platform?+
No. Connect each network once by OAuth from the console; the engine handles per-platform formatting, sizing, and scheduling from a single approval flow. Tokens refresh automatically in the background, and a health view flags any connection needing attention.
Can each platform have different posting times?+
Yes — that's the default. The engine learns a separate weekday-by-hour engagement heatmap per channel from your audience's real behavior, schedules into each channel's peaks, and revalidates as new results arrive. Your LinkedIn peak and Instagram peak are rarely the same.
Is there an API for custom integrations?+
Yes. REST v1 covers content generation, scheduling, publication history, leads, and analytics with bearer-key auth and per-plan quotas; signed outbound webhooks push events to your systems in real time. The OpenAPI spec is public at app.corelayerengine.com/api/v1/openapi.json.