InfiniteRanks documentation
Plan a partial topic correction safely
The read-only API does not accept PATCH requests for topics. A partial correction must use the app’s supported editing workflow.
Supported way to perform the task
Identify exactly which questions have the incorrect topic and keep unrelated fields unchanged in the review. Check the saved result rather than assuming a client-side preview persisted it.
What needs review
Do not simulate a PATCH request against an invented endpoint. Keep the prior export and verify that any historical report still describes its original topic cohort.
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.