Skip to content

Subtopics actions

2 actions. Every field marked Required must be sent; account, dryRun, idempotencyKey, confirmCredits and quoteId are the control fields every surface adds.

subtopics.list · read

The sub-topics inside the user’s niche that Xholic spreads their posts across: active ones (approved), trial ones (new lanes Xholic is testing in the weekly plan while the account is early; they become active once they work, or drop out when they don’t), suggested ones (proposed by Xholic, waiting for the user’s yes) and, with includeRemoved, removed ones. Each active one has its coverage (posts published and queued in the last 14 days), its lesson when it has results (how posts on it do against the user’s usual, like format lessons) and how many posts are taking off on it right now among the user’s creators, peers and the Library (beating their author’s usual; stored data only). Pass includeTrends for those posts. Use the least covered active sub-topic when choosing what to post next; never post outside them without the user asking.

  • MCP tool: subtopics_list. Catalog: reach it with find_actions and run_read_action, or turn on the full toolset.
  • REST: GET /v1/subtopics/list
  • CLI: xholic subtopics list
  • Scope: read
  • Plan: Every plan, including the trial
  • Cost: Free.
  • Rate limit bucket: read

Input

Field Type Required Description
includeRemoved boolean No Also list sub-topics the user removed.
includeTrends boolean No Include the posts taking off on each sub-topic (url, author, text, views, × their usual).
account string ≤ 64 chars No X account to act on, as @handle. Leave it out to use the connection’s default account.
note string ≤ 20000 chars No Optional, on any tool: one or two sentences for Xholic’s shared memory about what the user just decided, asked for or said about themselves or their plans (e.g. “Dropping threads for now; focusing on replies to founders”). Every AI the user connects reads it, so they never repeat themselves. In your words, never other people’s posts. Leave it out when nothing new was said.

subtopics.save · write

Change the user’s sub-topics in one call: approve suggested or trial ones (a trial lane approved stays in the plan for good), remove or restore, add the user’s own (active at once), edit a name, description or keywords, or set weights (how much the weekly plan leans on each; 1 is normal). Removed ones are never suggested again. Xholic re-plans around the change within minutes. Call it only when the user asked for this in the conversation; never on your own initiative. Returns the updated list.

  • MCP tool: subtopics_save. Catalog: reach it with find_actions and run_write_action, or turn on the full toolset.
  • REST: POST /v1/subtopics/save
  • CLI: xholic subtopics save
  • Scope: write
  • Plan: Every plan, including the trial
  • Cost: Free.
  • Rate limit bucket: write

Input

Field Type Required Description
approve array of string (uuid) (max 20) No Suggested sub-topics to approve (they become active).
remove array of string (uuid) (max 20) No Sub-topics to remove; Xholic won’t suggest them again.
restore array of string (uuid) (max 20) No Removed sub-topics to bring back as active.
add array of object (max 8) No The user’s own sub-topics, active at once.
edit array of object (max 12) No Changes to existing sub-topics; an edited one becomes the user’s own.
weights array of object (max 12) No How much the weekly plan leans on each sub-topic.
account string ≤ 64 chars No X account to act on, as @handle. Leave it out to use the connection’s default account.
note string ≤ 20000 chars No Optional, on any tool: one or two sentences for Xholic’s shared memory about what the user just decided, asked for or said about themselves or their plans (e.g. “Dropping threads for now; focusing on replies to founders”). Every AI the user connects reads it, so they never repeat themselves. In your words, never other people’s posts. Leave it out when nothing new was said.
dryRun boolean No Return exactly what would happen without doing it.
idempotencyKey string ≤ 200 chars No A unique key for this write. Repeating a call with the same key returns the first result instead of acting twice.