Search1API

Install corsair and @corsair-dev/search1api, add the Search1API plugin, and connect with an API key. Then call methods like corsair.search1api.api.account.health() from your app. Corsair syncs data per tenant.

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

Teams use Corsair for live web search, crawl, extraction, and site-wide data in one api for ai agents. Common builds include sync jobs, admin tooling, and agents that call Search1API APIs from your backend. Local DB entities let you query synced Search1API 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 Search1API 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/search1api in the open repo. When Search1API 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 Search1API data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Search1API data on your behalf.