OCR Web Service

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

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

Teams use Corsair for cloud ocr service for converting pdfs and images into searchable text content. Common builds include sync jobs, admin tooling, and agents that call OCR Web Service APIs from your backend. Local DB entities let you query synced OCR Web Service 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 OCR Web Service 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/ocrwebservice in the open repo. When OCR Web Service 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 OCR Web Service data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store OCR Web Service data on your behalf.