Hugging Face

Install corsair and @corsair-dev/huggingface, add the Hugging Face plugin, and connect with an API key or OAuth. Then call methods like corsair.huggingface.api.account.deleteNotifications() from your app. Corsair stores tokens, and syncs data per tenant.

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

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

Teams use Corsair for ai community hub for models, datasets, inference apis, and machine learning deployments. Common builds include sync jobs, admin tooling, and agents that call Hugging Face APIs from your backend. Local DB entities let you query synced Hugging Face 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 Hugging Face 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/huggingface in the open repo. When Hugging Face 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 Hugging Face data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Hugging Face data on your behalf.