Octen

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

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

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