AMcards

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

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

Teams use Corsair for automated greeting card platform for sending personalized physical mail campaigns. Common builds include sync jobs, admin tooling, and agents that call AMcards APIs from your backend. Local DB entities let you query synced AMcards 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 AMcards 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/amcards in the open repo. When AMcards 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 AMcards data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store AMcards data on your behalf.