Saperly

Install corsair and @corsair-dev/saperly, add the Saperly plugin, and connect with an API key. Then call methods like corsair.saperly.api.assistant.answer() from your app. Corsair verifies webhooks, and keeps each tenant isolated.

Yes. Saperly requires an API key from your Saperly account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Saperly, GitHub, Notion, Stripe, and the rest. Trigger Saperly from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for phone numbers, voice, and sms for ai agents. the workspace is resolved from a bearer api key. Common builds include sync jobs, admin tooling, and agents that call Saperly APIs from your backend. Webhook handlers react to Saperly events and fan out to Slack, email, or other plugins in the same tenant.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Saperly API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/saperly in the open repo. When Saperly ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Saperly data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Saperly data on your behalf.