new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Better Auth · Plugins · all subjects

creem/configuration

6 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Creem server plugin configuration

Configure the Creem plugin on the server using `creem({apiKey, webhookSecret, testMode, defaultSuccessUrl, persistSubscriptions})`. The apiKey is required. webhookSecret is optional and enables webhooks when provided. testMode defaults to false. defaultSuccessUrl is the redirect URL after successful payments. persistSubscriptions defaults to true and enables database persistence.

Creem client plugin configuration

Configure the Creem plugin on the client using `creemClient()` within `createAuthClient()`. For React with enhanced TypeScript support, use `createCreemAuthClient()` wrapper which provides better IntelliSense and autocomplete.

Creem database migration

If using database persistence (persistSubscriptions: true), run `npx auth migrate` or `npx auth generate` to generate and run the database schema.

Creem webhook endpoint URL

Configure the webhook endpoint in the Creem dashboard to point to `https://your-domain.com/api/auth/creem/webhook`, where `/api/auth` is the default Better Auth server path.

Creem webhook secret configuration

Copy the webhook signing secret from Creem and add it to environment variables as `CREEM_WEBHOOK_SECRET`. Update the server configuration to include this secret in the creem() plugin options.

Creem database mode vs API mode

Database mode (persistSubscriptions: true, default) stores subscription data locally - fast access checks, offline capability, SQL queries, automatic sync via webhooks, trial abuse prevention. API mode (persistSubscriptions: false) requires API calls for each check but needs no database schema. API mode has limited functionality and no built-in trial abuse prevention.

Give your agent this brain