Social & Challenges

This page documents currently implemented social surfaces and clearly separates default core routes, feature-mapped modules, and currently default-enabled unmapped modules.

Follow Graph & Profiles (Core)#

Core user-graph routes are active by default:

• GET /api/v1/users/:pubkey
• POST /api/v1/follows/:pubkey, DELETE /api/v1/follows/:pubkey
• GET /api/v1/follows?type=followers|following

Counters, Debates, and Threads (Core)#

Prediction conversations are currently modeled through counters and thread replies:

• /api/v1/commits/:id/counter, /counters, /debate
• /api/v1/commits/:id/reply, /thread, /replies
• /api/v1/threads/trending, /api/v1/threads/:id

Challenges & Events (Core)#

Challenge and event modules are enabled as core route modules:

• POST/GET /api/v1/challenges, /api/v1/challenges/:id, /api/v1/challenges/:id/enter
• POST/GET /api/v1/events, /api/v1/events/:id, /api/v1/events/:id/join, /api/v1/events/:id/leaderboard

The feed UI attempts to render a daily challenge banner when data is available; it falls back cleanly when daily data is absent.

Sharing, Proof Cards, and Embeds (Core)#

Sharing surfaces are actively implemented:

• /api/v1/reveals/:id/proof-card (+ .png, .svg)
• /api/v1/reveals/:id/share and Open Graph card endpoints
• /api/v1/embed/:type/:id, /api/v1/oembed

Referrals (Core)#

Referral endpoints are enabled by default: /api/v1/referrals/code, /stats, /rewards, and /apply. Current reward logic in source uses a flat rebate percentage in service code.

Feature-Flagged Social Modules#

These route groups exist in source but are disabled unless their feature flags are enabled:

• ENABLE_CALLOUTS — callout routes.
• ENABLE_BATTLES — battle routes.
• ENABLE_SOCIAL — collaborative/group prediction and virality modules.
• ENABLE_ENGAGEMENT — rituals, anti-dopamine, scarcity, and slow-feed modules.

Currently Default-Enabled (Unmapped) Modules#

The following modules are currently outside ROUTE_FEATURE_MAP, so they are enabled by default even when all ENABLE_* feature flags are false:

• GET /api/v1/realtime/events, GET /api/v1/realtime/feed
• GET /api/v1/users/me/notification-preferences, PUT /api/v1/users/me/notification-preferences
• GET /api/v1/weekly-prizes

Notification preferences are currently backed by an in-memory store in API route code, not persistent database storage.

Current Integration Gaps#

In this repository branch, some web components call endpoints like /api/v1/commits/:id/vouch and notification list routes that are not currently registered in services/api/src/routes. Treat those paths as in-progress.

For the full route map and auth details, see Developer API.