Google Cloud Vision

Install corsair and @corsair-dev/googlecloudvision, add the Google Cloud Vision plugin, and connect with an API key or OAuth. Then call methods like corsair.googlecloudvision.api.files.annotate() from your app. Corsair stores tokens, and keeps each tenant isolated.

Yes. Google Cloud Vision supports an API key or OAuth. Use credentials or OAuth scopes that match what you automate. Create them in the Google Cloud Vision developer console, then paste into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Google Cloud Vision, GitHub, Notion, Stripe, and the rest. Trigger Google Cloud Vision from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for image analysis api for labeling, ocr, face detection, and visual content understanding. Common builds include sync jobs, admin tooling, and agents that call Google Cloud Vision 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 Google Cloud Vision 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/googlecloudvision in the open repo. When Google Cloud Vision 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 Google Cloud Vision data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Google Cloud Vision data on your behalf.