@caffeinelabs

extension-email-raw sends emails to multiple to, cc, and bcc recipients simultaneously. all recipients see each other, making it unsuitable for bulk service distribution. depends on extension-email backend.

extension-email provides a motoko interface for sending transactional emails via a prefabricated backend module. supports individual recipient delivery with basic ok/err result handling.

extension-object-storage enables off-chain file/object storage with on-chain references via caffeine ai, requiring coordinated backend and frontend package installation and explicit storage.externalblob typing for all file fields.

extension-posting-to-x documents x-client mops integration for caffeine builds posting to twitter, emphasizing mandatory oauth 2.0 pkce compliance and architectural guardrails against raw http anti-patterns.

extension-email-marketing manages subscriber lists and sends topic-based marketing emails with mandatory unsubscribe links, requiring prior email verification. incomplete implementation details and vague operational guidance limit practical utility.

extension-user-approval provides approval workflows for user access control within caffeine ai, requiring prior extension-authorization setup and leveraging a prefabricated approval module.

Make a canister's data queryable by the Caffeine Data Intelligence agent. Use whenever an app stores structured data (Maps/Lists/arrays of records) that should…

Admin-only paginated viewer for stable canister state. Use whenever the user asks for a viewer, dashboard, debug panel, or admin browse over backend data —…

MANDATORY recipe for every Caffeine build that calls OpenAI (ChatGPT, GPT-4o, an LLM, a chatbot, embeddings). The ONLY supported path is the `openai-client`…

Payment support based on Stripe, supporting credit cards and debit cards

Core infrastructure providing backend connection configuration, storage client, and React app entry point.

Authorization system with role-based access control. Must-have for all apps that manage personal or access-restricted data.

HTTP outcalls performed by the backend canister (not in the frontend).

Support for sending an email with a link the recipient can click to prove they own the email address.

Requests invite-link / RSVP based access where guests can submit responses without login while admin can view responses with login.

Web-camera support.

QR code scanner using the camera.

Support for organising events/meetings and sending invitations by email.