Starton

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

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

Teams use Corsair for web3 backend for deploying and calling smart contracts, managing wallets, watching blockchain events, and pinning files to ipfs. Common builds include sync jobs, admin tooling, and agents that call Starton APIs from your backend. Local DB entities let you query synced Starton 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 Starton 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/starton in the open repo. When Starton 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 Starton data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Starton data on your behalf.