Memberstack Platform Help

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

1. What are you trying to do?

   • A) Manage members from your backend (create/read/update/delete) via the Admin REST API
   • B) Verify a member's JWT to gate your own API or app
   • C) React to events via webhooks (member.created, member.plan.*) — sync to a CRM/warehouse
   • D) Configure front-end auth, gating, or Stripe checkout (DOM package + data attributes)
   • E) Pick a plan / understand transaction fees
   • F) Fix a problem — webhook verification, json overwrite, member-not-found, 1.0→2.0 migration

2. Front-end or back-end? Browser auth/gating/checkout = DOM package (public key). Server-side member ops + token/webhook verification = Admin REST/Node (secret key). This decides everything.

Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.

Step 2 — Route or answer directly