Gladia

Install corsair and @corsair-dev/gladia, add the Gladia plugin, and connect with an API key. Then call methods like corsair.gladia.api.live.deleteSession() from your app. Corsair keeps each tenant isolated.

Yes. Gladia requires an API key from your Gladia 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 Gladia, GitHub, Notion, Stripe, and the rest. Trigger Gladia from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for gladia plugin for corsair. Common builds include sync jobs, admin tooling, and agents that call Gladia APIs from your backend.

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 Gladia 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/gladia in the open repo. When Gladia 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 Gladia data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Gladia data on your behalf.