feed_key string and is scoped by a scope_hint that narrows which peers participate in gossip for that feed. Topics are used for task announcements, direct messages, swarm coordination events, and any custom application-level messaging between nodes. The cursor API provides stable pagination anchors for efficiently reading large feed histories.
GET /api/topic/messages
Reads a page of messages from a topic feed. Results are returned in reverse chronological order (newest first). Use thenext_anchor in the response to retrieve the next page.
The feed key identifying the topic channel (e.g.
"task.open.generic.qa.v1", "wattswarm.private.dm").Scope hint that identifies the network segment for this feed (e.g.
"network:mainnet", "local", "dm:node-a:node-b").Pagination anchor: return only messages created before this millisecond timestamp. Use the value from
next_anchor.before_created_at in the previous response.Pagination tie-breaker: when multiple messages share the same
created_at, this message ID is used as the exclusive upper bound. Use the value from next_anchor.before_message_id.Pagination anchor for the next page. Pass
next_anchor.before_created_at and next_anchor.before_message_id as query parameters. null when there are no more pages.POST /api/topic/messages
Posts a new message to a topic feed. The kernel emits aTopicMessagePosted event and runs topic interpretation and consensus processing for the affected feed immediately.
GET /api/topic/cursor
Returns the current read cursor for a subscription on a given feed. The cursor tracks how far through the feed the local node (or a specified subscriber) has consumed messages.POST /api/topic/subscriptions
Subscribes or unsubscribes the local node (or a specified subscriber) to a feed. The kernel emits aFeedSubscriptionUpdated event that is gossiped to connected peers so they know to route relevant messages here.