Docs

Quickstart

1. Create an account with your email and the code we send.
2. In the dashboard, connect WhatsApp (scan a QR code), or Instagram, LinkedIn, Messenger or X (sign in).
3. Create an API key. It starts with spc_live_ and is shown once.
4. Add the MCP server to your agent, or call the REST API.

MCP server: https://api.spacesos.com/mcp · REST base URL: https://api.spacesos.com/v1 · Auth: Authorization: Bearer spc_live_xxxxxxxxxxxxxxxx

Sign up and set up from an agent

An agent can do the whole setup over the API or MCP. Only two steps need the person: reading the code from their inbox, and opening the links to add a card and connect an account.

1. POST /signup with the email (or the create_account tool). We email a 6-digit code.
2. POST /signup/verify with the code (or verify_account). You get an API key.
3. POST /messaging/billing/checkout (or create_messaging_billing_checkout) returns a link. The person adds a card to start the 14-day trial. The subscription renews automatically. Connect an account only after Checkout finishes.
4. POST /messaging/accounts/connect-link (or create_messaging_connect_link) returns a link where the person scans a QR code or signs in.
5. GET /messaging/accounts (or list_messaging_accounts) confirms the account is live. Keys: GET, POST and DELETE /keys.

Set me up on Spaces so you can read and send my messages. Instructions: https://www.spacesos.com/llms.txt

Start the trial and connect, with a key

curl -X POST https://api.spacesos.com/v1/messaging/billing/checkout \
  -H "Authorization: Bearer spc_live_xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{ "success_url": "https://app.spacesos.com/dashboard", "cancel_url": "https://app.spacesos.com/dashboard" }'

curl -X POST https://api.spacesos.com/v1/messaging/accounts/connect-link \
  -H "Authorization: Bearer spc_live_xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{ "channel": "whatsapp" }'

Connect your agent

The MCP server gives your agent tools to list accounts and chats, read messages, reply and start chats.

claude mcp add --transport http spaces https://api.spacesos.com/mcp --header "Authorization: Bearer spc_live_xxxxxxxxxxxxxxxx"

Which key permissions do I need?

New keys can read and send. A read-only key is enough for agents that only summarise or search your messages.

MCP tools

Two servers. https://api.spacesos.com/mcp/start needs no key and signs people up. https://api.spacesos.com/mcp takes Authorization: Bearer spc_live_xxxxxxxxxxxxxxxx and does everything else. Each tool describes its own limits, so Claude and Grok can plan around them.

REST API

Every request needs your key. Account ids come from GET /messaging/accounts.

List chats

curl "https://api.spacesos.com/v1/messaging/accounts/ACCOUNT_ID/chats?limit=20" \
  -H "Authorization: Bearer spc_live_xxxxxxxxxxxxxxxx"

Reply in a chat

curl https://api.spacesos.com/v1/messaging/accounts/ACCOUNT_ID/chats/CHAT_ID/messages \
  -H "Authorization: Bearer spc_live_xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: reply-7781" \
  -d '{ "text": "Thanks, see you at 3." }'

Start a WhatsApp chat

curl https://api.spacesos.com/v1/messaging/accounts/ACCOUNT_ID/chats \
  -H "Authorization: Bearer spc_live_xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-1042-confirmation" \
  -d '{ "to": { "phone": "+15551234567" }, "text": "Your order is ready." }'

Every send needs an Idempotency-Key (8 to 128 letters, digits, dots, dashes or colons). Retrying with the same key never sends twice. If we cannot tell whether a message went out, the send is marked UNKNOWN and is not retried for you.

Limits

Every account stays inside the limits each channel allows, enforced on our side for every key and every agent, however it is prompted. New accounts start lower and warm up over four weeks. A customer can set a lower cap. The cap cannot go above these ceilings.

What each channel can do

Keeping your accounts safe

Spaces reduces ban risk with enforced limits, warm-up, pacing and an automatic pause. It cannot guarantee the platform will not restrict the account. These limits apply to the API and to MCP. A 429 means nothing was sent. Wait retry_after_seconds, then retry with the same idempotency key. A send includes account_safety (remaining today, remaining this week, whether sending is paused, and why). New chats on a fresh account ramp up over four weeks. The same cold text cannot be sent to many people. If someone says stop, later sends to that chat are refused. If the account needs a checkpoint, new credentials, or is restricted, sending pauses until it is reconnected. You can read current usage with GET /messaging/usage.

LinkedIn actions

Profile lookups on other channels: up to 100 a day on WhatsApp and 50 a day on Instagram, Messenger and X.

Replies in existing chats are never held back by the first-week limits. Over a limit you get 429 with a Retry-After header and retry_after_seconds in the body; nothing was sent. Agents should wait that long and try again. See your live numbers with GET /messaging/usage or on the dashboard.

Errors

Pricing and channels

Free is $0, no card, one account, and 500 agent actions a month. Paid is $49 a month for the first connected account and $29 for each extra, with no contact fees. A card starts a 14-day trial, or 30 days with a trial code. The agent guide is at /docs/agents.