Zenserp

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

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

Teams use Corsair for zenserp plugin for corsair. Common builds include sync jobs, admin tooling, and agents that call Zenserp 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 Zenserp 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/zenserp in the open repo. When Zenserp 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 Zenserp data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Zenserp data on your behalf.