What is Saperly (SMS / text)?
Saperly (SMS / text) is a communication tool. With OSP.net, your AI agent connects to it directly so it can act on your behalf instead of just answering questions about it.
What your OSP agent can do with Saperly (SMS / text)
- Answer inbound SMS / text through your agent
- Use the same agent, memory and tools as every other channel
How to connect Saperly (SMS / text)
- Note: this connects Saperly for SMS / TEXT only. Saperly lines have three modes — Audio (real-time voice over websocket), Webhook (SMS + webhooks over HTTPS), and Hosted. Our bridge is HTTP, so it supports Webhook mode (SMS/text) only. For phone VOICE, use Vapi above (Saperly's websocket voice isn't supported yet).
- 1) Create a Saperly account at saperly.com. saperly.com
- 2) Create a line / number — and when asked for the mode, choose WEBHOOK (not Audio or Hosted). Webhook mode is the SMS/text-over-HTTPS mode our bridge speaks.
- 3) Give the line a name that matches your OSP agent, so its identity stays consistent across channels.
- 4) In the line's settings, paste THIS exact URL as the Webhook URL:
- 5) Create / save the line, then copy its Line ID from the line's settings.
- 6) Open the dashboard's API section and copy your API key.
- 7) Back here: paste your API key and Line ID, then Connect. Optional but recommended for production: copy the line's webhook signing secret and paste the SAME value above — the bridge then rejects any turn whose signature doesn't match. Text your Saperly number to test.
Security: Saperly here is for SMS / text; for phone VOICE use Vapi (Saperly's real-time voice is websocket-based and not supported yet). Name your Saperly line to match your OSP agent so its identity stays consistent. Your Saperly API key and signing secret are stored encrypted and injected at runtime — never logged or shown again. The bridge only ever relays to YOUR agent (resolved from the line id) and verifies the per-line signing secret on every turn. Rotate the key or signing secret any time from your Saperly dashboard.
Related communication integrations
Frequently asked questions
- Can OSP.net connect to Saperly (SMS / text)?
- Yes. Saperly (SMS / text) is a native OSP.net integration — you bring your own Saperly (SMS / text) key or token, paste it in your dashboard, and your agent restarts live.
- What can my OSP agent do with Saperly (SMS / text)?
- Connect a Saperly line in Webhook mode so your agent answers SMS / text. BYO Saperly account + number. (For phone VOICE, use Vapi above — Saperly's real-time voice is websocket-based and not supported yet.) Specifically: Answer inbound SMS / text through your agent; Use the same agent, memory and tools as every other channel.
- Is Saperly (SMS / text) a native integration or via the gateway?
- Saperly (SMS / text) is a native, baked-in integration. You connect it with your own credentials, which are stored in an encrypted vault and injected only at runtime.
- Is my Saperly (SMS / text) data secure with OSP.net?
- Yes. Your Saperly (SMS / text) credentials live in an encrypted secrets vault, are injected only at container runtime, and are never written to disk in plaintext or used to train any model. Each customer runs in a fully isolated instance.