Messaging for companies that build AI agents
If you build AI agents that act for your users, Spaces is how those agents reach WhatsApp, Instagram, LinkedIn and Facebook Messenger. Each user connects their own accounts inside your app, and your agent uses every Spaces tool for them through the REST API or the MCP server.
You add Spaces once, as a partner, and your users never sign up with Spaces or add a card. Partner accounts are in early access. To become a partner, email hello@spacesos.com.
What your users get on each channel
- WhatsApp: Your user links their number with a QR code. Your agent reads their chats, replies, sends files and schedules messages for them.
- Instagram: Your agent answers direct messages and comments, and can send a private reply from a comment where Instagram allows it.
- LinkedIn: Your agent answers messages, looks up profiles and sends careful one-to-one messages and connection requests inside LinkedIn’s limits.
- Facebook Messenger: Your agent replies in Messenger on your user’s personal Facebook account.
Spaces works with Instagram, WhatsApp, LinkedIn, Facebook and TikTok (coming soon). On Facebook, that means Messenger on a personal Facebook account.
Your user, to your agent: Answer anyone who asks about the flat on Elm Street, and tell me who wants a viewing.
Enquiry on WhatsApp: Is the flat on Elm Street still available?
Your agent, through Spaces: It is, from 1 December. Viewings are Thursday at 5 or Saturday at 11. Which suits you?
Your agent, to your user: Arjun would like the Saturday viewing. Shall I confirm it?
Built for agents
A user key works with every Spaces tool, route and limit, exactly as in the main docs. Retries are safe with an idempotency key, so a timed-out send never goes out twice, and a request over a limit is refused with the time to wait.
Each key belongs to one user. It cannot reach another user’s messages, a leaked key exposes one user only, and you can revoke one user’s access without touching the rest. A key with the draft scope writes messages that wait for your user to approve them.
How to build it in
- Become a partner. Sign up on spacesos.com and email hello@spacesos.com with your workspace and the domains your app runs on. You get a partner key that manages your users.
- Create a Spaces user for each of your users. Use your own id for them. The call is safe to repeat.
- Give your agent a user key. Choose read, send or draft scopes, and point your agent at the MCP server or the REST API with that key.
- Send your user a connect link. Spaces shows your name and logo and tells them, in plain words, that your AI agent will read and send messages through the account.
- Listen and test. Register one webhook for every user’s events, connect a test account and let your agent answer a real message.
Every partner endpoint is in the partner docs, and the tools your users’ keys can use are in the main docs.
What stays with your users
Your product decides how much your users automate. Spaces gives you the controls:
- user keys with read, send or draft scopes, so messages can wait for a person to approve them
- caps for each user on accounts, sends, new chats and monthly actions, lower than Spaces’ own limits
- pausing and resuming any user, with nothing sent while they are paused
- disconnecting one account, or deleting a user and their messages for good
- usage for each user, each month
Safety and limits
Spaces enforces each platform’s limits on every connected account, for every key. Your product cannot raise them. You can set lower caps for each user, never higher, and pause any user. Nothing is sent while a user is paused.
Agents do best with conversations people start, and with people who expect to hear from your user. Spaces lowers the risk with limits, pacing and warm-up, and pauses sending if an account shows signs of a restriction. No tool can promise that a platform will never restrict an account, and Spaces does not either.
- A reply to someone who wrote in is never held back by the daily limits, so customers get answers from the first day. Only messages that are not replies to someone who wrote in count toward the messages a day, which rise each week of the warm-up.
- Instagram replies to people who wrote in: no daily limit, at least 15 seconds apart.
- LinkedIn: up to 100 new conversations and 100 messages a day, at least 20 seconds apart.
Every channel’s limits are on sending limits, and how Spaces protects accounts is on account safety.
FAQ
Does my agent need a special SDK?
No. Any agent that can use an MCP server or call a REST API works, with the user’s key.
Do my users need a Spaces account?
No. You create a Spaces user for each of them with your partner key, and they never sign up on spacesos.com or add a card.
Can my user approve messages before they go out?
Yes. Give the agent a key with the draft scope, and every message waits for a person to approve it.
What happens if my agent sends too much?
Spaces enforces per-account limits for every key. Over a limit the request is refused and nothing is sent.
Which channels can my users connect?
Spaces works with Instagram, WhatsApp, LinkedIn, Facebook and TikTok (coming soon). On Facebook, that means Messenger on a personal Facebook account.
How is a partner account priced?
You are billed monthly for your users’ connected accounts and actions. The partner rates are in the partner docs, and the plans for single businesses are on the pricing page.
Built for
Read more
- Partner docs
- Docs
- Webhooks
- Pricing
- Connect your AI agent
- Features
- How Spaces keeps accounts safe
- Sending limits
Other use cases: ATS software, CRM software, Outreach software, or see all use cases.
Start building
Start with a workspace of your own to try the API, then email hello@spacesos.com to become a partner.