For AI agents
Spaces is a messaging API and an MCP server. Follow this page in order.
Machine-readable copy: /llms.txt, /llms-full.txt, /openapi.json, /.well-known/mcp.json. The same files are on https://api.spacesos.com/llms.txt.
Plans
- Free: $0, no card, 1 connected account, 500 agent actions a month, then a hard stop.
- Paid: $49 a month for the first connected account, $29 a month for each extra. No contact limits and no contact fees. Yearly is 20% off: $470.40 and $278.40.
- A card starts a 14-day trial, or 30 days with a trial code. Paid accounts include 5,000 agent actions a month, then $1 per extra 1,000, with a spend cap and emails at 80% and 100%.
- Agencies: $29, $24, or $19 per account a month (1-19, 20-49, 50+), minimum 5 accounts, and a 30% lifetime commission on referred subscriptions.
Quickstart
- POST https://api.spacesos.com/v1/signup with the person's email.
- POST https://api.spacesos.com/v1/signup/verify with the 6-digit code. Store the spc_live_ key. It is shown once.
- If connect returns BILLING_REQUIRED, POST https://api.spacesos.com/v1/messaging/billing/checkout and give the person the url.
- POST https://api.spacesos.com/v1/messaging/accounts/connect-link with a channel. WhatsApp and Telegram use a QR code. Other channels are a sign-in, including a second factor when the platform asks. A workspace can connect more than one WhatsApp number.
- GET https://api.spacesos.com/v1/messaging/accounts.
- Add MCP:
claude mcp add --transport http spaces https://api.spacesos.com/mcp --header "Authorization: Bearer KEY"
Channels
Instagram DMs, comments, and a private reply from a comment into a DM when the platform allows it. WhatsApp with multiple numbers. LinkedIn. Messenger. Telegram. Gmail, Outlook, and IMAP as one-to-one email. Workflows are paced steps on LinkedIn, Instagram, WhatsApp, and Telegram that stop when the person replies.
Read, reply, and media
list_messaging_chats, list_messaging_messages, and get_messaging_attachment. Attachments include voice, video, GIFs, images, and files. reply_in_chat and start_chat need messages:send and an Idempotency-Key. A 429 means nothing was sent. Wait retry_after_seconds and retry with the same key.
Clients
- Claude Code and Claude Desktop: MCP url https://api.spacesos.com/mcp and Authorization Bearer.
- ChatGPT: custom MCP connector, same url and header.
- Cursor: server name spaces, same url and header.
- Grok: same url and header.
- Onboarding, no key: https://api.spacesos.com/mcp/start
Safety
Spaces reduces ban risk with enforced limits, warm-up, pacing and an automatic pause. It cannot guarantee the platform will not restrict the account. Do not work around a limit. On 429, wait retry_after_seconds and retry with the same Idempotency-Key. If the account is paused, stop. Check GET /v1/messaging/usage or the MCP tool get_messaging_usage before bulk work. A send returns account_safety with remaining today, remaining this week, paused and the reason. The ceilings are in /llms.txt.