Community quest and XP platform (formerly Crew3). Run sprints, leaderboards, and reward loops with off-chain XP that bridges to onchain claims.
- 01Discord/Telegram community quests
- 02XP and leaderboard sprints
- 03ambassador programs
- 04automated quest verification via webhooks
- 05airdrop allocation by engagement
| Variable | Scope | Description |
|---|---|---|
| ZEALY_API_KEY | Server | Zealy v2 API key generated from community settings. |
| ZEALY_SUBDOMAIN | Server | Community subdomain (e.g. `myproject` from `zealy.io/c/myproject`). |
Use Zealy for community quests and XP. Authenticate REST calls with header `x-api-key: $ZEALY_API_KEY` against `https://api-v2.zealy.io/public/communities/{subdomain}` — list quests via `GET /quests`, create via `POST /quests`, and look up claimed quests via `GET /reviews/claimed-quests-lookup`. For custom verification, configure an API quest pointing to your `POST /verify` endpoint that receives `{ userId, communityId, subdomain, questId }` and must respond with HTTP 200 (success) or 400 (failure) within 10 seconds.
- ⚑Public API is capped at 50 requests/sec — enterprise plan required for higher throughput.
- ⚑API quest verification endpoints must respond within 10 seconds or Zealy treats the call as failed.
- ⚑Only HTTP 200 and 400 are accepted as valid responses; 5xx and timeouts are silently retried and can double-count XP if your endpoint isn't idempotent.
- ⚑XP is off-chain — bridging to onchain rewards requires a separate snapshot + Merkle distributor or Sablier-style stream.
- ⚑Sybil signals (unique IP, captcha, Discord age) are admin-tunable but not enforced by default; enable Zealy Connect or wallet binding for serious campaigns.
- ⚑Free tier limits the number of active quests and reviewers; large communities need the Pro/Enterprise tiers.