InfiniteRanks documentation
Rename a tag without obscuring its reporting meaning
The public contract has no PUT tag endpoint. Edit supported tag metadata through workspace controls.
Supported way to perform the task
Review the label’s current assignments and any report using it. Decide whether a rename preserves meaning or whether a new tag is needed for a different cohort.
What needs review
A new color is presentation; a new audience definition is analytical scope. Record the latter and keep the old cohort in historical reporting. Review saved report notes before a semantic rename.
Developer access boundary
The supported public resources are GET /api/v1/workspace, /api/v1/prompts, /api/v1/answers and /api/v1/sources. A read-only key cannot perform this write action. Do not reuse authenticated internal app requests as a promised public automation contract.
Verify the result
Read the relevant current records after saving through the app and retain the IDs, review date and evidence needed to explain the change. A client-side preview, successful export or generated instruction is not confirmation that a workspace mutation occurred.
Sources and further reading
Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.