REST API: topics
Curate agent topics and use topic statistics for review workflows.
Topics are agent-scoped resources. Begin a curation job by reading the agent's topics and their statistics, then create, update, merge, or remove only the records your policy selected. Keep the agent identifier and topic identifier separate: a merge or deletion should never be built from display text alone, because labels can be similar and change over time.
Use similar-topic results as a review aid, not an automatic merge instruction. A safe workflow records the candidate topics, applies a chosen merge, and reads the resulting list again before proceeding. Topic statistics have their own bounded query behavior and are not a substitute for all-conversation reporting; use the Analytics guides when the question is about broader performance.
Topic mutations require a trusted backend and a write-capable key. Validate the outgoing payload against the generated reference, surface API validation errors to the operator, and retain enough context to undo an incorrect curation decision through your own operational process.