Skip to main content
Full details of one topic: description, resolution criteria and sources, options with prices and backer counts, categories, the stake range it accepts, any live ruby boost, the winning option once resolved, and whether the key owner has it on their watchlist. Scope: read · Annotations: readOnlyHint REST equivalent: GET /open/v1/topics/{id}

Parameters

Returns

Everything on the list card plus description, image_urls, resolution_criteria, resolution_sources, categories, winning_option_id, invalid_reason, settled_at and is_watchlisted. Options additionally carry backers_count here (list responses omit it). A topic ruled invalid ends as status: resolved with invalid_reason set and winning_option_id null — there is no separate refunded status in 2.0.

Stake rules and ruby boost

Read these before preview_order:
  • stake_rules (v21_lmsr only; null on v2_share) — the topic’s stake rules, fixed when it was created: min_coins / max_coins bound the amount_coins a preview accepts (inclusive, whole coins; older topics are 100 / 100), default_coins is what an order stakes if amount_coins is omitted (a fallback, not a suggestion — ask the user for the amount), and rules_version is 1 for fixed-stake topics and 2 for variable-stake ones.
  • ruby_boost — the ruby boost running right now (multiplier, and ends_at, which is exclusive), or null. Orders placed, settled, or (in the app) sold while the boost is live get the multiplier.
See Rubies and positions. Example:
A 404 means the topic doesn’t exist or isn’t available to this key (moderation/privacy) — existence is deliberately not leaked. See Errors.

Example prompts

list_topic_opinions · preview_order · search_topics