Necessary cookies keep Deep Pick secure. Anonymous analytics are optional.
What gets shared?
Product events only—never your email or raw account ID.
Choose your analytics settings
Deep Pick uses necessary cookies for security and account access. With your permission, we also use Google Analytics and anonymous PostHog events to improve the product. No email or raw account ID is sent.
Never manufacture a cursor and never infer an update from page order. Treat cursors as opaque, and use the complete pick embedded in each event as the latest revision.
Sealed fields stay sealedPick identity, selection, odds, units, and publish time do not rewrite when a grade appends.
Corrections stay visibleA legitimate correction emits a new event for the same stable pick ID—never a duplicate bet.
Failure is explicitIf canonical verification fails, the API returns a problem response instead of stale or invented picks.
// 1. Import history once, oldest first.
GET /api/public/v1/picks?limit=250
// 2. Follow next_cursor while has_more is true.
GET /api/public/v1/picks?limit=250&cursor=OPAQUE_CURSOR
// 3. Poll changes. Upsert event.pick by event.pick.id.
GET /api/public/v1/events?cursor=CHECKPOINT_CURSOR
// 4. Drain next_cursor, then persist checkpoint_cursor.
STABLE V1 SHAPE
Only the fields a tracker needs.
No private analysis, model prompts, internal IDs, or Battle tape.