Admin Strategy Curation
Internal Admin Endpoints
Admin Strategy Curation
Internal-only endpoints for managing the curated strategy discovery board
POST
Admin Strategy Curation
These endpoints manage the hand-picked strategy set served by
Response: the deactivated entry.
GET /v2/discovery/strategies?collection=curated. The curated board is read
live, so changes take effect immediately — no deploy or snapshot cycle.
Auth
All routes are protected by the platform admin token:Authorization: Bearer <admin-token>Content-Type: application/json
List Active Curation Entries
GET /v1/admin/strategy-curation
Returns every active curation row (including rows outside their display
window), in editorial order.
Response:
Add A Strategy To The Curated Board
POST /v1/admin/strategy-curation
strategyId is the public strategy id (the legacy blueprint id, e.g.
01KVXD93001RE2NVTRT8A66C1C). Only public, mirrorable strategies can be
curated — the curated read filters on both, so anything else would silently
never appear.
Request:
position(optional, default0): editorial order, lower sorts firststartsAt/endsAt(optional): display window; omit either side for open-ended.endsAtmust be afterstartsAtnote(optional): internal rationaleupdatedBy(required): actor for the audit trail
Remove A Strategy From The Curated Board
DELETE /v1/admin/strategy-curation/:strategyId
Deactivates the strategy’s active curation row (rows are never hard-deleted).
The same strategy can be re-added later with a new POST.
Request:
Errors
400: validation failure, non-public strategy, non-mirrorable strategy, or an inverted display window401: missing or invalid admin token404: unknownstrategyId, or no active curation row to deactivate409: strategy is already actively curated (deactivate first to re-add)