The problem
Every social platform has its own API, its own OAuth flow, its own webhook format, its own rate limits, and its own error codes. If you want to reply to a comment on Instagram, respond to a Google review, and send a DM on Facebook, you need three completely separate integrations with different token refresh logic, different pagination, and different retry strategies.
Most existing tools focus on publishing and scheduling. They push content out. But the real operational work for businesses and AI agents is inbound: reading what people say, triaging it, and responding. No unified API existed for that workflow across social and review platforms.
So he built one.
How it works
One schema, every platform
Instagram calls it a "comment," Google calls it a "review," Facebook calls it a "message." SocialAPI.ai normalizes everything into consistent types with uniform fields and consistent error codes. One integration handles every platform.
75+ MCP tools for AI agents
The MCP server was built alongside the REST API because AI agents are a primary use case. Every REST endpoint has a matching MCP tool. Claude, ChatGPT, or any MCP-compatible runtime can connect without custom code.
Publish and engage
Create, schedule, and cross-post content across platforms. Then manage the conversations that follow: reply to comments, answer DMs, respond to reviews, all from the same API.
Webhooks for real-time events
Get notified instantly when someone comments, sends a DM, or leaves a review. Webhooks are delivered over HTTPS with automatic retry and exponential backoff.
Who built this
SocialAPI.ai is built and run by Erwan Prost, a French software engineer.
From the founder
Erwan Prost
Founder & engineer · France
Writing Go since 2020, mostly open-source infrastructure tooling. The one that took off is azuretls-client · 461★, a low-level HTTP/TLS client now used in production by other developers. SocialAPI.ai is what he does full-time. Built in France against the EU data-protection framework as a baseline, not a bolt-on.
Erwan
Before SocialAPI.ai
CapitalSync (2023 to 2025)
CapitalSync was a trade copier that Erwan Prost built and ran for two years, from 2023 to 2025. For two years, it replicated trading positions between accounts on MetaTrader 4, MetaTrader 5, and cTrader, in real time, with sub-second latency. Multi-tenant, billed monthly, 24/7 uptime, real money moving through it.
CapitalSync’s infrastructure included a custom Kubernetes operator written in Go that orchestrated Wine-emulated MetaTrader 4 and 5 instances. The hard part was the infrastructure. MetaTrader only runs on Windows, so to scale it Erwan wrapped each instance in Wine, packaged it in Docker, and orchestrated the pods with a custom Kubernetes operator written in Go. The operator handled lifecycle, health checks, resource limits, auto-recovery, and Prometheus metrics. A separate Go service called relay processed trading signals over NATS, with Redis caching and circuit breakers. The rest of the platform (auth, billing, admin, K8s infra) was Go too.
He shut CapitalSync down in December 2025. SocialAPI.ai is being built by the same person, with the same standards: Kubernetes-native, observability-first, infrastructure-grade Go.
Go · Kubernetes · Custom K8s operator · Wine-in-Docker · NATS pub/sub · Redis · PostgreSQL · Prometheus · Circuit breakers · Sub-second relay · Multi-tenant
Public open-source work
azuretls-client
Go461★ · 65 forks ↗
garage-ui
Go210★ ↗
SocialAPI-AI/SDKs
5 languages5 SDKs · 1 MCP server ↗
Full profile at github.com/Noooste (23 repos, 75 followers, active since 2021).
Your data is safe
SocialAPI.ai does store data to provide a fast, reliable service. But security is built into every layer, and we only keep what we need.
Encrypted at rest
All OAuth tokens are encrypted with AES-256-GCM. They are decrypted per-request and never cached in plaintext.
Minimal storage footprint
We store connected account metadata, posts, usage logs, and webhook state. Social media content like comments and DMs is fetched in real time from platform APIs and not persisted.
Hashed API keys
Keys are hashed with SHA-256 for lookup and verified with bcrypt. The raw key is shown once at creation and never stored.
HTTPS everywhere
All API traffic is encrypted in transit. Webhook deliveries use HTTPS with automatic retry.
GDPR-aligned
Built and hosted in accordance with European data protection standards. Deleting your account removes all associated data.
Supported platforms
Seven platforms are live today. Three more are in active development.
| Platform | Capabilities | Status |
|---|---|---|
| Comments, DMs, mentions, publishing | Live | |
| Comments, DMs, mentions, publishing | Live | |
| Threads | Comments, publishing | Live |
| TikTok | Publishing | Live |
| X / Twitter | Comments, DMs, mentions, publishing | Live |
| YouTube | Comments, publishing | Live |
| Telegram | Direct messaging | Live |
| Google Business Profile | Reviews, replies, local posts | Live |
| Comments, publishing | Soon | |
| Direct messaging, templates | Soon |
How SocialAPI.ai is built and run
Official platform APIs only
No reverse engineering, no scraping. Your accounts won’t get suspended because of anything we’re doing on our side. SocialAPI.ai uses only official platform APIs and does not perform reverse engineering or scraping.
Go on Kubernetes
Same stack as CapitalSync. Health checks, circuit breakers, Prometheus metrics, horizontal scaling, all the boring stuff that keeps things up at 3am.
One engineer end to end
Every connector, every webhook handler, every database migration. If something breaks, the person who wrote it is the one fixing it.
Built and hosted in Europe
Erwan is French and SocialAPI.ai is a French company. He’s spent his whole career building software inside the EU regulatory framework, so GDPR isn’t a checklist bolted on for a US market, it’s the baseline he’s always built against. Postgres and Redis run in EU regions. SocialAPI.ai is hosted in Europe and is GDPR-aligned by default.
SDKs and community
We provide official SDKs and the MCP server on GitHub. The MCP server is also listed on agent marketplaces including Smithery, Composio, MCP.so, PulseMCP, and mcpmarket.
Bug reports, feature requests, and pull requests on the SDKs are welcome. If you are building something cool with the API, I would love to hear about it.
Say hello
This is an indie project and every email gets a personal reply.