Browse AI

Install corsair and @corsair-dev/browseai, add the Browse AI plugin, and connect with an API key. Then call methods like corsair.browseai.api.monitors.create() from your app. Corsair syncs data per tenant.

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

Teams use Corsair for no-code web scraping robots for monitoring sites and extracting structured data. Common builds include sync jobs, admin tooling, and agents that call Browse AI APIs from your backend. Local DB entities let you query synced Browse AI records without hitting the API on every read.

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